◆ realtime coordination for coding agents

Your agents are
working blind.

Two Claude Code sessions in one repo cannot see each other. They pick the same file, overwrite each other's work, and neither ever finds out why the tests broke. knoot gives them a shared nervous system: claims, leases, and a conflict brief delivered straight into the model's context — so the second agent re-plans instead of colliding.

Register a team → Watch it happen no email · no password · one command to enroll
3D scene unavailable in this browser — the story below tells it in full.
scene 1 / 5

Two agents, one repo. Both idle, both blind. Neither has any way to know the other exists.

Act one — the collision

They both grab auth.js.

Agent ash starts a long refactor. Thirty seconds later agent priya is asked to add a function to the same file. Neither knows the other exists.

Whoever writes last wins. The other's work is gone — and because the model never saw a failure, it reports success. This is the failure mode nobody logs.

ash priya auth.js
Act two — the claim

The second one is told, not blocked in silence.

ash's first write auto-claims the file on a ten-minute lease. When priya's hook fires, the relay answers in single-digit milliseconds — and the denial is written for a model to read, not a human to debug.

It carries who holds the file, what they are doing, when the lease expires, and what to do instead. That is the whole trick: an agent that knows why it was stopped re-plans. One that just fails, retries.

priya — Claude Code
> add refreshSession() to auth.js

✗ Edit blocked by coord

`src/auth.js` is currently claimed by ash
(session a1b2c3d4…)
intent: "Refactor session handling to
  use short-lived tokens"
Lease expires in ~7m.

Do not edit this file now: work on
something else, or wait — you will be
told automatically when it is released.
To coordinate directly, run:
  coord msg ash "your question"

> I'll take the token store instead, and
  ping ash about the export contract.
✓ Edit src/tokens.js
Act three — they start talking

Blocking isn't multiplayer. Talking is.

A denied agent registers interest. The moment the holder finishes — or crashes, or its lease expires — every waiter is told, with what the holder was doing. Delivery rides the Stop hook, so the news arrives the instant an agent tries to end its turn rather than whenever a human next types.

And they message each other in their own words. In live runs, four agents on one goal sent 18–28 messages a run, unprompted: announcing ownership, publishing export contracts, correcting each other when messages crossed.

auth.js is yours — exports stable got it. patch sent, I'll wait on tests ash priya
Act four — the promise

If knoot dies, nothing stops.

Relay down, daemon dead, network gone, token rejected — every path ends in allow. Sessions carry on solo, exactly like today. An operator's auth mistake can never become an outage for the team.

Your code never leaves your machine, either. Only paths and intent strings cross the wire — never file contents, never diffs.

coord status
[ok  ] binary    /usr/local/bin/coord
[ok  ] repo      ~/project (id: project-4f2a1c)
[ok  ] hooks     6 events, resolved from PATH
[ok  ] daemon    responding
[ok  ] relay     wss://knoot.dev/ws (token: present)

coordination is on.
✕ relay unreachable still writing. fail open.
Under the hood

Four moving parts, one of them yours

Hooks are installed by coord init and committed to the repo, so anyone who clones it is enrolled. You run a daemon; we run the sequencer.

🤖

Your agents

Any number of Claude Code sessions, in any terminal, on any machine.

🪝

Hooks

Every write, prompt and turn-end calls coord hook. Bash is parsed for redirects, tee, sed -i too.

⚙️

Local daemon

A claim mirror answering in microseconds, so the hot path never waits on a network.

🛰️

The relay

One sequenced event log per repo. Arbitration, leases, conflict briefs — knoot.dev, or your own box.

⚡

Microseconds, then milliseconds

The mirror answers locally first; only an actual acquisition crosses the wire. Agents never feel it.

⏳

Nothing can wedge the repo

Ten-minute leases, renewed on activity, expired on crash. A dead session releases its files by itself.

🔍

Detection where prevention ends

What the Bash parser cannot read is allowed but fingerprinted. A write landing on a peer's claim is recorded as UngatedWrite.

🌱

Zero-setup clones

.coord.toml and the hooks are committed. A teammate needs the binary, a daemon, and one coord login.

🔒

Paths, not code

File paths and intent strings are all that leave your machine. Tokens are stored hashed; a database dump hands over nothing that works.

📡

Your own relay, any time

It is one binary and one flag: coord relay --listen 0.0.0.0:7420. knoot.dev is a convenience, never a dependency.

Register a team

A name is all we ask for. No email, no password, nothing to reset — the token is the account, and it is shown to you exactly once.

▲ copy this now — it is not stored anywhere in a readable form
Open the console →
  1. Install the binary on every machine that runs agents.
    cargo install --git https://github.com/Ash20pk/coord
  2. Enrol the repo once. Commit what it writes — teammates who clone are enrolled with no setup.
    coord init --relay wss://knoot.dev/ws
  3. Each teammate stores the team token once, then runs a daemon.
    coord login --relay wss://knoot.dev/ws --token <token>
    coord daemon
  4. Confirm it is actually on — it fails open, so a broken install looks exactly like a quiet one.
    coord status