Skip to main content

Documentation Index

Fetch the complete documentation index at: https://mintlify.com/bastndev/f1/llms.txt

Use this file to discover all available pages before exploring further.

Every CLI Hub session ships with five tools docked into the right side of the panel. Each tool is toggled by a dedicated keyboard shortcut — no mouse required — and closes automatically when you refocus the terminal. The tools share the panel’s full height so they never obscure the terminal content; they slide in as an overlay alongside the active xterm.js canvas.

​
Tool Reference

The Prompt Composer is the richest of the five tools. It provides a multi-line text editor with @-file mention expansion, clipboard image paste, live spellcheck across four languages, a source-language picker that auto-translates to English, and skill chip attachment.Open it with Shift+F1 and send the composed prompt to the active CLI with Ctrl+Enter (⌘+Enter on macOS). See the dedicated Prompt Composer page for full documentation.
The Translator lets you translate any text from the terminal session inline, without leaving the panel. Select output text from the terminal and press Shift+F2 to open the modal; the selection is pre-populated and translation begins immediately.Translation uses the same two-provider pipeline as the Prompt Composer (host-prompt-translator.ts):
  • MyMemory — primary provider for short selections
  • Google Translate (unofficial) — automatic fallback, preferred for longer selections
The result appears directly in the modal. The translator supports all five prompt languages: English, Spanish, Chinese, Portuguese, and Russian.
The Status / Use view shows a per-agent summary of the active session’s state. Press Shift+F3 to open it. The view reflects the current session’s status (running, exited, or error), the command line that was used to launch the agent, the working directory (cwd), and whether the session is awaiting its first output.This tool is useful for verifying which command is actually running in a given session tab — especially helpful when using a Custom CLI whose label may differ from the binary name.
The Keymaps view is an in-panel shortcut reference for the active CLI. Press Shift+F4 to open it. The reference is scoped to the current agent so you always see shortcuts relevant to the tool you are working in rather than a generic list.This is particularly useful when working with a new agent whose keyboard model (Vim-style, Emacs-style, or custom) you are not yet familiar with. No internet connection is required — the reference is bundled with the extension.
The Commands palette is a searchable list of every slash command the active agent supports. Press Alt+F1 to open it. The palette is per-agent and switches automatically when you change sessions, so /models (OpenCode) never appears while you are in a Claude Code session that expects /model.Each agent’s command fragment lives under src/my-cli/webview/tools/modal-commands/components/<agent>/. The palette is styled using the --agent-accent CSS custom property so the highlight color matches the active agent’s brand color.Type to filter commands as you search. Pressing Enter on a result inserts the slash command into the terminal input.

​
Voice: Read Replies Aloud

CLI Hub includes a full text-to-speech system that can read agent replies aloud using the Piper TTS engine. Voice is available in five languages matching the prompt composer: English, Spanish, Chinese, Portuguese, and Russian.

​
Setup

Voice uses the Piper TTS engine with one high-quality ONNX voice model per language. On first use, F1 downloads the engine and the voice model for the selected language via a VS Code progress notification. If you also have the ATM extension installed (bastndev.atm), F1 reuses any Piper engine or voice files ATM already downloaded — nothing is downloaded twice. Voice models used per language:
LanguageVoice ID
Englishen_US-hfc_female-medium
Spanishes_ES-sharvard-medium
Chinesezh_CN-huayan-medium
Portuguesept_BR-faber-medium
Russianru_RU-irina-medium

​
Playback Controls

ActionShortcut
Play / pause the current readSpace
Playback uses the native audio player for each platform (afplay on macOS, aplay on Linux, PowerShell SoundPlayer on Windows). Audio is streamed directly from Piper to the player so sound starts as soon as the first synthesized bytes are ready — there is no full-buffer wait.

​
Finish-Ding Cue

The finish-ding is an optional short audio cue that plays when an agent finishes responding. It is designed for the case when you have switched away from the F1 panel to do other work — you hear the ding without having to watch the terminal. The cue is suppressed when the F1 panel is both visible and the VS Code window has OS focus (i.e. you are actively watching the response). It plays in all other states: when you are in a different panel, the window is collapsed, or you have switched to another application. Per-language WAV files are shipped inside the extension under dist/my-cli/shared/voice/wav/. A minimum gap of 500 ms between cues prevents a double-fire when a settle event and an exit line arrive close together. 
// Platform playback commands used by finish-sound.ts
case 'darwin': { command: 'afplay', args: [wavPath] }
case 'linux':  { command: 'aplay',  args: ['-q', wavPath] }
case 'win32':  { command: 'powershell', args: ['-NoProfile', '-Command',
                  `(New-Object Media.SoundPlayer '${wavPath}').PlaySync()`] }
Voice and finish-ding both run entirely in the extension host process, not in the webview. This is intentional: the My CLI webview is torn down whenever you leave the F1 panel, so a webview-side audio cue would never fire while you are working elsewhere. The host process stays alive and owns the output stream, so it can both detect when a response finishes and play the sound.

Build docs developers (and LLMs) love

Get started for freeTalk to us