Loom coordination archive
The continuity problem that led to Linear-first coordination
Loom proved that agents need task ownership, checkpoints, routing, and recovery. Current CREATE SOMETHING repo work now uses Linear as the source of truth for tracked ownership, status, and evidence.
Legacy install references
Kept for historical MCP users. New CREATE SOMETHING coordination should start in Linear.
Add to claude_desktop_config.json
Settings → MCP → View raw config
codex mcp add loom
Works with any MCP client
What Loom proved
Continuity matters
Agent work needs persistent context when sessions end or hands change.
Routing needs evidence
Agent choice only matters when the task, cost, and proof surface are visible.
Progress needs receipts
A task is not done until evidence survives outside the chat window.
# Legacy MCP reference. Current repo coordination uses Linear.
# Start working (create + claim in one call)
loom work "Fix authentication bug" --agent claude-code
# Save progress (crash recovery point)
loom checkpoint "JWT validation implemented"
# Get routing recommendation
loom route lm-abc --strategy cheapest
→ Route to: gemini (score: 0.85, cost: $0.001/1k)
# Complete with evidence
loom complete lm-abc --evidence "commit abc123"How Loom compares
Different tools solve different problems
| Feature | Beads | Gas Town | Loom |
|---|---|---|---|
| Multi-agent coordination | No | No | Yes |
| Smart routing | No | Basic | Yes |
| Session memory | No | Yes | Yes |
| Crash recovery | No | Yes | Yes |
| Git sync | Yes | No | Yes |
| Ground integration | No | No | Yes |
| Cost optimization | No | No | Yes |
Legacy tool surface
These tools remain useful as design evidence. They are not the current repo task source of truth.
Manage tasks
loom_work— Start working on something right nowloom_create— Create a task for laterloom_spawn— Break a task into smaller piecesloom_ready— See what's available to work onloom_complete— Mark something done
Route work
loom_route— Get a suggestion for which agent to useloom_agents— See all your configured agentsloom_analytics— See what's worked well in the pastloom_record_execution— Help Loom learn from results
Remember context
loom_checkpoint— Save your progressloom_resume— Pick up where you left offloom_get_resume_brief— Get a summary of what happenedloom_update_context— Note what files you changed, decisions you made
Plan ahead
loom_formulas— Use workflow templatesloom_discuss— Talk through preferences before startingloom_verify_plan— Check if a plan makes sense
Use the right coordination surface for the job
Loom showed why agent work needs routing, recovery, and receipts. In this repository, Linear now owns tracked work while product pages keep Loom as historical proof of the coordination problem.