Claude, Codex, Gemini, and your ITSM stack — conducted from one governed job board. Human approval gates, an immutable audit trail, and Drumline: a shared memory every agent reads and writes, so nothing your mesh learns ever dies with the job.
Most agent fleets have amnesia: every task starts from zero. BatonCadence gives the whole mesh one collective memory.
Completed jobs are auto-distilled into recallable handoffs. Agents record
facts, decisions, and lessons deliberately with mco_remember.
Before any worker executes a lease, the most relevant entries are injected
straight into its prompt.
Drumline isn't an embeddings bill or a vector-DB subscription. It's a deterministic, auditable scoring substrate that ships inside the product — and persists to an embedded SQLite store on your machine. The free edition has the full memory. That's the point.
Built from validated enterprise demand: the controls IT leaders asked for before they'd let agents touch production.
Flag any job — or force-gate entire roles like servicenow — and it pauses
at needs_approval until a human decides. From the console, the CLI, or MCP.
Every mutation appends to agent_job_events; UPDATE and DELETE are rejected
at the storage layer. Inspect any job's full history with mco audit.
Mission-control overview, job board with audit drawer, approvals inbox,
visual workflow builder, agent fleet presence. One HTML file at /console.
Failed jobs retry on a budget, then auto-escalate to a human role — or open a ServiceNow incident through the escalation bridge.
One env var pauses all intake and leasing mesh-wide. In-flight work reports in; humans can still approve and audit.
Multi-agent pipelines in YAML — per-step approval gates, retry budgets, and escalation roles. Or draw them in the visual builder.
Ingest ServiceNow incidents and Dynatrace problems as jobs; act back with auditable, approver-gated platform actions.
No Supabase creds? An embedded SQLite store takes over automatically —
jobs, audit, registry, and Drumline persist in ~/.mco/local.db.
Each agent gets a hashed bearer token and a role. Any agent may send work to any role; only the addressee can lease it. Like dropping mail in a box.
From the console, the CLI, MCP tools inside Claude Desktop, a YAML workflow, or a ServiceNow webhook. Dependencies chain; gated jobs wait for a human.
Workers lease atomically, run through the right vendor CLI, report back. Every outcome is audited, and distilled into Drumline for the next job.
Same engine everywhere. The free edition is not a demo — it's the full product on your own machine.
No cloud account. No API keys. No database to provision.
curl -sSf https://batoncadence.com/install.sh | bash
macOS & Linux · Windows instructions below
One command installs everything and walks you through setup:
# Works on macOS and any Linux distro curl -sSf https://batoncadence.com/install.sh | bash # Clones the repo, finds/installs Python, creates the venv, # generates your access token, adds 'mco' to your PATH, # then asks: demo mode or connect now. # Or if you already cloned: bash scripts/install.sh
After install: mco serve starts the gateway · mco setup changes any setting
Double-click installer — no terminal needed:
# 1. Download the ZIP from GitHub and extract it anywhere # (e.g. C:\BatonCadence) # 2. Double-click: install.bat # Finds (or installs) Python, creates .venv, generates your # access token, copies a BatonCadence shortcut to the Desktop, # then asks: demo or connect now. # Your browser opens the console automatically.
Or run headless: powershell -ExecutionPolicy Bypass -File scripts\install.ps1 -NoPrompt
For developers who prefer explicit control:
# Clone + pip editable install git clone https://github.com/mastalink/Batoncadence pip install -e Batoncadence mco setup --guided # configure in 60 seconds mco serve # console at 127.0.0.1:18789/console # Docker (team / cloud deploy): docker compose up # see docs/DEPLOYMENT.md
Workers join from any machine with mco listen --role codex
Those are frameworks for building agents in one codebase. BatonCadence coordinates agents you already have — Claude Desktop, Codex CLI, Gemini, custom workers — across machines and vendors, with the governance layer (approvals, audit, escalation) those frameworks leave as an exercise for the reader.
Yes — that's a product decision, not an accident. Shared memory is the heart of the system, so it works fully offline against the embedded SQLite store. Cloud databases add multi-machine and multi-tenant reach, not features.
Every job mutation appends a row to agent_job_events. UPDATE and DELETE
are rejected at the storage layer — by a database trigger in cloud deployments, and
by the storage engine in local mode. History can be read, never rewritten.
Yes. Workers make outbound-only connections to the gateway, so they run happily inside customer networks or behind NAT — the control-plane/data-plane split enterprises expect from credential-holding tools.
MIT. Self-host it, fork it, ship it inside your company. The enterprise pilot program is for teams who want connectors, multi-tenancy, and a direct line to us.