claudeClayrune (CR) is the open-source mission control for Claude Code. Spin up parallel agents across every project, run a hivemind that decomposes its own goals, and schedule work that fires while you sleep — then tap into the whole operation from your phone like a group chat with your AI workers.
Clayrune ships its own attested Cloudflared tunnel and a mobile UI that feels less like an admin panel and more like a messaging app — a chat list of your projects, drill-down conversations, unread badges, paste-screenshots-into-prompts. Your fleet is one notification away.
Ten parallel claude sessions in ten terminals is not an operation. Clayrune (CR) turns that mess into a coordinated fleet — locally, on your machine, with one Flask process and one HTML file.
You forget which agent is on which branch. Plans scroll off-screen. You spawn "just one more" and lose context two hours later. Costs blur. Your phone can't help you. Cloud agents like Devin lock you into someone else's runtime at someone else's price.
Every project gets a tile. Every tile gets agents. Plans, backlogs, GitHub Issues, MCP servers, skills, and per-project memory all live where they belong. Streaming output, hivemind orchestration, scheduled runs — and a tunnel that lets you tap "deploy" from a phone in the airport. localhost:5199 · MIT · yours.
Every project gets its own sandbox — its own memory, backlog, skills, MCP servers, accent color, conventions. Nothing leaks across by accident. When you do want them to talk — a hivemind goal that spans repos, a skill shared with the whole fleet, a shared rule book — the seams are explicit, not implicit.
One project's MEMORY.md, skills, and MCP servers never leak into another's context. No accidental cross-talk.
Authored a skill in project A that should help everywhere? Promote it once — it appears in every project's pack.
One goal, workers spawned across repos. Coordinated by the orchestrator, observable from the same chat list.
data/SHARED_RULES.md + engram memory layer give the fleet a common language without giving up per-project boundaries.
┌──────────────────────────────────────────────────────────────────┐ │ YOUR DEVICE ─── laptop · phone via clayrune.io tunnel │ ├──────────────────────────────────────────────────────────────────┤ │ ┌─ static/index.html → vanilla JS · no build · no framework │ │ │ • tile board · multi-window · stream viewer │ │ │ • SSE client · plan modal · tour engine │ │ └──────── ↑↓ HTTP + Server-Sent Events ────────┐ │ │ │ │ │ ┌─ server.py (Flask · port 5199) │ │ │ │ • REST API · SSE streams · static │ │ │ │ • github_sync.py (bidir issue sync) │ │ │ └─── subprocess.Popen ───┐ │ │ │ ↓ │ │ ┌─ claude (CLI subprocess) │ │ │ • --output-format stream-json │ │ │ • mode A: per-turn | mode B: persistent stdin │ │ └─── reads / writes ───────→ data/projects/*.json │ │ data/uploads/* │ │ data/SHARED_RULES.md │ └──────────────────────────────────────────────────────────────────┘
# 1. download zip from Releases # 2. unzip anywhere # 3. double-click MissionControl.exe → MissionControl-Windows.zip → MissionControl.exe → http://localhost:5199 // also opens in browser # Claude CLI auto-installs on first launch # if it isn't already on your system.
$ git clone https://github.com/ronle/mission-control.git $ cd mission-control $ pip install -r requirements.txt # native window (pywebview) $ python app.py # or browser-only $ python server.py $ open http://localhost:5199
MIT-licensed. No framework lock-in. No build pipeline. Bug? Open an issue. Idea? Open a PR. Want to wire up a new connector — Linear, Notion, Slack? The Flask backend is small and friendly. The proprietary platform binding (mc_remote + mc_tunnel) is a thin shell over an MIT seam — implement the contract and plug in your own.
Forged in production by a working operator who needed it. It's better when more hands shape it.