Documentation · v0.1.7
Using talk2me
talk2me is a voice layer for coding agents that live in the terminal. You talk, it turns your words into the agent’s prompt. The agent works; Blip, the mascot, tells you the short version and leaves the full reply on screen. There’s no LLM inside talk2me: speech goes through Deepgram Flux, and everything else is a deterministic Rust engine.
Install
- Download
talk2me_0.1.7_x64-setup.exe(11 MB) from the download section. - Run it. It installs for your Windows user only (no admin rights) into
%LOCALAPPDATA%\talk2me, withtalk2me.exeand thet2m.exeterminal wrapper side by side, and fetches WebView2 if it’s missing. - If SmartScreen says Windows protected your PC, choose More info → Run anyway. This early build isn’t code-signed yet.
To check the download first, compare its hash with the one on the download page:
Get-FileHash .\talk2me_0.1.7_x64-setup.exe -Algorithm SHA256
# 09fabdc6c89edc14202dbde1a9ef57a839068650e893433e89fe1b09579d689b
You’ll need
Windows 11 x64 (Windows 10 22H2 is best effort), a microphone, a Deepgram API key, and Kiro CLI or OpenCode installed and signed in.
First run
The first launch walks you through five short steps. You can run it again any time from Settings → Startup & advanced → Run setup again.
- Welcome. Blip says hi.
- Microphone. Pick your mic and say something; the level meter shows Blip hears you. Keep echo cancellation on if you use speakers.
- Voice engine. Paste your Deepgram key and press Test. It’s stored in Windows Credential Manager.
- Agents. talk2me lists the agents it found and offers to install the voice rule. Nothing is written until you press Continue.
- Style. Pick Blip’s voice, whether to start hands-free or push-to-talk, and how chatty Blip is while the agent works.
Deepgram key
talk2me uses Deepgram in both directions: Flux for speech-to-text (it detects when you’ve finished a sentence) and Flux TTS for Blip’s voice. Create a key in your Deepgram console and paste it in setup or in Settings → Voice & engines → Deepgram key. Deepgram bills usage to your key.
- The key lives in Windows Credential Manager and never reaches the web UI. Settings shows only its last four characters.
- Test makes one request and tells you what went wrong: a rejected key, missing permissions, no credit, rate limiting or no network.
- Region set to Auto picks the fastest Deepgram region by connect time. You can pin US, EU, India or Australia.
- Optional: send your folder and agent names to Flux as keyterms so project names are recognised, and opt out of Deepgram’s Model Improvement Program.
Start a session
Home asks Who do you want to talk to?
- Start a new session: pick Kiro CLI or OpenCode and a project folder, then press Start talking or Enter. talk2me launches the agent over ACP, the cleanest two-way connection, and keeps the transcript.
- Attach to a running session: talk to an agent that’s already open in a terminal, and keep watching its TUI. See Kiro CLI and OpenCode.
- Recent conversations: press Resume to pick one up again.
While it connects you’ll see a short checklist. If the agent needs you to sign in (for example “run kiro-cli login”), it says so with Retry and Open log buttons.
Talking
Hands-free
The mic stays open for the whole session. Just talk. Your words appear live as you speak, and when Flux detects the end of your turn they’re sent to the agent. Settings → Listening lets you tune Patience (how sure Flux must be that you’re done) or switch end-of-turn detection to manual.
Push-to-talk
Hold Right Alt (Right Ctrl on AltGr keyboard layouts), talk, and let go to send. The key works in every app, even when talk2me is hidden. Change the key in Settings → Shortcuts, or make it tap-to-toggle in Settings → Listening. Switch between modes with Ctrl+Shift+Space, the dock, or by saying “push to talk” / “hands free”.
Mute
Ctrl+Shift+M or the mic button. Hard mute releases the microphone.
While the agent is busy
If you talk while the agent is still working, talk2me holds your words until it’s idle. With a Kiro attach session you can choose to steer it mid-turn instead (Settings → While working).
What Blip says
Blip speaks a short summary, not the whole reply. The full answer, tool steps and diffs are always in the conversation panel, and Full reply on Blip’s card expands it.
- The
<say>line. With the voice rule installed, the agent ends its reply with a short<say>…</say>line. Blip speaks it sentence by sentence while it streams. - No
<say>? A markdown-aware fallback picks the first sentences and a trailing question, and skips code, tables and long lists. - While it works Blip stays quiet by default and speaks only for questions, permission requests, errors and the final answer. You can also have it say milestones (“Still on it, tests are running”), or stay silent until done.
- Tune it in Settings → Voice & engines: voice, speed, reply length, when to start speaking, and the maximum spoken length for the fallback.
Voice commands
Short whole-sentence commands (up to five words, eight if you say “Blip”) are handled by talk2me instead of being sent to the agent.
| Say | What happens |
|---|---|
| “stop”, “cancel that”, “never mind”, “scratch that” | Cancel the agent’s current turn |
| “stop, and use Tailwind instead” | Cancel, then send the rest as the next prompt |
| “quiet”, “stop talking”, “enough” | Stop Blip talking (the work carries on) |
| “repeat that”, “say that again” | Repeat the last spoken line |
| “read the full reply”, “read it all” | Read the whole reply aloud |
| “mute”, “go silent” / “unmute”, “you can talk” | Mute or unmute Blip’s voice |
| “mute mic”, “stop listening” | Mute the microphone |
| “push to talk” / “hands free” | Switch input mode |
| “quiet mode”, “milestones”, “silent mode”, “chatty” | Change how much Blip says while the agent works |
| “disconnect”, “hang up”, “bye Blip” | End the session (asks twice if the agent is busy) |
Turn the “stop” words off in Settings → Listening → Say “stop” to cancel the agent.
Permissions
When the agent asks to run a command or edit a file, a card appears and Blip asks you (you can turn the spoken question off). Answer however suits you:
- By voice: “yes”, “no”, “always”, or “yes, but use pnpm”, which turns the request down and sends your correction as the next prompt. The card shows what it heard.
- By click: Allow once, Always allow, or Deny.
- By keyboard: Alt+Y allow once, Alt+A always, Alt+N deny.
The answer grammar follows a fixed 13-rule order and never guesses “allow”: an unclear answer is asked again, and Blip’s own voice echoing back can’t approve anything.
Risky commands
More than 20 patterns are classified as risky: force pushes, reset --hard, recursive deletes (including Remove-Item -Recurse), curl | sh, publishing, admin elevation, and edits outside the project under system or profile paths. For these:
- By default voice can’t approve them. Blip says “That one needs a click. Use Allow on the card.”
- If you turn off Settings → While working → Risky commands need a click, you approve them with a spoken “confirm”, once, after Blip explains the risk.
- “Always” is never granted by voice for a risky command.
Interrupt and stop
- Talk over Blip. It ducks as soon as you start and stops on a real word; an “uh-huh” lets it carry on. Pressing push-to-talk stops it at once. Interrupting the voice never cancels the agent’s work.
- Esc stops Blip talking. Esc Esc (twice within 0.6 s) cancels the agent’s turn, like the Stop button or saying “stop”.
- With speakers, echo is cancelled in Rust using the exact audio being played, so Blip doesn’t interrupt itself. Turn on I’m using headphones in Settings → Listening to make interrupting easier.
Typing
Click the composer under the conversation, or press Ctrl+L. The voice pauses while you type; Enter sends and Shift+Enter adds a line. The reply is still spoken (you can turn off the <say> request for typed prompts).
Widget and tray
The floating widget lets you keep talking with the main window closed. It never takes focus from the window you’re typing in.
- Pill: Blip, the current line and progress. Click it to open the card.
- Card: the full state, permission answers and controls. It opens by itself when the agent needs you and closes again when the work is done. Esc closes it.
- Mini: a small Blip snapped to the screen edge that becomes the pill on hover.
- Ctrl+Alt+Space shows or hides the widget from anywhere. Choose its corner, always-on-top and auto-expand in Settings → Appearance.
- Closing the main window hides it; talk2me keeps running in the tray. Quit from the tray menu.
Reading Blip
Blip’s colour and face tell you the state at a glance, and the status line under it says it in words for screen readers.
Blip has 18 emotions in all. Settings → Appearance → Motion sets full, reduced (only the mouth moves) or off; Windows’ reduced-motion setting is respected automatically.
Keyboard shortcuts
| Keys | Action | Where |
|---|---|---|
| Right Alt (hold) | Push-to-talk | Global |
| Ctrl+Alt+Space | Show / hide the widget | Global |
| Ctrl+Shift+Space | Toggle hands-free / push-to-talk | Global |
| Ctrl+Shift+M | Mute the microphone | Global |
| Esc | Stop Blip talking | In talk2me |
| Esc Esc | Cancel the agent’s turn | In talk2me |
| Ctrl+L | Focus the text box | In talk2me |
| Ctrl+K | Command palette | In talk2me |
| Alt+Y / A / N | Allow once / always / deny | In talk2me |
| Enter | Start talking (on Home) | In talk2me |
Kiro CLI
- Native session. talk2me starts
kiro-cli acpfor you (v3 engine, falling back to v2). This is the default and needs nothing else. - Attach in your own terminal. Run Kiro through the wrapper and talk2me can join it while you keep the TUI:
Turn on Settings → Agents → Make t2m available in terminals to add talk2me’s folder to your user PATH, or runt2m kiro%LOCALAPPDATA%\talk2me\t2m.exe kiro. Then pick the session under Attach to a running session. - Kiro must be installed and signed in (
kiro-cli login).
Kiro IDE experimental
The reliable way: continue the chat in talk2me. Home lists Your Kiro chats, the chats you had in Kiro IDE or Kiro CLI over the last two weeks. Talk here reopens that exact chat over ACP, on its own model and with everything it already knows, and you can keep talking for as long as you like. If the chat can’t be opened, talk2me tells you instead of starting a new one. Leave that chat alone in Kiro while you talk here.
Voice inside Kiro IDE. Kiro IDE has no way for another app to type into its chat, so talk2me uses Kiro’s own end-of-turn hook instead. Kiro runs that hook once per message you type, so this gives you one spoken answer per typed message.
- Turn it on with Voice in Kiro IDE on the chat you want, in Your Kiro chats. talk2me adds one file,
~/.kiro/hooks/talk2me.json, aStophook that runst2m.exe hook, and follows only that chat. Turning Settings → Agents → Kiro IDE voice off removes the file. - Send a message in that chat as usual. When the reply finishes, the widget appears, Blip reads you the gist, and what you say next is sent to Kiro as your answer. After Kiro replies to that, type your next message in Kiro, or switch to Talk here for nonstop voice.
- Stay quiet for a minute and the turn simply ends. Type in Kiro whenever you like.
- Approvals, cancel and model changes stay in Kiro’s own window.
- Safety: nothing is sent unless you said or typed it, and after 10 voice turns in a row talk2me asks you to type once in Kiro. If talk2me isn’t running, the hook exits at once and Kiro behaves as if it weren’t there.
- Other chats and other projects are never picked up, and neither are workflow steps, sub-agents or any session talk2me is already connected to another way. After you disconnect, talk2me leaves that chat alone until you pick a chat again or it restarts.
OpenCode
- Native session. talk2me starts
opencode acp. - Attach. talk2me can talk to sessions in OpenCode’s background service through its server API (
/api/session,/api/event). If the service is unhealthy, the attach screen says so and offers a restart.
The voice rule
The voice rule is a short instruction that asks the agent to end replies to voice prompts with a one-to-three sentence <say> line. It’s optional (Blip summarises replies itself without it), and nothing is written until you confirm.
- Kiro CLI:
~/.kiro/steering/talk2me-voice.md - OpenCode: a marker block in
~/.config/opencode/AGENTS.md, with the diff shown first
Install or remove it in Settings → Agents.
Settings
| Tab | What’s there |
|---|---|
| Voice & engines | Deepgram key and region, keyterms, training opt-out, Blip’s voice and speed, what gets spoken |
| Listening | Hands-free or push-to-talk, the PTT key, end-of-turn detection and patience, interrupting, stop words, mic and speaker, echo and noise |
| While working | How much Blip says, activity feed, widget progress, finish chime, talking while busy, risky commands need a click |
| Agents | Kiro CLI and OpenCode: native sessions, engine, attach, t2m on PATH, voice rules |
| Appearance | Scanlines, widget position and behaviour, Blip’s motion, keycap hint, let your screen reader speak instead of Blip |
| Shortcuts | The PTT key and the global shortcuts |
| Privacy & data | How long transcripts are kept, the data folder, what’s sent to Deepgram |
| Startup & advanced | Launch at sign-in, start in the tray, log level, export diagnostics, run setup again |
Press Ctrl+K for the command palette to reach any of these by name.
Privacy and data
- Your voice goes to Deepgram Flux only while a session is connected and the mic is live. Blip’s spoken lines go to Flux TTS.
- The full agent reply, your code and your files never leave your PC through talk2me.
- No accounts, no telemetry, no analytics.
- Conversations are stored locally as JSONL; choose how long to keep them (forever, 90 days, 30 days, or not at all).
- The Deepgram key is in Windows Credential Manager. Hard mute releases the microphone.
- Diagnostics are exported only when you ask, and never include mic audio unless you turned that on.
Troubleshooting
- SmartScreen blocks the installer
- The build isn’t code-signed yet. Choose More info → Run anyway, after checking the SHA-256 if you like.
- Blip doesn’t hear me
- Check Settings → Listening → Device and the level meter. If Windows blocks mic access for desktop apps, setup links to the microphone privacy settings. Make sure you’re not muted (Ctrl+Shift+M) and not in push-to-talk mode.
- “Deepgram didn’t accept this key”
- Paste the key again in Settings → Voice & engines and press Test; the message says whether it’s the key, its permissions, credit or the network.
- The agent won’t connect
- Make sure the CLI works on its own in a terminal and you’re signed in (
kiro-cli login). The connect checklist shows which step failed; Open log shows why. - Blip talks over itself on speakers
- Keep echo cancellation on, lower the speaker volume, or use headphones.
- Reporting a bug
- Settings → Startup & advanced → Export diagnostics saves logs you can attach to an issue.
Build from source
You need Rust 1.98.1 (pinned in rust-toolchain.toml) and Node 22.
# dependencies
npm ci # Tauri CLI
npm --prefix app ci # frontend
# run the app (Vite on :1420)
npx tauri dev
# tests and gates
cargo test --workspace
cargo clippy --workspace --all-targets -- -D warnings
npm --prefix app run typecheck; npm --prefix app test
# the Windows installer (target/release/bundle/nsis/)
npx tauri build --bundles nsis
# this website (site/dist)
npm --prefix site run build
The repository layout, crates and architecture are described in the README.
Status and limits
v0.1.7 is an early release. It has been verified end to end on a real machine with a scripted agent and live Deepgram voice (822 Rust tests, 186 frontend tests, a live TTS → STT round trip and a 14-check app run).
- Everyday use with real Kiro CLI and OpenCode sessions is the next step. Please report what breaks.
- The installer isn’t signed yet, and auto-update is off: download new versions from this site.
- The offline voice pack (small on-device models used when Deepgram is unreachable) and Kiro click-to-type attach aren’t available yet. Without Deepgram, you can still type.
- Windows only for now. Claude Code and Cursor adapters are planned.
Uninstall
Use Settings → Apps → Installed apps → talk2me → Uninstall in Windows, or run %LOCALAPPDATA%\talk2me\uninstall.exe. If you added the voice rule, remove it first in Settings → Agents, or delete the file listed above.