Skip to content

Releases

v1.122.0

Choose a tag to compare

@omrikais omrikais released this 18 Nov 04:36

Added

  • Codex cost reports price gpt-6.2-astra, gpt-6.2-sol, gpt-6.2-astra-law and gpt-6-cyber from their published rate cards instead of falling back to gpt-5 rates, including usage recorded before you upgrade.
  • Claude cost reports price claude-fable-5-2 and claude-mythos-5-2, including Fast mode, instead of counting them at $0, and statusline uses their 1M context window.

Fixed

  • The dashboard no longer briefly drops its stats.db locks while checking the database version, which could let the status line write at the same moment a page was reading or a refresh was writing.
  • After a Codex home is moved or renamed, the dashboard, codex quota and the --source codex reports no longer count its sessions, projects, totals and quota history twice until cleanup finishes.
  • cctally codex percent-breakdown --account now shows the chosen account's cycle and rejects an unknown account, instead of ignoring the flag.
  • Codex requests over 272K input tokens on gpt-6-astra-law are priced at its long-context rates instead of its standard rates.
  • cctally pricing-check no longer reports GPT-5.6 Sol's promotional pricing as expired before it ends on November 30, 2026.

v1.120.1

Choose a tag to compare

@omrikais omrikais released this 17 Nov 07:01

Stable upgrade: v1.118.2 → v1.120.1

Includes every released CHANGELOG section in this range, newest first.

[1.120.1] - 2026-11-17

Fixed

  • With an older SQLite, as many Linux distributions ship, upgrading an old install whose cache.db is damaged no longer shows a database migration error; the upgrade waits until the cache is repaired, as it already did with newer SQLite.

[1.120.0] - 2026-11-16

Added

  • cctally db reindex-search checks the conversation search indexes against their messages and rebuilds any that disagree; --check only reports.

Changed

  • Commands you run now stop waiting on cache.db or conversations.db maintenance after 5 seconds, as they already did for stats.db. Hooks, the status-line writer (record-usage) and background work keep waiting.
  • cctally db status now only reads your databases: it no longer resumes an interrupted stats rebuild; the next command that shows or records usage, such as report or the status line, finishes it instead.
  • On a large usage history, the dashboard no longer pauses for most of a second every few seconds while it refreshes, so pages and live updates respond more evenly. It costs about 30 MB more memory.
  • While cache.db is being repaired, the dashboard no longer reads it: conversation search and the reader, Explain and project detail are unavailable until the repair ends, and the Projects panel keeps the data it already shows.
  • The dashboard no longer updates or repairs databases while answering a page: a block detail reads stored usage, or your session files during a rebuild, and the dashboard's background work fixes what a page finds.
  • Right after an upgrade, db status and doctor show a stats.db from an older version as not readable until the next command converts it.
  • After a gap without a running cctally dashboard, its transcript catch-up writes about 9% less to conversations.db. Search results are unchanged.
  • When the Codex hooks that cctally setup installs are enabled, the first Codex turn after deleted Codex sessions are cleaned up no longer redoes that cleanup's quota work, so it stays fast.
  • With an account selected, the dashboard Conversation Viewer and transcript commands respond much faster: they reuse the conversation summaries they can verify instead of rebuilding the account's whole list. Results are unchanged.
  • The first cache build after installing, and cache-sync --rebuild, now write about half as much to disk and finish sooner on large histories. Usage and cost results are unchanged.
  • Title search in the dashboard Conversation Viewer and transcript search --kind title no longer reads every stored message, so it stays fast however large the transcript history is. Results are unchanged.

