Symptom
v0.0.58 changed what installClaudeConfig writes (#15), but updating did nothing for existing machines: the dummy ANTHROPIC_AUTH_TOKEN stayed in ~/.claude/settings.json until tokenmaxx install was rerun by hand.
Root cause
Install-time config is only written when the user explicitly runs tokenmaxx install or toggles routing in the dashboard. Nothing re-applies it after an update, so config fixes never reach already-installed machines on their own.
Proposal
On daemon start, when the running version differs from the last version that wrote configs, re-apply install for whatever is currently routed (per installStatus), then record the version.
- Only currently-routed harnesses — never re-adds routing the user uninstalled, never touches a harness they never routed.
- Once per version change, not on every start.
- A heal failure logs and never blocks the daemon.
Once #11 lands, the same pass should cover openclaw, pi, and hermes.
Symptom
v0.0.58 changed what
installClaudeConfigwrites (#15), but updating did nothing for existing machines: the dummyANTHROPIC_AUTH_TOKENstayed in~/.claude/settings.jsonuntiltokenmaxx installwas rerun by hand.Root cause
Install-time config is only written when the user explicitly runs
tokenmaxx installor toggles routing in the dashboard. Nothing re-applies it after an update, so config fixes never reach already-installed machines on their own.Proposal
On daemon start, when the running version differs from the last version that wrote configs, re-apply install for whatever is currently routed (per
installStatus), then record the version.Once #11 lands, the same pass should cover openclaw, pi, and hermes.