Repository navigation
0.12.0's promises now hold on the path most blocked edits actually take. An audit
after release found that tower guard — what the PreToolUse hook and the pre-commit
guard run — never reached the code 0.12.0 added. Everything below is a fix or a
correction; no protocol changes, still 20 tools.
Fixed
- A hook-blocked agent was promised a message it never got.
tower guard
pre-checked withcheck_collisionand returned beforeclaim_intent, so the blocked
agent was never registered as a waiter, never sawalternatives, and the collision
never reachedtower stats— while the prompt printed "[w] wait — Tower messages you"
and 0.12.0's notes said the same.guardnow goes straight throughclaim_intent
(a refusal registers nothing, so the pre-check bought nothing). - An edit built on a moved declaration went through unclaimed. The same pre-check
ignored the agent's recorded reads; the claim that followed was refused over them, and
the refusal was dropped. It now blocks. - Claims from the CLI and the hooks carried no signatures.
path#namesymbols were
sent without their declaration fingerprint, so on the hook path there was no hard
write_read, no heartbeat invalidation and no landed-signature notice on complete —
only MCP clients that sentsigthemselves got any of it. They are now fingerprinted
from the working tree. tower statscounted a retry as a new collision. A hook retries a blocked edit each
time the agent reaches for it. A refusal is now counted once per agent per blocking
claim.init --hooksnever upgraded an existing install. It skipped any event already in
.claude/settings.json, so an install from before 0.11 kept aPostToolUsematcher
withoutRead— no recorded reads, none of 0.12's read-time warnings — and re-running
the documented command said "already wires every Tower hook". It now rewrites Tower's
own entries, moves Tower's command out of a group it shares with yours rather than
editing that group, adds Tower's entry beside your own hooks for the same event, and
never changes your hooks. Upgrade: in your Tower clone,
git pull && npm install && npm run build && npx tower-mcp init --hooks..claude/settings.example.jsonhad the old matcher too; a test now holds it equal to
whatinit --hookswrites.tower initprinted a hand-copied pre-0.12 rule; it now prints the onetower setup
writes.tower <command> --helpexited 1 with "Unknown option"; every command now prints help
and exits 0. New:tower --version. Help now listswork's--agent,--repo,
--cmd,--interval,--max-minutes,--no-push,--no-prandserve's--host.- The UserPromptSubmit nudge hook fell back to
npx -y tower-mcp nudge— a registry call
on every prompt, contradicting "no network calls you didn't configure". Like every
other hook it now needs the built CLI, and says so on stderr if it is missing. tower-anywherehad the same guard bug; itsguardnow goes throughclaim_intent
too, and both commands print what is still free when refused.- Docs: SECURITY.md described one hook on one machine; team.md and enforcement.md said
repo identity comes fromorigin(it is the root commit sha); worker.md never said what
happens when a headless run hits a conflict; the site's tool grid listed 19 of 20
tools. Sample repo ids and agent names in tests and on the site are now made up.
Added
site/logo.png(listed as the registry icon) andsite/og.png, the link preview.glama.json, for claiming the Glama directory listing.