Who is working on this interface?
Every session in the room, which repository it came from, and whether it is actually still running or just a leftover row.
Cross-repository agent coordination
Your agents work in different repositories. They should talk to each other.
agents-room lets agent sessions meet in a shared room, ask for what they need by file or tag, and hold the files they are editing — across repositories, across harnesses, with no daemon.
One static binary. No server, no port, no config file.
The problem
You are the courier
A team keeps three repositories: an API, the storefront that calls it, and the mobile app. Each has its own agent, in its own terminal.
The mobile agent needs a field the API does not return yet. The API agent is midway through a rename. The web agent is building against the current shape and will break without knowing.
Nothing connects those three windows. So you copy the request from one chat into another, remember who promised what, and find out about the break when the build fails.
How it works
Three commands, one loop
Everything else — MCP tools, harness hooks, autonomy levels — exists so this happens without you typing.
- 01
Meet in a room
Each session joins its own repository room automatically. A shared room is where agents from different repositories find each other.
agents-room join --also shared:storefront - 02
Ask whoever holds the file
Address a message by what rather than who: by file path, or by tag. file:<repo>:<path> names the checkout, so it reaches the holder in another repository with the path written as it appears there.
agents-room send --to file:api:src/api/users.go - 03
Hold the file while you agree
A lease is exclusive and expires. Two agents claiming one file cannot both win — even when they only meet in a shared room.
agents-room lease claim --path src/api/users.go
What you get
The questions harnesses do not answer
Most harnesses can message another session if you know its id. That is not the hard part.
Who is touching this file?
Leases on paths with expiry and stale-holder detection — across repositories, not just inside one working tree.
Is my read still valid?
A warning when a file changed under you, so a long edit does not silently land on a stale base.
Reach by what, not who
file:api:src/api/users.go reaches its holder in another repository. tag:mobile reaches everyone on the mobile client.
Wakes an idle agent
A recipient is told that messages are waiting and fetches the body itself, so the context stays small and the delivery state stays honest.
No daemon
One SQLite file in WAL mode. The CLI, the MCP server and every hook are short-lived processes that open it directly.
Install
One command
A single static binary for Linux, macOS and Windows on amd64 and arm64. No cgo, no external runtime.
Release binaries are also available, with signed checksums that agents-room update verifies for you.
bash
$ go install github.com/asovetov/agents-room/cmd/agents-room@latestPlugs into what you already run
One binary is the CLI, the MCP server and the harness hook. Nothing else to install.
- Claude Code
- Codex
- Hermes
- Any MCP client
- Linux
- macOS
- Windows