Fixed

  • When cache.db exists but cannot be read, cctally pricing-check no longer says every observed model is priced: it reports Coverage: unavailable (cache.db could not be read). and a degraded check (cache in --json).
  • When cache.db is found corrupt while an upgrade runs its database steps, cctally no longer deletes it; the next command quarantines a copy and rebuilds it through the normal recovery.
  • On macOS, remounting the external drive or disk image that holds the data folder no longer makes the next sync rebuild the Codex quota index.
  • Codex quota blocks, milestones and alerts stay accurate when updates overlap, Spark windows keep their dashboard block detail, and re-enabled alerts notify again. Turning alerts on or changing their rules no longer stalls Codex turns.
  • After an upgrade, the dashboard Conversation Viewer re-checks its stored session summaries a few at a time, so a session cost that had fallen behind its usage records is corrected.
  • On Linux, the stats rebuild memory peak that cctally doctor and cctally db status report no longer includes the peak of the process that started the rebuild, which could raise a false 2 GiB memory warning.
  • With an account selected, a dashboard Conversation Viewer model chip and transcript search --account with --model no longer fail; they list that account's conversations that used the chosen model family, and the search hits in them.
  • The dashboard Conversation Viewer's session costs, cost filter and sort, and cache-rebuild counts now update when usage records change or are removed without a transcript change, and after an interrupted sync.
  • cache-sync --prune-orphans no longer fails when a removed session continues in another project, and neither a pricing refresh of the session list nor cache-sync --rebuild blocks the conversation store for minutes.
  • With a Codex budget alert set, Codex commands, the dashboard and Claude usage recording no longer occasionally stall for about 10 seconds.
  • The dashboard first-run hint now sits behind any open dialog or sheet, so on a phone it no longer covers the bottom of the Doctor dialog or blocks taps there.
  • Long same-name project names in the dashboard Projects panel, its Projects window and a Codex project's detail now shorten the name itself, keeping the (…) part that tells them apart and, on All, the provider prefix visible.
  • In the dashboard Codex block and project details, +N more now shows the extra rows in the dialog itself instead of in a small inner scroll box whose hidden scrollbar made the button look as if it did nothing.
  • A timed-out cctally dashboard diagnosis no longer risks signalling an unrelated process; a new diagnosis starts only after the previous worker and everything it started have exited.
  • Transcript search no longer misses messages an earlier SQLite build tokenized differently or leaves orphaned entries: the dashboard and cache-sync check the search indexes after an upgrade and every 30 days, rebuilding any that disagree.
  • diff --help and its reference page no longer say --sync runs sync-week; it refreshes the selected providers' cached usage data.
  • When the stats.db maintenance lock cannot be locked because of a file system error, cctally now names that error instead of saying maintenance is in progress.
  • When stats.db is busy, being upgraded or cannot be read, cctally explain with a week --window now reports the store as unavailable (exit 3, or 503 in the dashboard) instead of saying no subscription-week anchor is available.
  • In the dashboard Projects panel at window widths of about 1200 to 1440 px, the heading's project count or status no longer runs under the partial chip; the chip moves to its own line.

v1.120.0

v1.120.0 Pre-release
Pre-release

Choose a tag to compare

@omrikais omrikais released this 17 Nov 02:43

Added

  • cctally db reindex-search checks the conversation search indexes against their messages and rebuilds any that disagree; --check only reports.

Changed

  • Commands you run now stop waiting on cache.db or conversations.db maintenance after 5 seconds, as they already did for stats.db. Hooks, the status-line writer (record-usage) and background work keep waiting.
  • cctally db status now only reads your databases: it no longer resumes an interrupted stats rebuild; the next command that shows or records usage, such as report or the status line, finishes it instead.
  • On a large usage history, the dashboard no longer pauses for most of a second every few seconds while it refreshes, so pages and live updates respond more evenly. It costs about 30 MB more memory.
  • While cache.db is being repaired, the dashboard no longer reads it: conversation search and the reader, Explain and project detail are unavailable until the repair ends, and the Projects panel keeps the data it already shows.
  • The dashboard no longer updates or repairs databases while answering a page: a block detail reads stored usage, or your session files during a rebuild, and the dashboard's background work fixes what a page finds.
  • Right after an upgrade, db status and doctor show a stats.db from an older version as not readable until the next command converts it.
  • After a gap without a running cctally dashboard, its transcript catch-up writes about 9% less to conversations.db. Search results are unchanged.
  • When the Codex hooks that cctally setup installs are enabled, the first Codex turn after deleted Codex sessions are cleaned up no longer redoes that cleanup's quota work, so it stays fast.
  • With an account selected, the dashboard Conversation Viewer and transcript commands respond much faster: they reuse the conversation summaries they can verify instead of rebuilding the account's whole list. Results are unchanged.
  • The first cache build after installing, and cache-sync --rebuild, now write about half as much to disk and finish sooner on large histories. Usage and cost results are unchanged.
  • Title search in the dashboard Conversation Viewer and transcript search --kind title no longer reads every stored message, so it stays fast however large the transcript history is. Results are unchanged.

