How to set up voice chat for OpenCode
Set up a voice huddle in OpenCode so you can talk through a plan with your agent before it starts working.
Posted by
Related reading
How to set up follow-up reminders for your AI agents
Set up Claude, Codex, OpenCode, or another AI agent to email you when a follow-up needs to happen later.
How do you automatically keep track of quotes you need to follow up on?
How to track sent quotes, schedule follow-ups, and stop reminders when customers reply.
How to build an AI to monitor budget for your client projects
A practical workflow to monitor project budget health weekly and catch margin drift early with AI.
Here's how to add voice chat to OpenCode in a few minutes. I use OpenCode for a lot of my work, including Pipa, and sometimes typing the whole brief is the annoying part. I already know the shape of what I want. I just need to talk it out.
Voice is especially useful right before you ask an agent to do a bunch of work. Planning, sorting priorities, naming the thing you actually want, catching the weird constraints. All of that is easier out loud.
The short version
Go to the Pipa tools page, copy the Voice huddles prompt, and paste it into OpenCode. OpenCode installs the skill and gives you a huddle link. After that, you can usually just say: "Please start a huddle."
If you want to watch the exact flow, Watch the YouTube tutorial here.
What this adds
The setup adds a live voice huddle to your OpenCode session. You get a link, join the room, and talk to the agent instead of trying to cram a half-formed plan into one perfect prompt.
I mostly use it before a work session starts. If I am about to hand over a feature, a launch checklist, or a messy pile of priorities, I want a quick conversation first. It saves me from writing a giant prompt that still somehow misses the point.
Why voice helps before agent work
Typing is great when you already know exactly what you want. Voice is better when the task is still fuzzy. You can say the messy version, correct yourself, add the context you forgot, and hear the agent reflect the plan back before it starts changing things.
That little pause helps. The agent gets a better brief. You get a chance to notice when the plan sounds wrong before it becomes a diff you have to unwind.
Set it up once
Start on the Pipa tools page. The prompt there tells OpenCode what to install and how to start the first huddle.
- Go to usepipa.com/tools.
- Find Voice huddles.
- Copy the prompt.
- Paste it into OpenCode.
- Let OpenCode install the Pipa Huddle skill.
- Open the link it gives you.
- Talk through the work.
- Come back to OpenCode when you are ready.
Copy the prompt from the tools page
I would copy it from the Pipa tools page. That way you get the current install command instead of whatever you saved in an old note three weeks ago.
Step 1. Copy the prompt
Open usepipa.com/tools and scroll to Voice huddles. Copy the prompt.
The prompt includes the install command and the instructions for starting the first huddle, so you do not have to remember any of it.
Step 2. Paste it into OpenCode
Paste the prompt into your OpenCode session. It will install the Pipa Huddle skill and start the setup.
This is the only fiddly part. Once the skill is installed, starting a huddle later is much less dramatic.
Step 3. Open the huddle link
When setup finishes, OpenCode gives you a link. Open it in your browser and join the huddle.
In the video, the room opens and the agent says hi. From there, it is just a conversation.
Step 4. Talk before the agent works
I would use this before the agent starts working, not after it has already gone off in the wrong direction. Say what matters. Say what you do not want. Let the agent repeat the plan back.
For example, you might say:
Please start a huddle so we can talk through this feature before you implement it.
The point is not to make the huddle fancy. It is to get from vague intent to a plan you actually trust.
Step 5. Start another one later
After the first setup, you do not need to go back through the whole thing. Just ask OpenCode to start a huddle.
Please start a huddle.
It will read the skill instructions and give you a new link.
When I would use this
Use voice when the typed prompt is starting to feel like a tiny legal contract. If you are over-explaining, backspacing, and trying to make the agent understand six caveats at once, it might be a huddle.
- You need to decide what to build.
- The backlog is messy and you need to pick a lane.
- There is business context the agent will not infer from the files.
- You want to talk through risk before code changes.
- You are shaping an automation and the first version is still fuzzy.
The flow
It ends up being pretty simple:
- Copy the Voice huddles prompt from Pipa tools.
- Paste it into OpenCode.
- Let OpenCode install the skill.
- Open the huddle link.
- Talk through the work.
- Go back to OpenCode with a better plan.
FAQ
Do I need to install the skill every time?
No. Install it once. After that, ask OpenCode to start a huddle.
Does this only work with OpenCode?
This video uses OpenCode because that is what I use. The same idea can work anywhere an agent can install and use skills, but the exact steps depend on your setup.
What should I use voice chat for?
Planning. Priorities. Talking through a weird edge case before the agent starts making changes. If you already have one precise command, type it.
Where is the skill source?
The skill lives in the Pipa skills repo: pipa-huddle-beta.
Set up OpenCode voice chat
If you want to try it, copy the Voice huddles prompt from usepipa.com/tools, paste it into OpenCode, and start with a low-stakes demo huddle. Once that works, use it the next time typing the plan feels more annoying than just saying it.