Voice input for opencode
Open-source terminal agents like opencode put the whole session in plain text — the file tree, the prompt, the diff. Halo adds one more plain-text input: your voice.
Everything’s already a text stream
A terminal agent session is just text going in and text coming out — no hidden UI state, nothing you can’t select and edit. That makes it a good match for dictation: whatever you say becomes exactly the same kind of input as whatever you’d have typed, sitting in the same prompt field.
Getting set up
Halo installs like any other system tray app. The first launch asks for microphone access. From there, pick a hotkey, open the terminal where you run opencode, and you’re set. There’s no config file to edit and nothing to point at your project directory; Halo doesn’t know or care what agent you’re running.
Why this matters for community tools
Open-source agents move fast and get configured differently by everyone who runs them. A dictation tool that hooks into a specific CLI would break the moment that CLI’s interface changed. Halo avoids that entirely by staying at the OS level — it works the same whether you’re on the latest build or a fork someone patched last night.
Frequently asked questions
Is Halo affiliated with the opencode project?
No. Halo is a separate, independent app. It works with opencode the same way it works with any terminal program — by typing into the focused window.
Does it need to know my project structure?
No. Halo only sees that a text field is focused; it has no access to your files or terminal history.
Will an update to opencode break dictation?
It shouldn't — Halo doesn't depend on any particular CLI's version or output format.
Can I use it for shell commands too, not just prompts?
Yes, Halo will transcribe into any focused prompt, including a plain shell.
Speak your next prompt
No config, no plugin — just a hotkey that works in whatever terminal you have open.
Download Halo