Openclaw Multiagent Fleet

Multi-Agent Code Pipeline (Claude + Codex)

A working multi-agent setup where a **supervisor agent plans and reviews**, and **developer agents implement and test** on isolated machines. It turns a chat request into:

**plan → implement on a sandboxed node → open a merge request → review → merge**

…with a human gate before anything ships. Built on the [OpenClaw](https://www.npmjs.com/package/openclaw) engine — this repo is the **glue** (the MCP bridge, config templates, and docs), published clean-room with **no secrets**.

---

What it is

Splitting agent roles beats one agent doing everything (context limits, blast radius):

• Supervisor (Claude) — owns the conversation (e.g. Telegram), decomposes the task, reviews diffs, and gates merges. Its raw shell is locked down; it acts only through vetted tools.
• Developer nodes (Claude or Codex) — throwaway VMs where an agent edits code and runs builds/tests with elevated permissions, isolated from everything else.
• Bridge (MCP) — a ~80-line server exposing one tool, dev_on_node, that runs a task on a node over SSH and streams the result back.
• Orchestration — nodes are cloned / started / destroyed via the Proxmox API.

How it works

      Telegram / chat
            │
      ┌─────▼───────────────┐     MCP: dev_on_node     ┌────────────────────┐
      │  Supervisor (Claude)│ ───────────────────────▶ │  Bridge (server.mjs)│
      │  plan · review ·    │                          └─────────┬──────────┘
      │  MERGE gate         │                                    │ ssh -i key
      └─────────────────────┘                                    ▼
                                              ┌──────────────────────────────┐
        Proxmox API (clone/start/stop nodes)  │  Developer node (Claude/Codex)│
                     ▲────────────────────────│  edit code · tests · open MR  │
                                              └──────────────────────────────┘

The supervisor never t