Steven's Knowledge Base

Multi-CC Architecture Research

5 min read

Multi Claude Code Architecture Research

Date: 2026-03-29

Core Concepts

tmux

  • Terminal multiplexer, manages multiple terminal sessions
  • Function: Human-to-AI communication bridge
  • 10 tmux sessions = 10 projects running simultaneously
  • Each session runs an independent Claude Code instance

Git Worktree

  • Creates isolated copies of a project for each agent
  • Function: AI’s underlying file/memory isolation
  • Each project gets its own files, memory system, CLAUDE.md
  • No cross-contamination between projects
  • Claude Code native flag: claude --worktree feature-name (v2.1.49+)

Claude Code Agent Teams

  • Built-in experimental feature (v2.1.32+)
  • Enable: CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS=1
  • Agents can message each other, share task lists
  • Works ON TOP of tmux/worktree, not a replacement

Paperclip (37K GitHub stars in 4 weeks)

  • “Company OS” for AI agents
  • Dashboard to monitor all agents: status, cost, progress
  • Per-agent budget limits + real-time token tracking
  • Supports Claude Code, Codex, Cursor, any HTTP agent
  • Analogy: Upgrade from “security guard watching 10 CCTV screens” to “boss viewing a dashboard”

Third-Party Orchestrators (Ranked by GitHub Stars)

ToolStarsLanguageWhat it does
Vibe Kanban24KRustWeb Kanban board, drag card to “In Progress” auto-launches agent
Claude Squad6.7KGoTUI dashboard, simplest to start (cs command)
Workmux1KRusttmux IS the interface, .workmux.yaml config
Uzi576GoAgent racing: same prompt, multiple agents, pick best

Architecture Decision: Steven’s Setup

Requirements

  • 3 people (Steven + 2 colleagues)
  • Up to 10 concurrent projects
  • Voice input via Telegram (no typing)
  • Single Claude Max Plan on existing VPS

Chosen: Plan A - 1 Bot per Project

Telegram:
  @project_video_bot (Video Pipeline)
  @project_web_bot (Website)
  @project_marketing_bot (Marketing)
  ... (up to 10 bots)

VPS (KVM 4, 16GB RAM):
  tmux session 1 → worktree-video → CC (with video skills)
  tmux session 2 → worktree-web → CC (with web skills)
  tmux session 3 → worktree-marketing → CC (with marketing skills)
  ...

Why Plan A?

  • Natural isolation: each project has its own Telegram chat (like how real teams use group chats)
  • Conversation history stays clean per project
  • Switching projects = switching Telegram chat (no commands needed)
  • Same workflow as real-life project management

Rejected Alternatives

  • Plan B (1 bot + commands): Can only work on 1 project at a time, not parallel
  • Plan C (1 bot + router): Chat history gets messy mixing 10 projects in 1 thread

Setup Time

  • First bot: ~30 min (figure out the flow)
  • Each additional bot: ~5-10 min (copy config, change token)
  • Total for 10: ~2 hours (can be scripted)

Each CC Instance Can:

  • Install different Skills per project
  • Spawn different sub-agents for different tasks
  • Maintain independent memory/context
  • One CC = one powerful team (not just one person)

Cost

  • 1 Claude Max Plan shared across all sessions on same VPS
  • All orchestration tools are free/open-source
  • Only cost: Claude subscription ($100-200/month depending on plan tier)

Phased Rollout Plan

PhaseWhenWhat
Phase 1When readytmux + worktree + first 2-3 bots
Phase 2After validationScale to 10 bots + Claude Squad for monitoring
Phase 3When neededAdd Paperclip for budget control + company-level management

Paperclip 深入分析

定位

“Not a chatbot — agents have jobs, not chat windows.” Paperclip 係管理平台，唔係溝通平台。你同 agent 講嘢仍然要透過 Telegram / Terminal。

核心功能

  • 公司架構（CEO → 部門 → 員工 org chart）
  • 治理系統（邊個 agent 有權做咩）
  • 每個 agent 月度預算（超支自動停）
  • Audit trail（每個決策都有記錄）
  • Plugin 系統（第三方擴展 SDK）
  • Heartbeat 排班系統（agent 定時起身做嘢）
  • Approval gates（等老闆批准先繼續）

Agent 運作模式

Agent 係「排班工人」：

  1. 定時起身（heartbeat interval）
  2. 拎任務（pull from task queue）
  3. 做嘢（execute against tools）
  4. 記錄（log everything）
  5. 瞓覺（sleep until next heartbeat）

支援嘅 Agent 類型

Claude Code, Codex, Cursor, OpenCode, Gemini CLI, Bash scripts, HTTP webhooks

為什麼「重」？

Paperclip 設計俾「零人公司」用，好似 SAP ERP：

  • org chart → 3 人團隊唔需要
  • 治理系統 → 小團隊唔需要
  • audit trail → 小團隊唔需要
  • plugin SDK → 小團隊唔需要

適合用 Paperclip 嘅場景

  • 10+ agents 同時跑
  • 需要嚴格預算控制
  • 需要合規/核數記錄
  • 團隊 5+ 人

唔需要 Paperclip 嘅替代方案

  • Claude Squad（6.7K stars）— 輕量 TUI dashboard，cs 指令搞掂
  • 自製 mission-control.js — 100-200 行 code，每 30 秒掃描 tmux sessions，顯示狀態
  • Vibe Kanban — 網頁版 Kanban board

Steven 嘅結論

而家用簡單版（Claude Squad 或自製 dashboard），日後需要先升級 Paperclip。

Mission Control 概念 vs 實現

「Mission Control」= 概念（監察所有 agent 嘅 dashboard） 具體實現有好多種：

工具類型複雜度
Paperclip完整公司 OS重
Claude SquadTUI dashboard輕
Vibe KanbanWeb Kanban board中
自製 mission-control.js自訂 web dashboard輕

好似「CRM」係概念，Salesforce / HubSpot / Excel 都係 CRM 嘅實現。

Key Resources

Graph View

Backlinks