roykollensvendsen/claude-voice

Talk to the Claude Code sessions on your own computer from your phone.
You speak to a voice assistant (Claude's mobile app in voice mode is the one
this was proven with). The assistant calls this bridge over the internet,
and the bridge does the work on your computer:
it starts and follows Claude Code sessions there;
it passes your messages into sessions already open in a terminal;
it reads back what they did.
Claude Code runs under your own Claude subscription, not a pay-per-use API key.
Anything risky, such as editing files or running commands, waits until you say
yes.
The bridge is an MCP server: a program
offering named tools that an AI assistant can call.
text
voice assistant on the phone (Claude app, voice mode)
│ custom connector, signed in with OAuth
public HTTPS address (e.g. Tailscale Funnel)
claude-voice on your computer
├─ sessions it runs itself ──► Claude Agent SDK ──► Claude Code
└─ sessions open elsewhere ──► Claude Code's own session messaging and transcripts
## Start here: five minutes on one computer
You need Linux or macOS, a Claude subscription (Pro or Max), and an internet
connection. Nothing else has to be installed first.
An assistant doing this for you should read AGENTS.md first.
bash
curl -LsSf https://astral.sh/uv/install.sh | sh # uv, which installs Python tools
curl -fsSL https://claude.ai/install.sh | bash # Claude Code
export PATH="$HOME/.local/bin:$PATH"
uv tool install git+https://github.com/roykollensvendsen/claude-voice
mkdir -p ~/src # the bridge only works in folders under here
claude-voice check
check now says that Claude Code is not signed in. Run claude, type
/login, sign in with your Claude account, and run claude-voice check again.
It should print ready to serve over stdio. Your projects belong in ~/src;
to use another folder, set CLAUDEVOICEROOT (see the settings).
Then connect it to Claude Code on the same computer:
bash
claude mcp add --scope user claude-voice -- claude-voice serve
Start claude in any folder and ask: "Which Claude Code sessions are running
on this computer?" The answer comes from the bridge. In Claude Desktop, add
this to its configuration file instead (Settings → Developer → Edit Config),
with the full path that which claude-voice prints:
json
{ "mcpServers": { "claude-voice": { "command": "/home/you/.local/bin/claude-voice", "args": ["serve"] } } }
That is the whole bridge, used locally. The next two steps let you reach it from
a phone: run it as a service,
then give it a public address.
## What it depends on
Only a signed-in Claude Code is required. Each of the rest adds something, and
the bridge says which are missing, with the exact fix, through its
checkdependencies tool and the event API's /api/v1/doctor:
| Dependency | What it adds |
| Claude Code, signed in | everything; required |
| git | git status on the companion app's cards, and the contribute session |
| GitHub CLI (gh), signed in | pull requests on the cards, and the contribute session |
| uv | updating claude-voice and running its tests |
| Tailscale, with Funnel | reaching the bridge from the phone |
| a tailnet-only tailscale serve port | the companion app on the phone |
| the status line writing its figures | the plan's five-hour and weekly bars, and how full each session is |