Become a sponsor to Jonathan Maye-Hobbs
What you're sponsoring
BMO is a multiplayer engineering workspace in the terminal. Describe what you want — fix a bug, add a feature, refactor a module — and BMO reads your code, makes edits, runs commands, and verifies the result. Parallel agents coordinate through a signal fabric, workspace claims, and review gates; edits and risky tools wait for your
confirmation by default.
BMO is Apache-2.0, runs on your workstation, and does not require a hosted
backend. It works with Anthropic, OpenAI, Gemini, Vertex AI, Bedrock,
OpenRouter, and local OpenAI-compatible providers.
Why it's different
- Shared workspace, not isolated chats. You and the agents use the same
sessions, tools, data dir, and evidence. - Approvals by default. Edits and risky tools wait for confirmation; auto-
approval is an explicit opt-in. - Signal fabric + stigmergic coordination. Advisory deposits, zone pressure,
and fabric-native induction let agents discover patterns and propose rules
without explicit orchestration — every beat writes machine-readable receipts. - Many surfaces, one core. Interactive TUI, headless CLI, HTTP server, MCP,
and A2A all expose the same concepts. - Coordination under parallelism. Workspace claims, mesh routing,
workstreams, and a multiplayer coordination dashboard keep overlap visible
and governable.
Public coordination specs
BMO implements patterns formalized as standalone, reusable specs:
- agent-coordination-substrate — signals, zone pressure, mortal claims, induction (Go reference impl + conformance runner)
- swarm-orchestration-spec v1.1 — orchestration taxonomy and environment-mediated coordination
- agent-coordination-readout — recommendation packets, outcome ledgers, operator cognition
What your sponsorship funds
- Maintaining the BMO core (TUI, headless CLI, HTTP/MCP/A2A surfaces)
- Hardening the signal fabric, workspace claims, and review-gate primitives
- Keeping the public coordination specs in lockstep with a working reference
implementation - Documentation, security posture, and reproducible proof harnesses
Status
BMO is pre-1.0 (v0.x). CLI flags and on-disk formats may still change between
minor releases — pin a reviewed release tag
for production use. Sponsorships directly extend the time available to push
toward a stable 1.0 and the surrounding spec ecosystem.
Thank you for supporting open agent infrastructure that runs on your machine,
under your approval, with the receipts to prove it.
Featured work
-
instagrim-dev/swarm-orchestration-spec
Technical specification for environment-mediated and adaptive multi-agent orchestration in software development tools
Shell 2 -
instagrim-dev/agent-coordination-substrate
Specification for environment-mediated coordination between autonomous agents
Go 1 -
instagrim-dev/agent-coordination-readout
Specification for read-model surfaces and explicit actuation over the Agent Coordination Substrate