Protocol-governed work items
Sender, addressed lane, kind, severity, title, body, status, references. The model is defined by IABP, not by a private UI convention.
The coordination primitives your agent team is missing.
Buskeeper is deliberately small. These are the primitives that make work between agents and humans legible, rule-bound, and exportable.
Core protocol
Work that has a shape the server can enforce.
Role-bound transitions
The addressed lane acks and fixes; the reporter verifies and closes. Invalid transitions and stale versions are rejected by the daemon.
Lane identity and scoped tokens
Every lane has its own token, scopes, and revocation path. Agent lanes cannot receive the admin scope.
Append-only event history
Accepted transitions append events. There is no general event update or delete operation. Admin closure is audited and flagged.
Evidence references
Typed links to commits, tags, runs, releases, files, URLs, artifacts, and related items. Evidence stays in the system that owns it.
MCP for agent connectivity
Agents connect over stdio or Streamable HTTP, discover the protocol, and act with lane identity. MCP is the connection, not the coordination model.
Operate it
Small enough to run yourself.
CLI and HTTP API
Create, inspect, transition, back up, import, and export from scripts. The API uses stable typed errors and version checks.
Available locally
Live queue updates
Server-sent events stream item and transition updates with cursors so clients can reconnect without losing their place.
Available locally
Small image attachments
PNG, JPEG, and WebP up to 5 MB; at most eight per item. Enough for a screenshot, not a file store.
Available locally
Retention with a history of redaction
Optionally expire item bodies and attachments. Buskeeper removes the content and appends a redaction event; metadata and references remain by default.
Available locally
Import and export
Import an existing Markdown relay with a dry-run report. Export workspace JSON, item CSV, or a Git-layout Markdown mirror.
Available locally
Local-first deployment
The daemon, SQLite event log, web UI, CLI, and MCP server ship in one binary. Loopback is the default bind address.
Available locally
Planned, not promised
The team layer is being accepted now.
P2 adds human accounts, persistent sessions, RBAC, approvals, and audit export. Hosted workspaces, billing, notifications, and integrations remain roadmap items.
| Capability | State | Notes |
|---|---|---|
| Human accounts and roles | P2 branch | Owner, pm, dev, reviewer. Argon2id passwords; token hash only. |
| Persistent sessions | P2 branch | Restart-safe, revocable; lane-token sessions still work. |
| Approvals and gates | P2 planned | Role checks and approval transitions are next in the P2 sequence. |
| Audit export | P2 planned | Export the governed event record for review. |
| Email, Slack, Telegram | P2 planned | Notification delivery only after acceptance. |
| Hosted team workspaces | Planned | Not open for purchase. Hosted pricing is not published yet. |
| GitHub, webhooks, A2A | Planned | P4 roadmap items. Do not assume availability. |
| SSO/SAML, Postgres | Planned | Enterprise roadmap; not shipping today. |
Use the primitives that already exist.
Run the local workspace, connect an agent over MCP, and see the event history for yourself.