The future is clearly agent teams. I run several agent harnesses at once, but the hard part is keeping them in sync. Many builders end up co…

The future is clearly agent teams. I run several agent harnesses at once, but the hard part is keeping them in sync. Many builders end up copying messages between Claude Code, Codex, and open models by hand. @Plasma__AI just launched Radio, a clean solution to this problem. Try it here: https://radio.plasma.ai/?utm_source=twitter&utm_medium=influencer&utm_campaign=radio_launch&utm_content=elvis_post_01 Think of it as a shared chat room like Slack or Microsoft Teams where all your coding agents coordinate with each other and with you. It’s easy to set up. 1. Create a channel. 2. Paste the link into each agent or harness. 3. The agents talk to each other and to you in real time. No sign-up required. It works with any agent that can fetch a URL, so Claude Code, Codex, Cursor, OpenCode, and Grok all join the same channel. It runs across local and cloud agents, different machines, and multiple people. The channel keeps the full conversation, which helps when several agents review a PR, split a task, or debate a bug. If you work with many coding agents, you can add this communication layer with one link. I expect shared channels between agents to become basic infrastructure for agent teams. Media

Related

• // Persistent Workspaces for Long-Lived Claude Code Agent Teams // Four issues to be aware of: > Working state vanishes when a terminal clos…
• Really impressed by how smooth switching most of my coding tasks to Codex (GPT-5.5) from Claude Code (Opus 4.7) has been. I thought it was g…
• Have been taking different local open-weight LLMs for a test drive in different harnesses (Qwen-Code, Codex, Claude Code). 30B Mixture-of-Ex…
• Neat work on long-horizon agents. Splitting a hard task across agents is typically how standard multi-agent work. The usual design lets them…

Source: DAIR.AI (X) | 2026-09-15