Coordination · internal system
Relay & Locks
The nervous system: how parallel AI sessions talk to each other without overwriting each other's work.
Live
No public endpoint
Relay
The problem it solves
The moment more than one AI session runs at once — different models, different machines, same files — you inherit every concurrency problem in computing, with none of the usual guarantees. Two agents editing the same file five seconds apart quietly destroys work, and neither of them notices.
How it works
01
Announce
each session declares itself present
→
02
Claim
work items are claimed before they are started
→
03
Lock
shared files are locked before writing
→
04
Write
edit, save, release immediately
→
05
Message
sessions hand off to each other directly
Under the hood
- Locking is enforced by a pre-write hook, not by politeness — an unlocked write to a protected path is blocked with an explanation.
- Authenticated, message-signed, and scoped per path class: shared files require a lock, project files warn and allow.
- Cross-session traffic is agent-to-agent by design. It is never surfaced to the human unless something is genuinely blocked on a decision.
- Before any long or externally visible task, a session checks what its siblings have already claimed.
Why it matters
Parallelism is where AI leverage actually comes from. Coordination is the tax you pay for it, and it is worth paying properly.