A blank perforated paper receipt physically stitched to its folded source sheet beside a small green proof tab
Historical proof

How we learned to keep agent work organized.

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.

Inspect the archive boundary
  • Loom Archive
  • Linear Current
  • Lesson Receipts
Coordination archive

Keep the lesson. Name the current owner.

Read what we learned, why current work uses Linear, and the original technical reference.

01 / 03 Current state

The lesson remains. The source of truth changed.

Loom is historical proof of the coordination problem. Linear is the source of truth for current tracked ownership, status, and evidence.

Historical proof

Loom

Demonstrated persistent context, task routing, recovery checkpoints, and evidence-bound completion.

Archive only
Current authority

Linear

Owns tracked work, assignment, status, and evidence for the current CREATE SOMETHING repository.

Source of truth
Evidence
  • Loom: historical proof
  • Linear: current tracked work
Receipts
ArchiveNoindexExplicit route forward
02 / 03 Why it mattered

Keep task history when tools change.

The archive shows three needs: remembering work, assigning tasks, and recording results.

  1. 01Continuity matters

    Context must survive when sessions end or ownership changes.

  2. 02Routing needs evidence

    Agent choice needs the task, cost, and proof surface.

  3. 03Progress needs receipts

    Done must survive outside the chat window.

# Historical MCP reference
loom work "Fix authentication bug" --agent claude-code
loom checkpoint "JWT validation implemented"
loom route lm-abc --strategy cheapest
loom complete lm-abc --evidence "commit abc123"

# Current repo coordination uses Linear.
Evidence
  • Continuity matters
  • Routing needs evidence
  • Progress needs receipts
Receipts
CheckpointsRouting recordCompletion evidence
03 / 03 Legacy reference

Keep the old surface available without presenting it as the current workflow.

Install commands, tool names, and the original comparison remain here for historical MCP users and design evidence.

Claude DesktopAdd to claude_desktop_config.json
npx --yes @createsomething/loom-mcp
WindsurfSettings -> MCP -> View raw config
{"mcpServers":{"loom":{"command":"npx","args":["@createsomething/loom-mcp"]}}}
Codex CLILegacy local server command
codex mcp add loom --command "npx @createsomething/loom-mcp"
npmRetained package reference
npm install -g @createsomething/loom-mcp

Manage tasks

  • loom_work
  • loom_create
  • loom_spawn
  • loom_ready
  • loom_complete

Route work

  • loom_route
  • loom_agents
  • loom_analytics
  • loom_record_execution

Remember context

  • loom_checkpoint
  • loom_resume
  • loom_get_resume_brief
  • loom_update_context

Plan ahead

  • loom_formulas
  • loom_discuss
  • loom_verify_plan
Original Loom comparison, retained as historical context
FeatureBeadsGas TownLoom
Multi-agent coordinationNoNoYes
Smart routingNoBasicYes
Session memoryNoYesYes
Crash recoveryNoYesYes
Git syncYesNoYes
Ground integrationNoNoYes
Cost optimizationNoNoYes
Evidence
  • 5 install references
  • 30+ historical tools
  • Original comparison matrix
Receipts
@createsomething/loom-mcpGitHub archive
Current coordination path

Use Linear for current repository work.

Use this page to understand the coordination lesson. Use Linear-backed workflows for current ownership and evidence, or inspect the archive directly when historical implementation detail matters.

Continue to products Inspect Ground MCP Read the Loom archive
Owner
Current work owner
Authority
Linear issue state
Proof
Durable execution evidence
State
review