Thanks for the shoutout on the release! that was cool!
I found a small update-path gap after 1.2.0 shipped. My host updated to stable 1.2.0, but my CLI binary (~/.traycer/cli/bin/traycer) stayed on 1.2.0-rc.1 — looks like the host update didn't reconcile a pre-release CLI to the final build.
Symptom: every Claude Code stop hook that calls the traycer CLI failed with E_HOST_INCOMPATIBLE ("This Traycer client is too old for this host"). Harmless but noisy — hooks are non-blocking, and everything going over MCP (agents, messaging, worktrees) kept working fine the whole time, since only the CLI path was rejected.
Fix: one command — traycer cli upgrade — swapped 1.2.0-rc.1 → 1.2.0 in place, hooks quiet again. Agents and history untouched, as the error message promises.
Might be worth having the host updater bump an rc CLI to stable automatically when the final version lands, so pre-release testers don't hit this. Happy to share logs if useful.