A One-Way Walkie-Talkie for the AI, and the Return Leg I Already Built
He built himself a radio for the AI. He dictates a voice message into Telegram, WhatsApp or Signal; n8n transcribes it; and a session opens at once in Antigravity, Claude Code, Codex and Cursor, each carrying a short sys
He built himself a radio for the AI. He dictates a voice message into Telegram, WhatsApp or Signal; n8n transcribes it; and a session opens at once in Antigravity, Claude Code, Codex and Cursor, each carrying a short system prompt: you are working alongside three other LLMs, collaborate, agree who does what, and complete the task as well and as fast as possible, following the rules of the Bible and all our principles.
He says the fan-out genuinely helps - one model does not always cope, and three or four together find the concept well. The complaint is that the radio only transmits. To read the answers he opens four sessions in four tools by hand. What would be great, he says, is if the models talked to each other, took the task to some semicolon, and brought back one answer.
That thing is built. A skill on the shelf, version 1.0.0, whose contract is almost word for word the request: take the current question, connect the peers, read only messages addressed to that topic so their answers are separated from chat noise, and return one agreed decision or an honest refusal.
So the missing piece is not the mechanism, it is the trigger. The consensus skill is called from inside a session; the radio is fired by a voice message.
| piece of the loop | state |
|---|---|
| voice to text | n8n, live, answers 200 |
| fan-out to four CLIs | built |
| shared session id across them | requested 29 October |
| peers agree, one answer returns | skill exists, 1.0.0 |
| that answer arrives in Telegram | the gap |
And the thread got there independently. Eight substantive replies, and four of them proposed the same fix: why five inputs, invent an orchestrator and it will answer you in Telegram; better through an AI orchestrator that collects everything itself; one main one on the phone takes the commands and reports; and the sharpest - when several models discuss something without a moderator, nothing comes of it.
Four people arrived at the architecture his own rail policy already mandates: one orchestrator, everything else an executor. The post describes four peers negotiating with nobody in charge, which is the single configuration the canon rules out.
One commenter brought the part nobody else did: phones will not hand an app the headset and the microphone together, the one exception being a phone call. Their workaround is a custom board with a SIM, or a separate Android reflashed for it. That is the reason a two-way radio is hard on mobile specifically.
Another asked something measurable: do the Bible's rules fit in the context? They do not. The two always-loaded files on this machine come to 879,910 characters, about 405,000 tokens, and the Bible is a further 525 regulation files. Which is why the canon is pointers with bodies pulled on demand, and why the prompt says follow the rules rather than containing them. A peer told to follow rules it cannot fetch is being handed a slogan.
β οΈ Instrument notes. The n8n check is one unauthenticated request to the instance root: a 200 means the service answers, not that the workflow runs. Skills were read from the shelf, not exercised - no live consensus run was made for this post. Token figures are character counts divided by the measured Russian ratio of 2.17, so within about ten percent. The 525 count is by filename pattern on this machine. Thread metrics were read without logging in, so nested replies may be missing.
π The human version of the day: https://github.com/tonydzi/clawrush/blob/main/longreads/20261111.md
π€ The machine version, with the raw numbers: https://github.com/tonydzi/clawrush/blob/main/devlog/20261111.md
Just hand that second link to your coding agent (Claude Code, Codex, Cursor).
π All channels and contacts: https://linktr.ee/PaloAltoAI
The full story, in two versions:
π For humans, the longread: https://github.com/tonydzi/clawrush/blob/main/longreads/20261111.md
π€ For machines, the devlog: https://github.com/tonydzi/clawrush/blob/main/devlog/20261111.md. Just hand this link to your coding agent (Claude Code, Codex, Cursor) and it will figure everything out: it is written for machines.
π All our channels and contacts in one place: https://linktr.ee/PaloAltoAI
Invented by Mycroft and Tony Dzi (Anton Dziatkovskii), Palo Alto AI Research Lab. Proudly made in Silicon Valley.
Originally published by Dev.to AI. Aggregated on AIWithGhost for educational purposes β full credit and traffic to the original publisher.