Fixed

  • When cache.db exists but cannot be read, cctally pricing-check no longer says every observed model is priced: it reports Coverage: unavailable (cache.db could not be read). and a degraded check (cache in --json).
  • When cache.db is found corrupt while an upgrade runs its database steps, cctally no longer deletes it; the next command quarantines a copy and rebuilds it through the normal recovery.
  • On macOS, remounting the external drive or disk image that holds the data folder no longer makes the next sync rebuild the Codex quota index.
  • Codex quota blocks, milestones and alerts stay accurate when updates overlap, Spark windows keep their dashboard block detail, and re-enabled alerts notify again. Turning alerts on or changing their rules no longer stalls Codex turns.
  • After an upgrade, the dashboard Conversation Viewer re-checks its stored session summaries a few at a time, so a session cost that had fallen behind its usage records is corrected.
  • On Linux, the stats rebuild memory peak that cctally doctor and cctally db status report no longer includes the peak of the process that started the rebuild, which could raise a false 2 GiB memory warning.
  • With an account selected, a dashboard Conversation Viewer model chip and transcript search --account with --model no longer fail; they list that account's conversations that used the chosen model family, and the search hits in them.
  • The dashboard Conversation Viewer's session costs, cost filter and sort, and cache-rebuild counts now update when usage records change or are removed without a transcript change, and after an interrupted sync.
  • cache-sync --prune-orphans no longer fails when a removed session continues in another project, and neither a pricing refresh of the session list nor cache-sync --rebuild blocks the conversation store for minutes.
  • With a Codex budget alert set, Codex commands, the dashboard and Claude usage recording no longer occasionally stall for about 10 seconds.
  • The dashboard first-run hint now sits behind any open dialog or sheet, so on a phone it no longer covers the bottom of the Doctor dialog or blocks taps there.
  • Long same-name project names in the dashboard Projects panel, its Projects window and a Codex project's detail now shorten the name itself, keeping the (…) part that tells them apart and, on All, the provider prefix visible.
  • In the dashboard Codex block and project details, +N more now shows the extra rows in the dialog itself instead of in a small inner scroll box whose hidden scrollbar made the button look as if it did nothing.
  • A timed-out cctally dashboard diagnosis no longer risks signalling an unrelated process; a new diagnosis starts only after the previous worker and everything it started have exited.
  • Transcript search no longer misses messages an earlier SQLite build tokenized differently or leaves orphaned entries: the dashboard and cache-sync check the search indexes after an upgrade and every 30 days, rebuilding any that disagree.
  • diff --help and its reference page no longer say --sync runs sync-week; it refreshes the selected providers' cached usage data.
  • When the stats.db maintenance lock cannot be locked because of a file system error, cctally now names that error instead of saying maintenance is in progress.
  • When stats.db is busy, being upgraded or cannot be read, cctally explain with a week --window now reports the store as unavailable (exit 3, or 503 in the dashboard) instead of saying no subscription-week anchor is available.
  • In the dashboard Projects panel at window widths of about 1200 to 1440 px, the heading's project count or status no longer runs under the partial chip; the chip moves to its own line.

v1.118.2

Choose a tag to compare

@omrikais omrikais released this 07 Nov 07:51

Stable upgrade: v1.117.2 → v1.118.2

Includes every released CHANGELOG section in this range, newest first.

[1.118.2] - 2026-11-07

Changed

  • The Codex hooks that cctally setup installs no longer re-read the whole quota history to resolve reset anchors, so recording new Codex usage stays fast on a long history.

Fixed

  • The dashboard and TUI now regroup a project within about a minute after a git worktree is removed, a repository is created or moved, or a folder becomes a repository; previously they kept the old grouping until restarted.

[1.118.1] - 2026-11-06

Fixed

  • With an account selected, the dashboard Conversation Viewer and transcript commands now show conversations' AI titles, and title search ranks, prefix-matches and highlights them; a session spanning two accounts keeps its fallback title.
  • After a rebuild of the conversation cache, the dashboard Conversation Viewer no longer shows an AI title that a replaced or truncated transcript no longer contains.
  • The dashboard Conversation Viewer no longer hides a conversation's earlier messages and AI title until the next rebuild after an unfinished last line is trimmed from its transcript.

[1.118.0] - 2026-11-06

Added

  • Codex cost reports price gpt-6.1-terra, gpt-6-rosalind and gpt-6-astra-law from their published rate cards, and gpt-5.5-cyber-preview as gpt-5.5-cyber, instead of falling back to gpt-5 rates.

Changed

  • cctally doctor checks an unchanged journal about three times faster. It keeps a small cache of its journal scan in the journal folder and verifies the journal against it by hash, so every check still sees every byte.
  • Repairing or fully re-reading Codex history (cctally cache-sync --source codex or the background worker) no longer locks the cache for the whole run, so Codex hooks keep recording usage during a history repair, and repairs re-read less.
  • While a Codex history repair runs (cctally cache-sync --source codex or the background worker), a Claude Code hook that arrives mid-step now waits briefly for its turn, so your Claude usage is recorded right away, not minutes later.
  • Upgrade rebuilds of stats.db and cctally db rederive finish much faster on large journals, and cctally db rederive uses less memory. Upgrade rebuilds, db rebuild --db stats and db rederive --yes write far less to disk.

