Run all your coding agents at once and talk to them. They ask out loud, you answer by voice, nothing merges without your review. Works with Claude Code, Codex, Cursor and more, on the plans you already have.
Talk to your coding agents and hear them talk back. SKI runs Claude Code, Codex, Cursor, OpenCode, Antigravity and pi side by side on your Mac, and tells you the moment one needs you.
Thanks a lot for supporting us and for your feedback with SKI.
We have taken in your feedback and requests. We have transformed SKI into a voice-first coding harness, with enhancements to support multi modal inputs in realtime
Supports 85+ languages: You could speak to your coding agents in languages that you are comfortable in, and the agent will talk to you in the same language as well.
Prompt processing: It runs your audio and brings in your thoughts as a proper prompt, refined for most agents (with optional approval)
All agents in one UI: Brings in all agents into a single UI, with most commonly used tools for coding. Switch sessions and agents by voice.
Chained agents: With a single voice command, you can give the agent a chained task. For example, ask Opus 5.5 to plan, and then to hand it over to GPT Luna to code and then to Fable for review, in just a simple voice command
Intelligent router: With "One chat for all" turned on, you can just talk to a single agent and it will intelligently route to sessions (with optional approval)
Expressive voice: A more human-like, low latency voice for each sessions with 28+ voices
First of all, a huge thank you to this amazing community. Your support, curiosity, and willingness to try new things mean the world to us, and we're genuinely grateful to have you along on this journey.
@rahul_saji007 SKI has undergone significant changes in its core fundamentals. While the first version of SKI was completely local, with slightly robotic voice with high latency, the new version has cloud components with more realistic voice at low latency. The new version is also intelligent and has improved in the user experience. We also have additional grounded voice-specific harness tools inside SKI, which makes the voice experience better.
congrats on the launch anand. the worktree per chat is the part that got me, i always lose track which agent touched what. one thing im curious, when the agent reads a long change back by voice how do you keep it short enough that i still really review it and not just say yes
The voice agent usually summarizes the changes in brief audio duration. If you want it to speak more or explain, it will. And it will bring up visual webpages and explain so that you can stay focused if needed. You can customize the behaviour as you like.
@anand_balakrishnan5 that makes sense. i am still curious about the voice part, is the read back short by default or do you have to ask for the short one
Running four different coding agents at once and hearing about it the second one needs me is the right shape for this, since the real cost is babysitting tabs and never knowing when to switch back.
@karimbenkeroum Yes. And you can just work across agents (not just sessions). For instance, in Claude Code, all agents are models from Anthropic. In SKI, you could let different agents run together, side by side, and even let agents hand over their work to the next agent by voice.
git worktrees solve the file-collision problem between agents, but what about state outside git - a shared dev server, a database migration one agent runs mid-task while another assumes the old schema. with 3-4 agents going at once that's the conflict I'd actually worry about, not two agents editing the same file.
@rahul_saji007 SKI has undergone significant changes in its core fundamentals. While the first version of SKI was completely local, with slightly robotic voice with high latency, the new version has cloud components with more realistic voice at low latency. The new version is also intelligent and has improved in the user experience. We also have additional grounded voice-specific harness tools inside SKI, which makes the voice experience better.
Quick demo: SKI isn't only for code. I described a lounge chair out loud, and Claude Code modeled it in SketchUp step by step.
Hey @anand_balakrishnan5 and team. Lovely products and a great launch video; absolutely loved that dumb dino😆.
Anyway, as said product seems promising, would surely give it a try.
Congrats on launch & best wishes ahead :)
@whatshivamdo Thank you, Shivam! Glad you liked it, we are so happy :)
When you try it, tell us how it works for you.
congrats on the launch anand. the worktree per chat is the part that got me, i always lose track which agent touched what. one thing im curious, when the agent reads a long change back by voice how do you keep it short enough that i still really review it and not just say yes
@agshin_rajabov Thank you for checking out SKI.
The voice agent usually summarizes the changes in brief audio duration. If you want it to speak more or explain, it will. And it will bring up visual webpages and explain so that you can stay focused if needed. You can customize the behaviour as you like.
@agshin_rajabov Thanks Agshin! Glad the worktree per chat clicked. Knowing which agent touched what was one of the first things we wanted to fix.
@anand_balakrishnan5 that makes sense. i am still curious about the voice part, is the read back short by default or do you have to ask for the short one
Running four different coding agents at once and hearing about it the second one needs me is the right shape for this, since the real cost is babysitting tabs and never knowing when to switch back.
@karimbenkeroum Yes. And you can just work across agents (not just sessions). For instance, in Claude Code, all agents are models from Anthropic. In SKI, you could let different agents run together, side by side, and even let agents hand over their work to the next agent by voice.
Please try it out and let us know your feedback.
git worktrees solve the file-collision problem between agents, but what about state outside git - a shared dev server, a database migration one agent runs mid-task while another assumes the old schema. with 3-4 agents going at once that's the conflict I'd actually worry about, not two agents editing the same file.