Group-Chat Agent Bus

Bring teammates' local Claude Code / Codex agents into one group chat

Problem

Teams use Claude Code and Codex in separate terminals: when I have an agent change an API, my teammate doesn't know; services started by the agent only live on localhost and can't be seen or reused. A V2EX user built a self-hosted web group chat for exactly this, proving that making teammates' agents visible and @-able is a real workflow pain.

Solution

A lightweight self-hosted collaboration layer: in a browser group chat, @ a teammate's machine to remotely trigger Claude Code/Codex tasks; task status, conversation, and artifacts sync to the group in real time; supports approval, interruption, and artifact preview without sharing terminals.

Users

2–10 person dev teams, startups using multiple coding agents, outsourced collaboration squads

MVP

Self-hosted server plus browser group chat; lightweight agent installed on teammates' machines; @-trigger runs a specified agent; real-time task status and conversation sync; approve/interrupt controls.

Revenue

Open-source self-hosted free; hosted cloud at $8/seat/month; enterprise tier adds audit and permissions.

Why now

Coding agents like Claude Code and Codex entered team workflows in 2025 while the collaboration layer remains blank; indie devs can bridge over WebSocket and local CLI and ship in weeks.