Fixed

  • Sessions from a removed git worktree now show and group under their repository in project, the dashboard and the Conversation Viewer instead of .worktrees; a .git folder counts only when it holds a repository.
  • Codex conversation project labels in the dashboard Conversation Viewer now stay current: a label left on an earlier folder or (unassigned) is corrected on the next full refresh.
  • Anonymized Codex transcript export output now scrubs both the repository name and the session folder's own name, as Claude exports already do.
  • The dashboard no longer rescans every Claude transcript on every refresh when its cache still tracks transcripts that were deleted from disk.
  • Compressed Codex history that fails conversation verification no longer keeps the dashboard rescanning every Claude and Codex transcript on each refresh; that history keeps its last verified view until it changes.
  • Upgrading from a cctally older than 1.74.0 on a Python without a zstd decoder keeps cached Codex history in codex-* reports; it is fully refreshed once Python 3.14+ or backports.zstd is available.
  • The dashboard's Doctor modal and cctally doctor now wait at most half a second in total for stats.db maintenance, instead of about 5 seconds per database read (40 to 60 seconds per report), and report the maintenance.
  • cctally doctor's Latest snapshot check no longer fails with "Hooks may be broken" when usage stays flat for over an hour; it now counts every accepted reading, and says when stats.db cannot be read.
  • The Current Week freshness chip in cctally dashboard and cctally tui no longer turns stale while usage stays flat; it now ages from the newest reading that confirms the shown percentage.
  • An interrupted cctally cache-sync --source codex --rebuild no longer gives Codex usage from before account tracking to the account logged in at the retry; it stays unattributed. A rebuild with an unreadable rollout now stays pending.
  • A running dashboard now shows corrected usage, milestone and block figures after a stored correction (db rederive, a rebuild or an in-place fix) without a new sample, and a reopened Claude or Codex cycle detail shows current figures.
  • explain's short-conversations-with-large-context class no longer measures prior-generation Claude requests above 200K tokens against a 200K window, and reports a request it cannot place as undecided instead of guessing.
  • cctally dashboard --no-sync started while stats.db is being rebuilt after an upgrade or repaired after corruption now shows your data once that finishes, instead of staying empty until a restart.
  • Conversation Viewer search results in the dashboard now keep a transcript's own square brackets, such as [WARN], as text and highlight only the words your search matched.
  • The dashboard Conversation Viewer header now shows a Codex conversation's project and git branch, or no branch recorded when Codex saved none, instead of —, as it does for a Claude conversation opened from All.
  • The statusline no longer runs at full CPU for minutes after recording a reading on macOS, and Claude Code hooks no longer pile up behind it: a hook-tick that finds another usage refresh already in progress skips its own.
  • Removing cached Codex history for deleted rollout files (cctally cache-sync and the background cleanup) and recording Codex conversation updates no longer slow down as history grows; a 20-minute cleanup now takes a few minutes.

v1.118.1

v1.118.1 Pre-release
Pre-release

Choose a tag to compare

@omrikais omrikais released this 06 Nov 21:43

Fixed

  • With an account selected, the dashboard Conversation Viewer and transcript commands now show conversations' AI titles, and title search ranks, prefix-matches and highlights them; a session spanning two accounts keeps its fallback title.
  • After a rebuild of the conversation cache, the dashboard Conversation Viewer no longer shows an AI title that a replaced or truncated transcript no longer contains.
  • The dashboard Conversation Viewer no longer hides a conversation's earlier messages and AI title until the next rebuild after an unfinished last line is trimmed from its transcript.

v1.118.0

v1.118.0 Pre-release
Pre-release

Choose a tag to compare

@omrikais omrikais released this 06 Nov 11:18

Added

  • Codex cost reports price gpt-6.1-terra, gpt-6-rosalind and gpt-6-astra-law from their published rate cards, and gpt-5.5-cyber-preview as gpt-5.5-cyber, instead of falling back to gpt-5 rates.

Changed

  • cctally doctor checks an unchanged journal about three times faster. It keeps a small cache of its journal scan in the journal folder and verifies the journal against it by hash, so every check still sees every byte.
  • Repairing or fully re-reading Codex history (cctally cache-sync --source codex or the background worker) no longer locks the cache for the whole run, so Codex hooks keep recording usage during a history repair, and repairs re-read less.
  • While a Codex history repair runs (cctally cache-sync --source codex or the background worker), a Claude Code hook that arrives mid-step now waits briefly for its turn, so your Claude usage is recorded right away, not minutes later.
  • Upgrade rebuilds of stats.db and cctally db rederive finish much faster on large journals, and cctally db rederive uses less memory. Upgrade rebuilds, db rebuild --db stats and db rederive --yes write far less to disk.

