Run several Claude Code and Codex sessions at once without babysitting them
SpeakApp reads your AI agents' replies aloud, one after another. You say “ok”, answer, say “enter”, and your message goes into the right session, with no window to hunt down. When several sessions run at once, the queue keeps the waiting ones in order, and the Control Center shows which one is working, finished, waiting or frozen. Dictation writes a text. It doesn't replace that tracking.
Why several sessions change how you work
One session analyses a file, another drafts a client write-up, a third prepares an answer. Each finishes in its own time. The problem is no longer writing: it is knowing which one is waiting, reading what it produced, then answering in the right place.
How the listening loop handles it
- A queue: finished replies wait and are read to you one after another, as they come.
- One toast per waiting conversation, at the top right, with read, skip, later, reply and open. The widget's circle counts what is left.
- Words to say: “ok” to answer, “pause”, “skip”, “later”, “replay”, “stop”. A first “stop” pauses, a second one turns reading mode off.
- A choice of what you hear: take a conversation out of the reading when you don't want to hear it, and put it back whenever you like.
- The Control Center, which shows which session is working, finished, waiting or frozen.
To answer: “ok”, your answer aloud, then “enter”. It is pasted and sent into the session shown in the toast, not into the last window you touched. Still glance at the conversation name on the toast before saying “ok”.
With which apps?
Listening and replying work with Claude Desktop (the Code tab, and Cowork locally), the Codex Windows app, Cursor, VS Code, Claude.ai and ChatGPT in Chrome through the SpeakApp extension for web apps. The full table, app by app, is on the features page.
One limit to know: SpeakApp doesn't read sessions that run in the cloud.
Dictation, voice loop or keyboard?
| Pick it for | What you still do yourself | |
|---|---|---|
| The listening loop | Following several sessions without leaving your work | Reading code or visual details on screen |
| Dictation alone | Saying a message instead of typing it | Choosing the session and reading its replies |
| Keyboard and windows | Careful, screen-centred review | Finding each window and checking its state |
Hearing a reply doesn't make it right. Keep the screen for what needs a visual review: a fix, a table, a document to proofread.
Keep reading
SpeakApp is available on Windows, coming soon to Mac. See pricing.
Frequently asked questions
How do I run multiple Claude Code sessions without checking each window?
With SpeakApp, finished replies are read one after another. You say “ok”, answer, say “enter”, and the message goes into the session of the conversation shown in the toast.
What happens when several conversations are waiting?
They wait in a queue, one card per conversation in the toast. You can read, skip, postpone, reply or open the conversation. The widget's circle counts what is waiting.
Can I take a conversation out of the reading?
Yes. You remove it from the reading when you don't want to hear it, and put it back whenever you like.
What is the difference between dictating and replying in a session?
Dictating writes your words at the cursor, in the field you chose. Replying sends your answer into the session of the conversation in the toast.
Are sessions running in the cloud read?
No. SpeakApp doesn't read sessions that run in the cloud.
Do I have to give up the keyboard?
No. The keyboard stays useful for reviewing code or phrasing a precise change.
Try SpeakApp
SpeakApp is available on Windows, coming soon to Mac. Download SpeakApp or join the Mac waiting list. To see the whole product first: What is SpeakApp?