Cobra Comms

The problem it actually solves

You start a long job, wander off, and come back nine minutes later to find it stopped eight minutes ago waiting for you to answer something. The screen knew. Nothing told you.

It answers the second you hit send

A short line fires before any work starts, so you know the machine heard you and did not just freeze.

It says what it found, not what it typed

Meaning, never mechanics. Not the file it opened, the question it was asking. No paths, no camelCase, no line numbers.

Failures are always spoken

If you walked away, a broken deploy is the one thing you need to hear about. It never swallows those quietly.

Pick who it sounds like

Personalities are single files with a brief and a pool of lines. Copy one, change it, drop it in. The brief is written for the model, not the speech engine, so plain English is exactly right.

Register	Sounds like
dry	Understated and competent. Says what happened and why it matters. No profanity. The default.
hype	Enthusiastic and fast. Treats every task like the good part of the day. Mild swearing.
menace	Sarcastic and sweary, permanently unimpressed with your dependencies. Never with you.
flirt	All of menace, plus quietly attached to you and absolutely never going to admit it.

One rule holds across all of them, and it is the difference between funny and tiring. The sarcasm aims at the code, never at you, and never at being asked. A voice that treats you as an interruption stops being fun by the third day.

Three voices, and it falls down them on its own

Tier	What you get
ElevenLabs	Best by a distance, and the only one that performs inline audio tags, so a sigh is acted rather than read out as the word. Needs your own key. Rendered lines are cached forever, so repeats cost nothing.
edge-tts	Free, no key, no account, genuinely good. The default.
Windows SAPI	Built into the OS. Not good. But it means the plugin talks the second you install it, on any machine, with nothing set up.

Then link your phone

Your computer has to be on for this half

Your phone is a remote control, not a host. There is no copy of your machine in the cloud. The sessions run on your actual computer, in your actual project folder, which is the whole point, and it means that computer needs to be powered on, awake, online, and running the bridge while you are out.

If it sleeps or the bridge window is closed, your phone sees nothing until you start it again. On a laptop, closing the lid is enough to end it, so the setup offers to stop that happening while you are plugged in.

Remote Control is a built in Claude Code feature and this does not replace it. It exists because four things silently stop it starting, and not one of them tells you why.

An API key in your environment shadows your subscription. Remote Control refuses API key auth, and the refusal does not say that is what happened.
Your home directory can never be trusted. That is deliberate, and it means the bridge cannot start where most people try it first.
The build on your PATH may not have the command at all. A stale global install looks identical until you need it.
On a laptop, closing the lid kills the bridge. Your sleep timeouts have nothing to do with it.

It checks all four, fixes what it can, and walks you up to the two steps that are gated on a human on purpose: accepting a workspace trust dialog, and being signed in with a subscription. Then your phone starts sessions on your machine, in a real project folder, with your files.

Burn the window while you are at work

Before: you collect ideas all day, get home, and hand the whole list over at once. That starts a five hour window at the exact moment your own evening starts. A few hours later the work is done and you are locked out until one in the morning, which is a fine time to be locked out of nothing, because you are asleep.

The window you spend should be the one you were at work for anyway.

With the bridge running, the ideas get built between tasks, from your phone, in the real project. That window opens and closes while you are on the clock. You walk in the door at zero percent with a full one ahead of you, and the thing you thought of at ten in the morning is already done.

You clocked out. You should not have homework.

The quiet part

A voice is useless at best and embarrassing at worst when you are not in the room. So when a prompt arrives from your phone or a browser instead of the desk, the machine stays silent. Remote sessions report themselves differently from local ones, and the voice checks before it opens its mouth.

The tool that lets you work from anywhere does not leave your machine talking to an empty room.