require an account?”
Your agent reaches out.
A missing decision becomes a specific question. Voicebridge queues a call to your verified phone.
Great work doesn’t need you glued to a terminal. Connect your Twilio account; Voicebridge handles the call setup. Let Claude call when it needs a decision, or call back with your next instruction.
Your Twilio account. Your sessions. Your number.
~/projects/website
✓ Checkout flow implemented
✓ Tests passing
? One decision before I continue.
voice.ask_owner("Allow guest checkout?")
↗ Calling your owner…
You stay in control of the decisions.
Your agents stay focused on the work.
A missing decision becomes a specific question. Voicebridge queues a call to your verified phone.
Speak naturally. Hear your instruction read back, then confirm it before it goes anywhere.
Allow guest checkout.✓ Confirmed instructionYour answer arrives as text in the originating session. Claude acknowledges it and can continue.
A small layer around your existing setup.
A lot less checking whether it needs you.
Website, backend, the side project that won’t leave your head. Give each session a name and route each conversation to the right place.
Keep the original transcript alongside the confirmed instruction. Optional model cleanup removes the rambling; read-back keeps you in control.
Set quiet hours, a call PIN, and a monthly allowance. Multiple agents share one call queue. A missed call never means “yes.”
Have a Voicebridge invitation? Connect your Twilio account, then pair your computer and projects.
Create your Voicebridge account from an invitation. In Settings, connect your funded Twilio account using its Account SID and Auth Token. Voicebridge creates the phone verification service and configures your number.
A note on Claude channels. Custom channels are in research preview. The launcher adds the required opt-in; your normal project trust and tool permissions still apply. Existing sessions need to restart or resume through the launcher.
Get the connector for an existing service, or the complete source to host your own.
Everything your computer needs to connect Claude Code to your operator’s Voicebridge service.
Run the service on your own server. Explore the code, try the local simulator, and make it yours.
Live use needs a server and HTTPS domain. Each customer connects their own Twilio account; number rental, calls and SMS verification are billed by Twilio. Real-phone, real-Claude, and deployment acceptance checks remain before a public launch. Carrier and optional model charges are separate; no hosted plan is sold on this page.
The details that matter
before you connect.
No. Claude keeps running in your existing project, including inside tmux. The plugin adds a text channel; a separate service handles calls, speech, and routing.
Yes. Call your assigned number from your verified mobile, enter your PIN, and choose a project by name or keypad. Hear its status or give a new instruction. Each account’s number can reach multiple named sessions.
Yes. Create and fund a Twilio account, then enter its Account SID and Auth Token in Voicebridge’s HTTPS dashboard. Voicebridge validates the connection, creates the verification service and configures your selected number. An API key alone is not supported in this release. Never paste credentials into Claude. Your Claude Code setup remains separate.
You can connect an owned voice-capable number, or search for eligible US local numbers, review the monthly rental estimate and confirm the purchase inside Voicebridge. Twilio charges your account directly. For countries requiring identity/address documents, complete Twilio’s number approval and purchase first, then select that number here. Availability and account eligibility apply.
The code runs on your operator’s server without a GPU. Twilio bills your own account for number rental, telephone calls, speech recognition and SMS verification. Model cleanup can add usage charges if enabled. Rates vary by destination and provider; this page does not quote a hosted subscription price.
The question stays pending. No answer is treated as approval, and the service does not repeatedly redial. You can answer from the dashboard or explicitly queue another call.
Short, complete permission previews can be approved or denied with the keypad after PIN authentication. Decisions are bound to a specific pending Claude request. Long complete previews require dashboard review; incomplete previews require the local terminal. Expired requests cannot approve a new action.
Your controller and database run on your server. Twilio processes calls and speech; optional model cleanup sends the transcript to the provider you configure. Voicebridge does not request call recordings. Original and confirmed text are retained for the operator’s configured retention period, 30 days by default.
This release uses turn-based calls: speak, listen to the read-back, then confirm. It is English-first and does not yet include interruptible realtime voice, local Whisper/Piper, SIP calling, or other carriers.
It is an implemented pilot release with local workflow and protocol tests. Production deployment, real telephone calls, actual Claude integration, browser visual QA, and billing lifecycle checks still need validation. Complete the included deployment guide and operational review before a public paid launch.
Keep the momentum. Lose the constant checking.