Fixed

  • Sessions from a removed git worktree now show and group under their repository in project, the dashboard and the Conversation Viewer instead of .worktrees; a .git folder counts only when it holds a repository.
  • Codex conversation project labels in the dashboard Conversation Viewer now stay current: a label left on an earlier folder or (unassigned) is corrected on the next full refresh.
  • Anonymized Codex transcript export output now scrubs both the repository name and the session folder's own name, as Claude exports already do.
  • The dashboard no longer rescans every Claude transcript on every refresh when its cache still tracks transcripts that were deleted from disk.
  • Compressed Codex history that fails conversation verification no longer keeps the dashboard rescanning every Claude and Codex transcript on each refresh; that history keeps its last verified view until it changes.
  • Upgrading from a cctally older than 1.74.0 on a Python without a zstd decoder keeps cached Codex history in codex-* reports; it is fully refreshed once Python 3.14+ or backports.zstd is available.
  • The dashboard's Doctor modal and cctally doctor now wait at most half a second in total for stats.db maintenance, instead of about 5 seconds per database read (40 to 60 seconds per report), and report the maintenance.
  • cctally doctor's Latest snapshot check no longer fails with "Hooks may be broken" when usage stays flat for over an hour; it now counts every accepted reading, and says when stats.db cannot be read.
  • The Current Week freshness chip in cctally dashboard and cctally tui no longer turns stale while usage stays flat; it now ages from the newest reading that confirms the shown percentage.
  • An interrupted cctally cache-sync --source codex --rebuild no longer gives Codex usage from before account tracking to the account logged in at the retry; it stays unattributed. A rebuild with an unreadable rollout now stays pending.
  • A running dashboard now shows corrected usage, milestone and block figures after a stored correction (db rederive, a rebuild or an in-place fix) without a new sample, and a reopened Claude or Codex cycle detail shows current figures.
  • explain's short-conversations-with-large-context class no longer measures prior-generation Claude requests above 200K tokens against a 200K window, and reports a request it cannot place as undecided instead of guessing.
  • cctally dashboard --no-sync started while stats.db is being rebuilt after an upgrade or repaired after corruption now shows your data once that finishes, instead of staying empty until a restart.
  • Conversation Viewer search results in the dashboard now keep a transcript's own square brackets, such as [WARN], as text and highlight only the words your search matched.
  • The dashboard Conversation Viewer header now shows a Codex conversation's project and git branch, or no branch recorded when Codex saved none, instead of —, as it does for a Claude conversation opened from All.
  • The statusline no longer runs at full CPU for minutes after recording a reading on macOS, and Claude Code hooks no longer pile up behind it: a hook-tick that finds another usage refresh already in progress skips its own.
  • Removing cached Codex history for deleted rollout files (cctally cache-sync and the background cleanup) and recording Codex conversation updates no longer slow down as history grows; a 20-minute cleanup now takes a few minutes.

v1.117.2

Choose a tag to compare

@omrikais omrikais released this 03 Nov 07:45

Stable upgrade: v1.116.1 → v1.117.2

Includes every released CHANGELOG section in this range, newest first.

[1.117.2] - 2026-11-03

Fixed

  • With more than one Claude account, the cctally dashboard Current Week card and modal show one account's cycle, milestones, spend and $/1% beside that account's label, and the older/newer cycle buttons stay on that account.
  • cctally five-hour-breakdown and the dashboard's five-hour milestones show — (null in --json) instead of a weekly percentage that a weekly credit later retired.
  • With more than one Claude account, the cctally dashboard All view shows its combined spend headline, summing each account's current cycle, instead of usually leaving it out.
  • Under Python 3.11, cctally quota --json no longer reports family shares and calibration figures that differ in their last digits from newer Python versions.

[1.117.0] - 2026-11-02

Added

  • cctally doctor adds accounts.claude_cost_attribution, reporting how recent Claude cost was attributed to accounts and the progress of the one-time upgrade step that records existing attribution.

Changed

  • cctally quota no longer withholds a forecast over a small Sonnet 5.5 share shift that meter evidence shows to be immaterial, and withheld lines name the family reason. Stored calibrations go stale until the next cctally quota run.
  • When a reviewed cctally db rederive correction changes a calibration's inputs, cctally forecast and the dashboard withhold calibrated figures ("recalibration needed") until cctally quota refits. Stats rebuilds once on upgrade.
  • A metering-rate change fitted from corrected inputs no longer shows its status-line marker or sends its notification; the dashboard's Recent Alerts keeps it, labelled "superseded by a correction".
  • After a gap without a running cctally dashboard, its first transcript catch-up writes less to conversations.db, and cctally dashboard-perf and cctally doctor no longer judge that catch-up as steady-state disk writes.
  • Automatic credit, early-reset and status-line drop detection paused by an older cctally process now resumes on its own, per account and per limit; cctally doctor shows what each limit waits for. Stats rebuilds once on upgrade.

