Loom Control Plane

Loom is the control-plane layer that sits on top of a project workspace and orchestrates multi-agent work through a real-time kanban board, runner-aware execution, generated project context, and VSCode entrypoints.

This repository can now be used in two ways:

1. npx bootstrap CLI for global setup and terminal-connected startup.
2. raw overlay install for direct file copy into a target workspace.

npx Bootstrap

From any terminal:

npx github:<owner>/loom-control-plane init

The CLI will:

• detect local codex and claude CLIs
• ask which project directory to wire up
• ask how you want to run Loom
• optionally wipe old Loom board/cards/cache
• install the overlay into the target workspace
• generate context
• optionally start the board in the current terminal

You can also clear old state directly:

npx github:<owner>/loom-control-plane clean-state --yes

Overlay Flow

The raw overlay flow is:

1. Clone this repo on any machine.
2. Copy its Loom files into a target project workspace.
3. Run Loom from that project root so the board, agents, and generated context operate against the real codebase.

Included

• tools/kanban-v3.cjs, tools/kanban-v3.html
  • Real-time board, task CRUD, SSE updates, runner queue, pair workflow orchestration
• tools/loom-mobile.html
  • Phone-first remote surface with live status, active tasks, and chat
• tools/loom-runner.cjs
  • Normalized Claude CLI and Codex CLI runner bridge
• tools/loom-context.cjs
  • Generated project context builder from live workspace state
• tools/loom-vscode/
  • VSCode local extension scaffold for starting and opening Loom inside the editor
• .loom/reed.yaml
  • Governance source for lanes, boundaries, and inspect gates
• .claude/agents/
  • Agent prompt scaffold
• ops/loom/
  • PM2, proxy, and quick-tunnel helpers for remote usage

Install Into A Project

From this repo root:

bash scripts/install-into-workspace.sh /absolute/path/to/your-project

That copies the Loom overlay into the target workspace:

• .claude/agents/
• .loom/reed.yaml
• tools/kanban-v3.cjs
• tools/kanban-v3.html
• tools/loom-mobile.html
• tools/loom-context.cjs
• tools/loom-runner.cjs
• ops/loom/
• tools/loom-vscode/
• docs/loom-vscode.html

Run

Inside the target project root:

node tools/loom-context.cjs
node tools/kanban-v3.cjs

Then open http://127.0.0.1:4141.

For remote/mobile usage:

cp .env.example .env
npm run loom:remote

Then open:

• http://127.0.0.1:4141/
• http://127.0.0.1:4141/mobile

VSCode Flow

Load tools/loom-vscode/ as a local extension and use:

• Loom: Start Control Plane
• Loom: Open Board
• Loom: Open Activity Log
• Loom: Refresh Context

Pair Workflow

Loom supports a parent-task fanout model where one task becomes:

• one implementation task
• one analysis task
• two reciprocal review tasks

Codex and Claude can run in parallel when assigned different runners, and the review tasks auto-unblock once both worker tasks reach review-ready state.

Notes

• Generated context from .loom/context/generated-project-context.md is injected before the legacy _project-context.md.
• Runtime truth from the control plane overrides stale absolute paths or ports found in old prompt files.
• Task state is stored in ~/.loom/tasks with legacy migration from ~/.claude/tasks.
• Basic auth can be configured from the board UI and is persisted in ~/.loom/settings.json.