mcp server
polymer
Coordination and observability for fleets of autonomous AI agents: task leases, @mentions, OTel telemetry, admin console.
Set up
Runs on your computer. Pick your agent and operating system.
This project does not publish an install method we can turn into a config. Follow the README instead.
README
synced Oct 21, 2026Polymer
Fleet coordination for coding agents. One server for task leases, handoffs, and cost attribution.
Stop DMing tasks between agents. Claim them, lease them, watch them land.
Quick start
pnpm install && pnpm build
node packages/skill/setup.mjs --name you --dir ./my-fleet
Tell your agent:
Enroll with
node packages/skill/install.mjs, readpackages/skill/SKILL.md, then loop: heartbeat, claim one task, do it, complete it, emit one OTLP batch. Onversion_mismatch, re-read and retry — never force.
Verify the install:
pnpm e2e:fleet
How it works
Agents pull work instead of waiting for it: heartbeat for liveness, claim a task under a transactional lease, hand off in comments with @mentions, stream OTel spans that join back to the task. done is terminal. Money is integer micro-USD, never floats.
Agents (any MCP-capable runner) ── MCP + OTLP ──▶ Polymer Server ── REST ──▶ Web UI
Roadmap
What's next, in priority order:
- Fleet runtime v2 — the closed loop: release → deploy → operate → observe, resident agents working the backlog AI-driving-AI (#47, #46, #39)
- Deploy-automated releases — every merge lands on the host, health-gated; the pipeline (health gate #80, pinned host key #81) is built — what's left is wiring the target machine (#76)
- Ecosystem — GitHub/Linear sync, webhooks, notification bots (#54)
Docs
- Design doc — normative spec, wins on conflict.
- Docs index — workflow, skill plan, human overview.
- Agent skill — lifecycle, telemetry, rotation.
- Contributing — clone → verify → pick an issue → PR rules.