Fixed

  • A stats.db upgrade rebuild or cctally db rebuild --db stats no longer reprices closed five-hour blocks and their milestones at the current rate card when it recovers missing records.
  • Archived Codex threads now count in codex-* reports, quota history and the dashboard, and archiving no longer deletes history. Archived usage first seen with no recorded account stays unattributed unless quota windows assign it.
  • On Python builds that link SQLite 3.54.1, a running cctally dashboard reclaims transcript space freed by retention again, so conversations.db shrinks instead of keeping the freed pages.
  • An idle Claude Code session's stale cctally statusline reading no longer records a false weekly reset, five-hour credit or zero-cost milestone once a later usage check reads higher; the stats index rebuilds once after upgrading.
  • Claude cost is attributed to the account active when Claude Code wrote it, not the one active when cctally read it. Upgrades and cctally cache-sync --rebuild keep each row's account.
  • cctally statusline measures 🧠 context % against the session's real context window (1M for Opus, Sonnet and Haiku 5.5), so an Opus 5.5 session no longer shows a red percentage five times too high and Fable sessions no longer show N/A.
  • A stats.db upgrade rebuild could exit early as busy when a status-line check for a running rebuild landed at the instant it started, delaying the rebuild; that check no longer interferes with a starting rebuild.
  • cctally explain and the dashboard's Explain view measure Opus, Sonnet and Haiku 5.5 requests against their 1M context window and now evaluate Fable requests, so short conversations are no longer flagged for large context against 200K.
  • cctally five-hour-blocks, cctally five-hour-breakdown and the dashboard keep each five-hour window's genuine peak, milestones and readings through a usage credit and through every stats.db rebuild, instead of dropping some.
  • cctally record-credit records the exact --at time instead of the start of that hour, keeping readings taken earlier in that hour, and a --force replacement at the replaced credit's own second now takes effect.
  • A weekly usage credit is no longer lost when recording is interrupted while it is being saved.
  • After stats.db is rebuilt from a missing or corrupt file, the stats index keeps updating incrementally instead of falling back to rereading the whole recorded history.
  • On an exFAT data folder, cctally now quarantines and rebuilds a corrupt conversations.db or cache.db and can run db repair --db stats, and a rebuild no longer fails after 20 s while another cctally process has the store open but idle.
  • On macOS, cctally cache-sync --rebuild no longer writes a full copy of conversations.db on volumes without copy-on-write clones (HFS+, exFAT); there and on Linux ext4 its integrity check runs in place when no write-ahead log is pending.
  • cctally dashboard no longer waits on a reverse-DNS lookup of its bind address before it prints its URL and serves, a wait that lasted the resolver's whole timeout where the network never answers that lookup.
  • Codex hooks installed by cctally setup no longer stall Codex sessions for over 10 seconds on large histories or after upgrading, or for over a minute with Codex budget alerts on; leftover work runs in the background.
  • cctally db rederive restores a five-hour milestone's cost when an earlier rederive repriced it under a closed block; one whose history is ambiguous keeps its cost and is listed in withheldMilestoneRepairs.

v1.117.0

v1.117.0 Pre-release
Pre-release

Choose a tag to compare

@omrikais omrikais released this 02 Nov 23:14

Added

  • cctally doctor adds accounts.claude_cost_attribution, reporting how recent Claude cost was attributed to accounts and the progress of the one-time upgrade step that records existing attribution.

Changed

  • cctally quota no longer withholds a forecast over a small Sonnet 5.5 share shift that meter evidence shows to be immaterial, and withheld lines name the family reason. Stored calibrations go stale until the next cctally quota run.
  • When a reviewed cctally db rederive correction changes a calibration's inputs, cctally forecast and the dashboard withhold calibrated figures ("recalibration needed") until cctally quota refits. Stats rebuilds once on upgrade.
  • A metering-rate change fitted from corrected inputs no longer shows its status-line marker or sends its notification; the dashboard's Recent Alerts keeps it, labelled "superseded by a correction".
  • After a gap without a running cctally dashboard, its first transcript catch-up writes less to conversations.db, and cctally dashboard-perf and cctally doctor no longer judge that catch-up as steady-state disk writes.
  • Automatic credit, early-reset and status-line drop detection paused by an older cctally process now resumes on its own, per account and per limit; cctally doctor shows what each limit waits for. Stats rebuilds once on upgrade.

Fixed

  • A stats.db upgrade rebuild or cctally db rebuild --db stats no longer reprices closed five-hour blocks and their milestones at the current rate card when it recovers missing records.
  • Archived Codex threads now count in codex-* reports, quota history and the dashboard, and archiving no longer deletes history. Archived usage first seen with no recorded account stays unattributed unless quota windows assign it.
  • On Python builds that link SQLite 3.54.1, a running cctally dashboard reclaims transcript space freed by retention again, so conversations.db shrinks instead of keeping the freed pages.
  • An idle Claude Code session's stale cctally statusline reading no longer records a false weekly reset, five-hour credit or zero-cost milestone once a later usage check reads higher; the stats index rebuilds once after upgrading.
  • Claude cost is attributed to the account active when Claude Code wrote it, not the one active when cctally read it. Upgrades and cctally cache-sync --rebuild keep each row's account.
  • cctally statusline measures 🧠 context % against the session's real context window (1M for Opus, Sonnet and Haiku 5.5), so an Opus 5.5 session no longer shows a red percentage five times too high and Fable sessions no longer show N/A.
  • A stats.db upgrade rebuild could exit early as busy when a status-line check for a running rebuild landed at the instant it started, delaying the rebuild; that check no longer interferes with a starting rebuild.
  • cctally explain and the dashboard's Explain view measure Opus, Sonnet and Haiku 5.5 requests against their 1M context window and now evaluate Fable requests, so short conversations are no longer flagged for large context against 200K.
  • cctally five-hour-blocks, cctally five-hour-breakdown and the dashboard keep each five-hour window's genuine peak, milestones and readings through a usage credit and through every stats.db rebuild, instead of dropping some.
  • cctally record-credit records the exact --at time instead of the start of that hour, keeping readings taken earlier in that hour, and a --force replacement at the replaced credit's own second now takes effect.
  • A weekly usage credit is no longer lost when recording is interrupted while it is being saved.
  • After stats.db is rebuilt from a missing or corrupt file, the stats index keeps updating incrementally instead of falling back to rereading the whole recorded history.
  • On an exFAT data folder, cctally now quarantines and rebuilds a corrupt conversations.db or cache.db and can run db repair --db stats, and a rebuild no longer fails after 20 s while another cctally process has the store open but idle.
  • On macOS, cctally cache-sync --rebuild no longer writes a full copy of conversations.db on volumes without copy-on-write clones (HFS+, exFAT); there and on Linux ext4 its integrity check runs in place when no write-ahead log is pending.
  • cctally dashboard no longer waits on a reverse-DNS lookup of its bind address before it prints its URL and serves, a wait that lasted the resolver's whole timeout where the network never answers that lookup.
  • Codex hooks installed by cctally setup no longer stall Codex sessions for over 10 seconds on large histories or after upgrading, or for over a minute with Codex budget alerts on; leftover work runs in the background.
  • cctally db rederive restores a five-hour milestone's cost when an earlier rederive repriced it under a closed block; one whose history is ambiguous keeps its cost and is listed in withheldMilestoneRepairs.

