What exactly does the Cursor integration do?

It installs a hook in your Cursor config. When the agent stops, finishing a turn or asking a question, wispa shows a reply window where you answer by voice or text, and sends your answer back into the session.

Do I have to edit config files by hand?

No. Flip the Cursor switch in wispa's Integrations tab and it writes the hook for you; toggle it off to remove it cleanly. Start a new Cursor session for the change to take effect.

Does it pop up on every single message?

By default wispa only opens when Cursor's message reads like a question or a request for input, and stays quiet during ordinary progress. Prefer it on every turn? That's a single toggle.

Does my answer go back into the same session?

Yes. Continuation mode returns your reply straight into the running session and works even when the terminal is in the background. You can also choose Paste, which types it in like a normal dictation.

Can I fix a mistake before it sends?

Always. The window opens with a text field, so you can speak or type, correct anything, and nothing is sent until you press Send or Enter. Esc dismisses it without answering.

Does this work with Claude Code, Codex and Gemini CLI?

Yes. The same reply overlay supports Claude Code, Codex and Gemini CLI too, each with its own page. This one covers Cursor.

wispa for coding agents

Answer Cursor by voice.

Cursor's agent ranges across your codebase and stops when a direction call actually matters. wispa catches that moment: a reply window opens wherever you are, you answer by voice, and it goes straight back into the session.

Download for Mac

Requires wispa for macOS 13+. Free in beta, no account.

Cursor is waiting

wispa-landing/auth

The useSession hook is duplicated across three components, each fetching a little differently.

Want me to:

Extract one shared provider and consume it everywhere
Keep them separate but dedupe the fetch logic
Leave it and just fix the stale-token bug

Which direction should I take?

Cancel esc Speak ⌘L Send ⏎

How it works

Set it up once, then just talk.

Turn on the Cursor hook

Open wispa, go to Integrations, and flip the Cursor switch. It writes the hook for you; start a new session to activate.
Cursor pauses and asks

When the agent needs you, the reply window appears over whatever app you are in, with its message and project.
Answer out loud

Hold your dictation key and speak, or just type. Hit Send, and your answer lands back in the session.

Why it's better

Built for the way agents actually interrupt you.

Weigh in on the big calls

Cursor's agent can touch a lot of files before it needs you. When it stops to choose a direction, wispa surfaces over your editor with the full message, so the decisions that shape the change never wait in a buried terminal.

Speak the spec, don't type it

Broad changes need detailed direction, and a paragraph of intent is faster spoken than typed. wispa sets your words down as clean text right in the reply box.

Back into the running session

Continuation drops your answer straight into the live Cursor session, even when the terminal sits in the background. Prefer the old way? Paste types it in like a normal dictation.

FAQ