We build a voice AI co-worker that lives inside web apps, and we build it with coding agents like Claude Code. The problem is that voice isn't something a coding agent can test by itself, because it can't hear. It writes the change and runs the tests, but it has no idea if the voice still works. And for voice AI it's not only about whether sound comes out or the transcript is right. It also has to get what the user wants and call the right function, so the thing actually happens in the app, even when someone's tapping on the desk or the network drops. So we built a twin. It role-plays a user with a goal and talks through a fake microphone into the real voice pipeline. The whole session comes back as text the coding agent can read. A test only passes if the right action really happened in the app, not because the answer sounded right. A run costs one or two cents, so the coding agent can run it after every change. I'll run it live and show what it caught, for example a reconnect that killed the session 11 seconds in, which in the end was triggered by our own test tool. I'll also show what it can't catch, like the day our German sessions went silent while every transcript looked fine. Hopefully you leave with a way to test your own voice features without listening to every change.
Ebrahim(Ebi), has shipped product across three continents, director of engineering at a Middle East company he helped take to IPO, an engineering manager in Germany, a staff engineer in New York, then NearDynamics, a voice AI venture he built and saw through an exit. Now he's building Coworkkit, a batteries-included AI co-worker any app can drop in and ship. What excites him most is the faceless app that serves one UX rendered for each user.
