Repository navigation
v0.12.0 — nobody waits
Nobody waits. Before this release a hard conflict ended in stand_down and
nothing else, and the rule tower setup writes said "stop and ask the user" — so a single
conflict parked an agent until a human noticed. Each of the four places an agent could
stall now has an answer on the wire. All of it is additive and optional: a client that
ignores the new fields behaves exactly as on 0.11. Still 20 tools.
Added
- A refusal says what to do instead. A refused
claim_intentcarries
alternatives:avoid(what the blocking claims hold, plus code inferred to depend on
it),nextTask(a sequencer task, when.tower/policy.yamldefines modules),
notifyOnRelease, and one line ofadvice.tower claimprints it under the refusal. - Dependencies inferred from reads, not configured. A claim that wrote
checkout
having readverifyis evidence thatcheckoutdepends onverify, so whileverify
is heldcheckoutis inavoidtoo. One hop, the last seven days of claims, capped at
50 — nopolicy.yamlrequired. - The refused agent is messaged when the block ends. Refusal registers a waiter on
each blocking claim; completion, release or expiry sends it a message fromtower
naming what freed up. No retry loop. - Warned at read time.
record_readsreturnsconflicts— anyone changing what you
just read — and takes an optionalbranch, so work on another branch warnssoft. The
PostToolUsehook delivers this to Claude Code asadditionalContexton everyRead
(plain stdout from that hook never reaches the agent). - Contract-first:
declares. ASymbolRefyou claim may carry the declaration it
will have once your change lands. Readers get asoftwrite_readwith
declaredSigTextand build against it in parallel; a declared contract is neverhard,
and a reader already on it is not warned.heartbeatdelivers a declaration to readers
that claimed first. complete_claimreports the contract that landed. It takes the claimedsymbols
as they stand after the change (tower completeand the post-commit hook fill them
from the working tree). Every agent that read a declaration which moved — or was
declared — is messaged the landed signature and whether it matches the declaration. The
output is now{ ok, notified }.tower setup --keep-goingwrites a rule that routes around a conflict instead of
stopping: work outsideavoid, and ask the human only when nothing safe is left. The
default rule still says stop and ask.
Fixed
- On Windows, a blocked edit was not blocked. The hooks ended with
process.exit(),
which aborts in libuv (!(handle->flags & UV_HANDLE_CLOSING)) while V8 is still
compiling tree-sitter's WebAssembly in the background. The PreToolUse hook printed its
refusal and exited127instead of2, which Claude Code treats as a non-blocking
error — so the edit went ahead. The same crash discarded everyPostToolUsecontext.
The hooks now setprocess.exitCodeand let the process end, with an unref'd timer as
a backstop; measured 0/10 correct exit codes before and 10/10 after. Re-run
npm run buildin your Tower clone — the hooks run from there, not from npm. cmdRecordReadsdid not fall back to derivingrepoIdthe waycmdClaimdoes, so a
caller that omitted it recorded reads in a different partition from its own claims. The
shipped hook always passed one; this closes the gap for every other caller.- A
declareswritten with a leadingexportfingerprints the same as the parsed
declaration, which never includes it. [w] waitin the collision prompt said "retry in a few minutes"; Tower now messages you.- Docs: the protocol tool table omitted
propose_intent, the README and site still said
the hook claims at file granularity (it has claimed the enclosing function since
0.10), and the protocol's "current limit" described heartbeat delivery as unshipped.