v1.116.1

Choose a tag to compare

@omrikais omrikais released this 28 Oct 10:47

Stable upgrade: v1.113.0 → v1.116.1

Includes every released CHANGELOG section in this range, newest first.

[1.116.1] - 2026-10-28

Maintenance

  • Internal improvements only; no user-facing changes.

[1.116.0] - 2026-10-28

Added

  • cctally doctor, cctally db status and the dashboard's Doctor chip now say when a stats.db upgrade rebuild or auto-heal is running, has stalled, failed or died, or used more memory than its bound.

Changed

  • The stats.db upgrade rebuild that runs after an update, cctally db rebuild and cctally db rederive use far less memory and disk, and the upgrade rebuild finishes faster.

Fixed

  • After a usage credit, cctally statusline refuses an idle session's cached usage once it is proven stale, and five-hour views stop hiding genuine weekly values. cctally db rederive adds retract; stats.db rebuilds once after upgrading.
  • Under Python 3.11, cctally quota --json no longer reports a mix-support radius that differs in its last digits from one run to the next.
  • cctally quota --json reports the same eligibilityFence on Linux as on macOS; on Linux it could differ in its last digits.
  • A sync with nothing new to read no longer rewrites the compressed Codex rollout status in cache.db and conversations.db, so an idle cctally dashboard writes less to disk.
  • cctally cache-sync --rebuild rebuilds transcripts again on a filesystem without copy-on-write clones, such as ext4 on Linux, instead of failing every time.
  • On Python 3.11, the upgrade that moves transcripts out of cache.db now shrinks the file as intended. If you already upgraded on Python 3.11, run cctally db vacuum --db cache to reclaim the space.

[1.115.0] - 2026-10-21

Added

  • cctally doctor has two new checks: Legacy writer warns while an older cctally process left running across the upgrade is still writing or its status-line files cannot be read, and Outcome quarantine names each paused account and why.
  • cctally quota recognises Claude Opus 5.5, Sonnet 5.5 and Haiku 5.5 and weights usage from 2026-09-22 with Opus 5.5 coefficients, fitting it when the model-mix checks pass; a week spanning that date is not modelled.

Changed

  • The status line now records every reading under the Claude account active when it was captured, so switching accounts can no longer file one account's usage under another.
  • Upgrading marks a one-time cutover: anything an older cctally process writes afterwards, including after a downgrade and re-upgrade, is kept out of your usage history. Restart such processes, usually a cctally dashboard.
  • After an older process writes post-upgrade, credit and reset detection pauses until each account reads clean, or indefinitely if status-line files changed or are unreadable; usage still records, and cctally record-credit records resets.
  • cctally record-usage exits 2 and records nothing when the active Claude account cannot be read consistently, instead of recording under a guessed account.
  • Existing cctally quota calibrations become incompatible immediately; each account's is replaced on its next successful automatic fit, and a diagnostic run or too little Opus 5.5 history leaves the old one stored and ignored.

