v0.60.1

Fixed

• A credential's banked resets sit on their own line under its limits title,
  wrapping, instead of lengthening the title past the edge of the panel. The
  title wraps too where a frontend used to cut it off (Omarchy, Plasma, the
  tray), and the TUI gives a wrapped title and note the lines they take.

What's Changed

• Banked resets on their own line under the limits title, and titles that wrap by @Arzaroth in #99

Full Changelog: v0.60.0...v0.60.1

v0.60.0

Added

• tokengauge --sync-export prints 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 of AWS_ACCESS_KEY_ID and
  AWS_SECRET_ACCESS_KEY in 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 as bankedResets.kinds for remuda, the idle resets marked idle.

Fixed

• Fleet sync counts a Claude Code, Codex, Kimi or Grok session once when it is
  moved or copied to another machine (t3cc send, --copy), and when two
  machines read a shared ~/.claude/projects with 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

v0.59.0

Added

• Opening a panel fetches current figures when the snapshot is at least five
  minutes old, on Plasma, GNOME, Omarchy and the tray.
• Providers: GitHub Copilot, Google Antigravity, DeepSeek, MiniMax and Meta Muse.
• A + beside the remuda button opens remuda (0.37.0 or later) on its add-account sheet, on
  Plasma, GNOME, Omarchy and the TUI, and through --open=remuda-add for a waybar
  click. Signing in stays remuda's.
• Codex's free limit resets are marked on the limits title, the way Claude's
  banked resets are.
• The panel and every frontend read in French, following the locale or [panel] language = "auto" | "en" | "fr", with a switch in each settings pane.

Changed

• A provider answering 429 keeps its last figures current for thirty minutes
  rather than turning stale at once. Any other error still marks them stale.
• The Omarchy widget answers omarchy-shell over the shell's own socket on
  Omarchy 4.5 and later.
• New app icon: a coin whose edge is a gauge, with an AI sparkle filling up in the middle.

Fixed

• Omarchy: provider logos in the panel have smooth edges, and Codex's >_ is no
  longer half filled in.

What's Changed

• [fix/omarchy-mark-edges] Omarchy logos keep their antialiased edges by @Arzaroth in #90
• [feature/panel-open-fetch] Fetch when a panel opens, and hold figures through a 429 by @Arzaroth in #91
• [feature/codex-reset-credits] Codex's free resets on the limits title by @Arzaroth in #92
• [feature/more-providers] Copilot, Antigravity, DeepSeek, MiniMax and Muse by @Arzaroth in #93
• [feature/i18n] English and French, on every surface by @Arzaroth in #94
• [feature/remuda-add] a + beside the remuda button adds an account in remuda by @Arzaroth in #95

Full Changelog: v0.58.0...v0.59.0

v0.58.0

Added

• Fleet sync shares each limit's history: a machine that was off or signed out
  for days takes in what the others saw meanwhile, so its pace, its projection
  and remuda's drain chart are measured from the whole week rather than across
  the gap. Finished weeks are shared too. Each machine shares only what it saw
  itself, and the fleet's view lands in tokengauge-window-fleet.json beside
  its own history, so a new fleet key forgets the old fleet's.

Fixed

• A limit's projection after a quiet start follows how fast it is filling
  now: a week left at 0% for days and then spent in an afternoon was measured
  as if that afternoon's use had been spread over the whole week.
• After a banked Claude reset, which refills the week without moving its
  reset, the pace is measured from the refill: a fresh 0% three days before
  the reset reads as on track rather than far behind, and its projection
  follows the use since the refill.

What's Changed

• [fix/burn-stretch-and-wild-resets] The burn measures its own stretch, and a refill in place opens the window by @Arzaroth in #88
• [feature/fleet-window-trails] Fleet sync shares each limit's history by @Arzaroth in #89

Full Changelog: v0.57.0...v0.58.0

v0.57.0

Changed

