Stop being your agents' control plane.
When two agents reach for the same files, one loses the work. Coven decides who waits, and keeps the record of why.
The Windows MSI can trail the macOS and Linux release. No Arm64 installer yet — the x64 build runs under emulation.
No .deb or .rpm yet — the AppImage runs on any distribution.
TestFlight installs are signed by Apple and verified on device, so there is no checksum to run.
The board is read-only here; claims and merges happen in Cave.
Cave is a desktop app. Copy the install line and run it on the machine your agents work on.
claude code·sonnet 4.6 Hexi working tree · opencoven Hexi working Two claims on one surface.
Hexi has been writing in ui/composer since 14:02. Sage reached for the same shell at 14:19 and the runtime held it there.
Both rewrite the same four lines of composer-shell.tsx, and they disagree about where the radius comes from. Whichever landed second would have quietly undone the first.
Sage only needs the token scale. Narrow its claim and both can work at once.
38 minutes and 86 lines in, tests already green. Sage picks it up after the merge.
Neither suggestion fits? Write the instruction and both familiars get it.
Pill radius across the ecosystem
One shared record.
Every session keeps its own memory and its own worktree. None of them knows about the other three. Coven caught this overlap before either agent shipped.
The Windows MSI can trail the macOS and Linux release. No Arm64 installer yet — the x64 build runs under emulation.
No .deb or .rpm yet — the AppImage runs on any distribution.
TestFlight installs are signed by Apple and verified on device, so there is no checksum to run.
The board is read-only here; claims and merges happen in Cave.
What changes on day one
Agents stop overwriting each other
A claim on a surface holds until the work lands or you release it. Coven tells the second session before it writes.
Claims and memory outlive the session
Close the terminal, restart the machine. The claims, the events, and what each familiar learned are still there.
You stay the authority
Guards stop anything past their line and wait for your yes, with the diff in front of you.
Install Cave, then open a repo.
The daemon runs on your machine. Point it at a project and every session working there shares one record.
The Windows MSI can trail the macOS and Linux release. No Arm64 installer yet — the x64 build runs under emulation.
No .deb or .rpm yet — the AppImage runs on any distribution.
TestFlight installs are signed by Apple and verified on device, so there is no checksum to run.
The board is read-only here; claims and merges happen in Cave.