Voice for Cursor

wispa gives Cursor a voice loop, and this is the one agent where it reaches both the terminal and the Cursor editor. When Cursor's agent stops to ask you something, you answer by voice and Cursor picks up your reply as the next message.

How the voice loop works with Cursor

Cursor runs a stop hook when its agent finishes a turn. wispa installs it, so when Cursor waits for you it passes its last message to wispa. You speak your answer, and wispa hands the text back as a follow-up message that Cursor submits on its own, so the agent keeps working.

Set it up

1. Open wispa's Integrations, pick Cursor, and install. wispa writes the stop hook into $HOME/.cursor/hooks.json and backs up any existing file.
2. Use Cursor the way you normally do, in the editor or in the Cursor CLI.
3. When the agent stops and asks, hold your wispa hotkey and speak your reply.
4. wispa transcribes it and Cursor submits it as the next message, then continues.

Terminal or editor?

Both. Cursor's stop hook fires whether you run the agent in the Cursor editor or the Cursor CLI, and in each case Cursor submits the follow-up wispa returns. That makes Cursor the one coding agent where the voice loop covers the graphical app as well as the terminal.

What wispa does in the background

wispa runs a local listener on 127.0.0.1 behind a private token, unreachable from the web. Cursor's hook sends its last message and workspace folder, read from the session transcript. wispa records your reply and transcribes it with your voice-loop model, with no AI cleanup on it, then returns it as a follow-up framed as user input. If a turn was cancelled rather than finished, wispa stays quiet and no prompt appears.