Fixed

  • Codex reports now read compressed rollouts (.jsonl.zst) without losing cached history, slow history cleanup no longer runs inside the Codex hook, and cctally doctor has a new Compressed Codex rollouts check.
  • daily, session and other Claude cost reports price Sonnet 5.5 cache reads at $0.10 per million tokens instead of $0.20. Recorded snapshots, closed blocks and milestones keep their original amounts.
  • The status line's 5-hour figure no longer changes, or retries a pending drop, when another account's 5-hour reset is recorded.
  • cctally db rebuild --db stats no longer drops percent milestones after a 5-hour or manual credit, which also stalled recording afterwards; this upgrade's one-time rebuild restores them.
  • A usage reading recorded right after an upgrade while an older cctally process (such as a dashboard) was still running, or during cctally db rebuild --db stats or a stats index repair, no longer goes missing or waits for a later reading.
  • cctally db rebuild --db stats keeps the current 5-hour block's first-seen time and pricing details as recorded. It no longer moves that time after a 5-hour credit or when two readings were recorded out of order.
  • The status line, dashboard, TUI, forecast, five-hour-blocks and five-hour-breakdown show the latest 5-hour reading when the newest reading has none, instead of a blank or 0 % 5-hour figure or a closed current block.
  • A 5-hour credit no longer discards a weekly reading recorded alongside the stale 5-hour figure, so the weekly figure no longer falls back to an older value.
  • A weekly credit detected mid-week no longer discards the 5-hour reading recorded with the stale weekly figure, so the status line, 5-hour blocks and 5-hour milestones keep it, and upgrading restores readings already lost.

[1.114.0] - 2026-10-08

Added

  • cctally dashboard-perf reports the dashboard's disk writes per minute and per publication against a write budget, and cctally doctor warns when a running dashboard or transcript maintenance exceeds it.
  • Claude cost reports price claude-haiku-5-5 at its published rates, including the higher rates for a request whose prompt exceeds 100,000 tokens, instead of showing $0.

Changed

  • cctally db vacuum --db cache or --db conversations started while the dashboard runs now asks it to release the store and waits up to 20 seconds before vacuuming, or refusing with the same message as before.
  • cctally doctor no longer warns about modest free space in conversations.db; it warns only while a large backlog (over 2 GiB and 20% of the file) is being reclaimed at a paced rate, and says why when reclaim is refused.

Fixed

  • Statusline and usage recording avoid redundant sorting of retained snapshots and expired blocks, with the same quota readings and publication order.
  • The dashboard block cost chart shows every trajectory sample when it exceeds a retained total.
  • The dashboard Sessions filter and sort icons keep their intended size on phones.
  • The dashboard keeps same-name project suffixes and panel counts readable, contains account status chips on phones, and keeps the swipe cue clear of spend details. Returning to All accounts starts at the first card.
  • cctally db rederive keeps five-hour milestone marginal costs consistent when applying reviewed weekly decisions, and resolves held-close corrections in one apply so the next preview needs no further correction on identical inputs.
  • cctally dashboard Codex panels now match a fresh rebuild after a memory-cache reset, a brief metadata or account-registry read error, a past-window share, or a window move under a Codex budget, instead of doubling, going stale or failing.
  • cctally db rederive now reports a cache.db that is missing a column it needs as missing-source (exit 2), naming the column, instead of failing with an internal error (exit 3).
  • cctally db rederive no longer fails with an internal error when cache.db still holds a transcript search index that this Python's SQLite cannot load.
  • Milestone tables put a negative amount's sign before the dollar sign: −$71.21 in the dashboard cycle modal, -$71.21 in the TUI, and -$71.210000 in five-hour-breakdown, percent-breakdown and report --detail, not $-71.21.
  • cctally dashboard no longer writes about a gigabyte a minute to disk on a large history: steady-state writes now follow new transcript data, and removing expired transcripts and reclaiming their space are paced.
  • cctally dashboard, cctally cache-sync and the Codex hook no longer write SQLite temp files while syncing transcripts and quota data, and two background lookups no longer re-sort a whole session's or quota window's history.

v1.116.0

v1.116.0 Pre-release
Pre-release

Choose a tag to compare

@omrikais omrikais released this 28 Oct 07:48

Added

  • cctally doctor, cctally db status and the dashboard's Doctor chip now say when a stats.db upgrade rebuild or auto-heal is running, has stalled, failed or died, or used more memory than its bound.

Changed

  • The stats.db upgrade rebuild that runs after an update, cctally db rebuild and cctally db rederive use far less memory and disk, and the upgrade rebuild finishes faster.

Fixed

  • After a usage credit, cctally statusline refuses an idle session's cached usage once it is proven stale, and five-hour views stop hiding genuine weekly values. cctally db rederive adds retract; stats.db rebuilds once after upgrading.
  • Under Python 3.11, cctally quota --json no longer reports a mix-support radius that differs in its last digits from one run to the next.
  • cctally quota --json reports the same eligibilityFence on Linux as on macOS; on Linux it could differ in its last digits.
  • A sync with nothing new to read no longer rewrites the compressed Codex rollout status in cache.db and conversations.db, so an idle cctally dashboard writes less to disk.
  • cctally cache-sync --rebuild rebuilds transcripts again on a filesystem without copy-on-write clones, such as ext4 on Linux, instead of failing every time.
  • On Python 3.11, the upgrade that moves transcripts out of cache.db now shrinks the file as intended. If you already upgraded on Python 3.11, run cctally db vacuum --db cache to reclaim the space.