• Codex and OpenRouter show their current logos: Codex's cloud with a prompt
  instead of OpenAI's knot, and OpenRouter's new mark.
• The Claude logo keeps its orange in the GNOME and Plasma panels, and the
  Codex, Cursor and OpenRouter logos are drawn in the foreground instead of
  their accent colour. In the Omarchy panel a black-and-white logo follows the
  theme's foreground.
• scripts/install-omarchy.sh --placement takes every Omarchy bar section
  (left, centerBegin, center, centerEnd, tray, right), not only
  left, center and right, and a rerun says how to move a widget that is
  already enabled.

What's Changed

• [feat/current-provider-marks] Current Codex and OpenRouter logos, each drawn in its own colour by @Arzaroth in #87

Full Changelog: v0.56.1...v0.57.0

v0.56.1

Fixed

• A Codex credit balance reads as credits (62,500), not dollars
  ($62500.00).
• opencode Go finds a login made in opencode 2, which keeps it in
  opencode.db rather than auth.json, reading the account opencode itself
  uses when it holds several, and a key filed under opencode 1's opencode
  id.
• Codex sessions compressed to .jsonl.zst, which Codex 0.163 and later does
  to every finished session, and sessions moved to archived_sessions count
  towards cost and history again.
• Codex calls made in Fast mode are priced at the priority tier, 2x to 2.5x
  the standard price, instead of at standard.
• A Cursor X Subscription shows its weekly pool shared with Grok, instead of
  a monthly figure stuck at 0%.
• kimi-k2-thinking is priced again: LiteLLM dropped it from its table, and
  TokenGauge now keeps the last price it carried for any model it drops.
• The omarchy widget's bar animations turn off with the shell's animations
  (omarchy 4.5).

Security

• A z.ai error that quotes the API key no longer carries the key into the
  snapshot or the panel.

What's Changed

• Upstream backports 2026-11: opencode 2, compressed Codex rollouts, Fast mode, Cursor pool by @Arzaroth in #86

Full Changelog: v0.56.0...v0.56.1

v0.56.0

Added

• tokengauge-window-history.json keeps a record of each window of a day or
  longer once it ends: how full it got and when it opened and reset, for a
  year. remuda's Usage tab reads it to show what a week of each plan bought.
• Plan weights come from selvedge's dated catalog, shared with remuda; no
  weight changes.

What's Changed

• Keep a record of each closed daily or weekly window by @Arzaroth in #84
• Plan weights come from selvedge's catalog by @Arzaroth in #85

Full Changelog: v0.55.0...v0.56.0

v0.55.0

Changed

• ChatGPT Pro 100, 200 and 500 now weigh 10, 20 and 50 Plus allowances, and a
  Business Premium seat 10, since OpenAI doubled their limits on 29 October.
  Plus and Business seats still weigh 1.

What's Changed

• Codex Pro plans and Business Premium weigh twice what they did by @Arzaroth in #83

Full Changelog: v0.54.0...v0.55.0

v0.54.0

Changed

• Pace follows how fast a window has been filling lately, not its average
  since it opened: a morning's burst followed by a quiet afternoon now ends
  near where it stands instead of reading as a run-out. TokenGauge keeps each
  window's history in tokengauge-window-history.json beside the snapshot,
  and the snapshot gives each window its recent burn. Until a window has
  some history, its pace is what it was.

What's Changed

• Window history: pace projects at the recent burn by @Arzaroth in #82

Full Changelog: v0.53.1...v0.54.0

v0.53.1

Fixed

• Spend history no longer disappears when the fleet store holds dedup keys in
  a shape the running build cannot read. The whole store used to be set aside
  as tokengauge-fleet.json.rejected and history restarted from whatever
  transcripts were left; now only the keys are dropped, and the next read
  rebuilds them.

What's Changed

• An unreadable counted index costs the keys, not the store by @Arzaroth in #81

Full Changelog: v0.53.0...v0.53.1