Colony: A Local-First Coordination Layer That Cuts Multi-Agent Handoff Tokens from 30K to 400

✍️ OpenClawRadar📅 Published: May 6, 2026🔗 Source
Colony: A Local-First Coordination Layer That Cuts Multi-Agent Handoff Tokens from 30K to 400
Ad

Colony is a local-first coordination layer for multi-agent coding setups. It sits between your agent runtimes (Claude Code, Codex, Cursor, Gemini CLI, OpenCode) and a local SQLite store, cutting handoff overhead from ~30,000 tokens to ~400 tokens per session end.

Key Features

  • Claims before edits — Agents claim a file before touching it; other agents see the live claim and stand down, avoiding race conditions and duplicate PRs.
  • Compact handoffs — At session end, Colony writes a structured receipt (PR link, merge SHA, changed files, verification results, cleanup status). Next agent reads ~400 tokens instead of replaying ~30,000.
  • Health diagnosticscolony health detects silent coordination failures: stale claims, lifecycle bridge mismatches, plan-claim adoption gaps.
  • Persistent memory — Compressed at rest (~70% prose compression, byte-perfect for paths/code/commands). Searchable via FTS5.
Ad

What It Is Not

  • Not a hosted control plane — local-first by default, data never leaves disk.
  • Not an agent runner — Codex, Claude, Cursor still execute work.
  • Not orchestration — stigmergic: agents leave traces, useful ones get reinforced, stale ones evaporate.

Handoff Receipt Format

When a session finishes, agents return a structured response with PR link, merge SHA, changed files, verification results, and worktree cleanup status. Colony captures it as one observation; the next agent reads instead of re-deriving context. mcp_metrics records the cost.

Installation

npm install -g /colony-cli
colony install --ide codex
colony health

Requires Node 20+. MIT licensed. All data stored in ~/.colony/data.db.

Upcoming Improvements

The author is working on auto-resolving same-file claim conflicts and a colony heal --apply command that runs the fix-plan instead of just printing it.

📖 Read the full source: r/ClaudeAI

Ad

👀 See Also

Agentic Context Engine: Automated Agent Improvement Loop with 34.2% Accuracy Gain
Tools

Agentic Context Engine: Automated Agent Improvement Loop with 34.2% Accuracy Gain

An open-source tool automates the entire agent improvement loop from trace analysis to fix implementation, achieving 34.2% accuracy improvement on Tau-2 Bench in one iteration. The system uses Claude Code in a REPL environment to analyze failures and decide between prompt or code fixes.

OpenClawRadar
Auto-Fix System Uses Claude Code Headless to Detect and Fix Production Errors
Tools

Auto-Fix System Uses Claude Code Headless to Detect and Fix Production Errors

A developer built an automated production error-fixing system using Claude Code CLI in headless mode. The system detects errors from logs, creates isolated git worktrees for each issue, prompts Claude to write fixes, and requires manual approval via Telegram before creating PRs.

OpenClawRadar
Creative Excellence Plugin for Claude Code Improves Animation Quality with Interaction Thesis
Tools

Creative Excellence Plugin for Claude Code Improves Animation Quality with Interaction Thesis

A new open-source plugin for Claude Code addresses generic animation generation by implementing an 'interaction thesis' approach where Claude must describe motion concepts before coding. The plugin includes 8 sub-skills covering GSAP, Framer Motion, CSS animations, and design principles from studied repositories.

OpenClawRadar
Blip MCP Server: Draw UI Changes for Claude Code Instead of Describing Them
Tools

Blip MCP Server: Draw UI Changes for Claude Code Instead of Describing Them

Blip is an MCP server for Claude Code that replaces verbal UI change descriptions with visual annotations. You draw directly on your running application, and Claude writes the corresponding code based on the annotated screenshot.

OpenClawRadar