v5.4.6 — Self-healing upgrade path
One-line fix shipped on top of v5.4.5.
Why
v5.4.5 restarts the daemon on macOS, Linux, and Windows after a plugin update. But the staleness check looked for the api/health capability marker. If you updated to v5.4.4 on Linux or Windows, your daemon script on disk already had api/health — v5.4.5 saw that, declared the file fresh, and skipped the restart. Your running daemon stayed stale.
What changed
The daemon script now embeds the exact version that generated it:
TOKEN_OPTIMIZER_DAEMON_VERSION = "5.4.6"The SessionStart staleness check compares this against the currently-running TOKEN_OPTIMIZER_VERSION. Any mismatch regenerates + restarts — on every future version bump, every user gets a fresh daemon automatically. No manual setup-daemon required for any upgrade path going forward.
Upgrade
Claude Code auto-updates the plugin on version bump. Just open a new session — SessionStart will regenerate your daemon and restart it via launchctl / systemctl / schtasks depending on your OS.