Multi-operator Claude Code: Hub-based architecture for multi-agent sessions

A Reddit user shared their architecture for scaling Claude Code beyond single-user sessions. The system uses a hub-and-spoke model: a central hub (self-hosted on Docker Hub or hosted) with four interface types.

Architecture overview

• Hub – central coordination point, available on Docker Hub for self-hosting.
• One-line MCP client – lightweight integration via Model Context Protocol.
• CLI – direct command-line access to the hub.
• Headless workers in Docker – containerized agents that can spawn more containers (agent calling agent).
• Small desktop supervisor – GUI for monitoring and controlling sessions.

What you get

• Multiple people attached to the same Claude Code session, watching the agent think in real time.
• Sessions that can route subtasks to each other across different repositories.
• Headless Claude instances in containers spawning child containers – enabling recursive agent workflows.
• Watch and intervene from a browser tab on your phone.

Details

The hub is the central component. The MCP client is a single-line integration. The desktop supervisor provides a lightweight UI for monitoring. All workers run headless in Docker, and they can spawn additional containers to offload subtasks. The system allows session routing across repos, so a complex multi-repo task can be broken up and delegated.

Repos and walkthrough are available on GitHub: https://github.com/clawborrator

This is essentially a plumbing layer for multi-operator Claude Code. If you're already using Claude Code and hitting the limits of single-user sessions, this architecture gives you a concrete pattern for scaling out.