Voice for OpenCode

wispa adds a voice loop to OpenCode. Unlike the hook-based agents, OpenCode uses a small plugin that wispa drops in, and from then on you answer OpenCode by voice when it waits for you.

How the voice loop works with OpenCode

OpenCode signals when a session goes idle at the end of a turn. wispa's plugin catches that, reads the last message, and passes it to wispa. You speak your reply, and the plugin sends it back into OpenCode as your next message through OpenCode's own interface, so the session continues.

Set it up

1. In wispa's Integrations, choose OpenCode and install. wispa writes a plugin to $HOME/.config/opencode/plugin/wispa-voice-loop.js.
2. Start or restart OpenCode in your terminal so it loads the new plugin.
3. When OpenCode finishes and waits, hold your wispa hotkey and speak your reply.
4. The plugin sends your transcribed answer back into OpenCode, which continues.

Where it runs

OpenCode runs in the terminal, and that is where the voice loop drives it. For anything outside the loop, normal push-to-talk dictation still lets you speak text into any other app.

What wispa does in the background

wispa runs a local listener on 127.0.0.1 behind a private token, unreachable from the web. The plugin fetches it when OpenCode goes idle, sending the last message and the working folder. wispa records your reply and transcribes it with your voice-loop model, with no AI cleanup on it, and returns the text; the plugin then injects it into OpenCode framed as user input.