Repository navigation
v0.60.0
Added
tokengauge --sync-exportprints everything another machine needs to join
the fleet on its own: the key, the[sync]transport and the S3 keys, never
the device id or label.tokengauge --sync-join -takes it where it took a
bare key, so a new machine is set up in one step.tokengauge --sync-s3-credentials -keeps the S3 keys in a private file
beside the fleet key instead ofAWS_ACCESS_KEY_IDand
AWS_SECRET_ACCESS_KEYin every process's environment. The variables still
work when the file is absent.- A banked Claude reset says what it clears:
1 Fable reset banked,1 Fable reset, 1 weekly reset banked, and one with nothing to clear yet is marked
(nothing to reset), as claude.ai greys it out. The snapshot carries the
split asbankedResets.kindsfor remuda, the idle resets markedidle.
Fixed
- Fleet sync counts a Claude Code, Codex, Kimi or Grok session once when it is
moved or copied to another machine (t3ccsend,--copy), and when two
machines read a shared~/.claude/projectswith other usage on the same day.
Both machines need this release; with an older one it counts as before. - Kimi and Grok sessions are counted in the history's sessions begun.
What's Changed
- [fix/fleet-moved-session] fix(sync): a moved or copied session counts once across the fleet by @Arzaroth in #98
- Banked resets say what they reset: Fable, 5-hour, weekly, full by @Arzaroth in #96
- [feature/sync-bundle] Fleet bundle export and join, S3 keys in a private file by @Arzaroth in #97
Full Changelog: v0.59.0...v0.60.0