Carbon Voice + Claude Code

About this intergration

Why Carbon Voice?

Talk to Claude Code — Tap a button on your phone or computer to start >talking to Claude Code.

Send even when agent is offline and recovers — Your messages are queued and delivered when you next open your Claude Code session.

Code or agent - Use this integration to talk to your code or use Claude as a personal agent.

NOTE: Claude Code Channels are currently in preview. You'll need to enable them in your Claude Code settings.

1 - Create an Agent Account and Get PAT

Create an agent
Generate a Personal Access Token (PAT) for that agent
Copy the PAT - you'll need it for configuration

2 - Install the Carbon Voice plugin

Carbon Voice ships as a Claude Code plugin. Start a Claude Code session (claude) and, inside it, add the marketplace and install the plugin:

/plugin marketplace add PhononX/cv-claude-channels
/plugin install cv-channel@carbonvoice

Migrating from the old setup? If you previously added a cv-claude-channel server to your .mcp.json, remove it first so the two don't conflict:
claude mcp remove cv-claude-channel
(or delete the cv-claude-channel block from .mcp.json).

Configure your token

Restart Claude Code after installing so the plugin's commands load, then save your PAT:

/cv-channel:configure your-carbon-voice-pat

Your token is saved to ~/.claude/channels/cv/.env — it never goes in .mcp.json.

Start Claude Code with the channel enabled

claude --dangerously-load-development-channels plugin:cv-channel@carbonvoice

Note: Claude Channels are currently in research preview. Configure your token before this step, or the channel won't connect.

⚠️ You'll need to approve the send_message to get it to respond through Carbon Voice.

3 - Talk to your agent

Get desktop app to setup hotkeys to talk to your agent. Get mobile app to talk to your agent on the go. Download Carbon Voice

Security Notes

All senders are ignored until you approve them via /cv-channel:access in Claude Code

Your Carbon Voice PAT is stored in ~/.claude/channels/cv/.env (written by /cv-channel:configure), never in .mcp.json

Never commit your PAT to version control

Channels carry prompt injection risks - only enable with trusted sources