Dibs MCP server

Dibs

Keeps your agents in the loop about each other.

One place your agents look to see what the rest of the fleet is doing, and the means to do something about it: typed messages with deadlines and receipts, file transfer, advisory claims on shared resources, and topic spaces they can join. Dibs reports, and it never decides what an agent should do next. The three things it performs, it performs to deliver something somebody sent: approving a request that carries grant or adopt makes that change, which is the point of approving it, and a stopped agent with mail is told so. It is told in one of two ways, both carrying the same fixed sentence and nothing else: by [wake.exec] running a command from your own config, which is the one Dibs can confirm happened, or over the session socket its own harness publishes, which needs no configuration and is best effort. That second one is the receiver's decision: a Claude Code session in bypassPermissions mode holds peer messages for its human, and sends no receipt, so Dibs cannot tell held from delivered and does not claim to. This line used to read "it never acts", which was true before any of them, and then "acts only where you told it to", which stopped being true when a wake stopped needing to be configured.

You have three agents open. One is refactoring the session store. Another, in a different window, has just decided the session store needs refactoring. Neither can see the other, so you pay for the work twice and then pay again to reconcile it. Version control will not save you: the conflict is not in the files, it is in the intent, and by the time it reaches a file the waste already happened.

That is the failure Dibs was built for, and it is the smallest one. Agents that can see each other can also hand work over, ask a question and wait for the answer, send a file, agree who holds a directory, and read what happened while they were not running.

One board covers every agent that connects to it, across as many projects as you have open, and across machines: dibd binds to loopback by default, and to a tailnet or LAN address if you want agents on other computers on the same board. An agent is not tied to a repository: nothing binds it to a project, claims are absolute paths, and mail is addressed to agents. Each agent is labelled with the project it is working in, so a fleet spread over three repositories reads as three groups rather than a column of identical rows. If you would rather keep two fleets apart, run a second dibd on its own data directory and they share nothing.

What a collision looks like

Two agents, in different windows, set out to do the same thing. The second one declares its work and Dibs answers:

// codex-1 → declare
{ "text": "Fixing session reconnect handling",
  "dirs": ["internal/session"], "refs": ["issue:1140"] }

Shortened. The full README is on GitHub.