[nsleigh]

Low priority, like #85: no release needed on its own. It numbers itself
2.5.5 after #85 (2.5.4); happy to rebase or renumber if the order changes.

Problem

Running /login to renew a login or switch account posted no "Claude Code
login" notification. The watcher (scripts/login-url-watcher.sh) only
looked for a login link while Claude was logged out, and while the old
login is still valid it counts as logged in, so the new link was skipped.

Fix

• Look for a new login link all the time, not only while logged out. The
  set of links already posted is unchanged, so a link is still never
  posted twice, and old links can't come back after a restart (the tmux
  session starts empty).
• Dismiss the notification once the saved login has changed and is
  valid, rather than as soon as any valid login exists (which the old one
  already was). The change is spotted with a checksum of
  .credentials.json, so the watcher never reads the tokens.
• DOCS.md: mentions re-running /login, and that the watcher reads the
  window Claude starts in.

If Claude refreshes its token while a /login is half done, the
notification can be dismissed early; the link is still in the terminal.

Tests

tests/test-login-url-watcher.sh gains a re-login case: logged in, a new
link appears → posted; the credentials don't change → it stays; the new
login is saved → dismissed. It fails on the old watcher. The existing
cases (first login, expiry with the old link in scrollback, a later new
login) still pass, as do the full suite and ShellCheck.

Tested

On Home Assistant OS: in the dev add-on, while logged in, /login posted
the notification, and it cleared once the code was pasted.

🤖 Generated with Claude Code

https://claude.ai/code/session_018rxd5pKHfU3wFULG6yLDE6

[ESJavadex]

Thanks, @nsleigh — I reviewed the /login notification flow and the checksum-based credential-change check; the watcher never emits token contents. The updated branch passed the full CI matrix, including browser and both architecture builds. Merged as 2.5.5.