Skip to content
vladkensPublic

About

Active time, tokens and estimated cost per project from local Claude Code, Codex, pi and fx history. Rust CLI with an interactive TUI.

Topics

Resources

Stars

12 stars

Watchers

0 watching

Forks

Latest commit

ย 

History

58 Commits

Folders and files

NameName
Last commit message
Last commit date
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 

Repository files navigation

cctrail

Where your AI coding time and tokens go, per project

version license built with ratatui follow @uid127

cctrail reads the local history of Claude Code, Codex, pi and fx and shows, for each project, how much time you spent in it, how many tokens it used and what that would cost at API prices. It needs no setup: repositories are found from the sessions themselves, with agent worktrees and clones counted as one project.

cctrail's interactive view: the projects for the last 30 days and a project's models, the models with their cost per hour and per million tokens and one split by harness, speed and effort, the timeline of days stacked by model by time and by cost, and the swears per model

๐ŸŒŸ Features

  • โฑ๏ธ Real hours. Active time per project: idle gaps don't count, parallel projects split it.
  • ๐Ÿ’ฐ Estimated cost. Each request at the API price of its day, to compare with your subscription.
  • ๐Ÿงฎ No double counting. History copied into subagents, forks or another profile counts once.
  • ๐ŸŒณ No setup. Reads the history already on disk; worktrees and clones fold into their repository.
  • ๐Ÿ‘ฅ All accounts. Every Claude Code and Codex profile (~/.claude-work) in one report.
  • ๐Ÿ–ฅ๏ธ Interactive. Projects, models and a timeline by model, with drill-downs and the mouse.
  • ๐Ÿ“Š Scriptable. Reports by day, week or month, per project, group or model, and JSON.
  • โšก Fast and private. Seconds for gigabytes of history, which never leaves your machine.

๐Ÿ“ฅ Installation

Download the archive for macOS (Apple Silicon), Linux (x86_64 or arm64, glibc 2.28 or newer) or Windows (x86_64) from the latest release and put cctrail (cctrail.exe) into a folder on your PATH, such as ~/.local/bin. Or build it with Rust:

cargo install cctrail

Newest version

This readme follows main, which may be ahead of the latest release. Binaries of main are in the dev release, or build it with Rust:

cargo install --git https://github.com/vladkens/cctrail

๐Ÿš€ Usage

cctrail                      # on a terminal: the interactive view (projects, models, timeline)
cctrail all                  # time, tokens and cost per project as text, all time
cctrail this-month           # for a period: today, yesterday, this-week, last-week, this-month, last-month
cctrail --since 2026-03-01   # from a date; --until sets the last day, both inclusive YYYY-MM-DD
cctrail --all                # every row; by default unconfigured dirs past 95% of the time fold into `other`
cctrail --by group           # per group from the config, or --by dir per working directory
cctrail here                 # the current directory's project: today, this week, this month, all time
cctrail days                 # per day; also weeks, months, and --models for a breakdown by model
cctrail --provider codex     # one harness only: claude, codex, pi or fx
cctrail --json               # everything with full paths and exact counts
cctrail update-pricing       # download the latest prices now
cctrail export FILE          # save the history into an SQLite file
cctrail import FILE          # add an exported history to the reports

Any argument, --json or a pipe prints a text report; NO_COLOR=1 turns its colors off. Weeks start on Monday. cctrail --help lists it all.

Interactive view

cctrail without arguments on a terminal opens the interactive view: projects, models, a timeline (a chart of the days stacked by model over their list) and swears for today, this week, this month, the last 30 days or all time. A model is one row whichever harness ran it, its dated id (-20250929) included; opening it splits it by harness and lists its weeks (days for a shorter period). Its $/h is the cost per active hour, its $/M the cost per million tokens as paid, with the cache, Fast and effort in it; the timeline's days and weeks have them too. Press ? in it to see the keys.

Swears shows how often you scold each model: % dir, the share of your messages scolding it, and a Score that pulls it toward your average, so a model you barely used doesn't top the list. How it counts.

The projects of cctrail's interactive view for the last 30 days: time, tokens, cost, sessions and share per project, with the total
Key Action
1 2 3 4 Projects, Models, Timeline, Swears
t T The next or the previous period
โ†‘ โ†“ PgUp PgDn Home End Move the selection
โ†’ Enter Open the row: a project's models, a model's harnesses, speeds, efforts and weeks, a day's projects
โ† Esc q Back; q quits from a list
s S Sort by the next column, reverse the sort; on the timeline s switches the bars between time, tokens and cost
p The provider: all, claude, codex, pi or fx
/ Filter by name: Enter keeps the filter, Esc clears it
? The keys

The mouse works too: a click selects a row or a bar and a second one opens it, a click on a column header sorts and a second one reverses, a click on a view, period or provider switches it, and the wheel moves the selection.

๐Ÿ“ Projects

Every repository is a row, named by its directory. Agent worktrees count as their repository (<repo>/.claude/worktrees/<name>, any <repo>/.<tool>/worktrees/<name>, <repo>/.worktrees/<name> and <repo>-worktrees/<name>), and clones of one repository at other paths (directories with the same name) count as the one used last. Temp directories, directories that hold other projects (~/Code) and clones Codex saw with different git remotes stay apart.

A config is optional: it names projects, merges several repositories into one and puts projects in groups for --by group. It lives in ~/.config/cctrail/config.toml (XDG_CONFIG_HOME moves the root, CCTRAIL_CONFIG sets the full path):

[projects]
"work/web-app" = ["~/Code/web-app", "~/Code/web-app-docs"]
"oss/cli-tool" = ["~/Code/cli-tool"]

Each key is <group>/<project>. A path includes everything below it, and the longest match wins. Repositories outside the config keep their own rows and form the @unmapped group.

๐Ÿงฎ How it counts

History

Harness Reads Override
Claude Code ~/.claude/projects and the same in every profile beside it (~/.claude-work) CLAUDE_CONFIG_DIR replaces all of them with one root
Codex ~/.codex/sessions and ~/.codex/archived_sessions, and the same in every profile beside them (~/.codex-personal) CODEX_HOME replaces all of them with one root
pi ~/.pi/agent/sessions and an absolute sessionDir from its settings.json PI_CODING_AGENT_DIR moves the agent directory, PI_CODING_AGENT_SESSION_DIR replaces both
fx ~/.fx/sessions FX_HOME, which only cctrail reads, moves ~/.fx

A forked pi session counts only what it added to the copy of its source. fx logs a session's tokens only as totals, so they are spread over its agents' activity, a share on every active day: exact per project, approximate per day. Claude Code deletes sessions older than 30 days by default: raise cleanupPeriodDays to keep a long history.

To move to another machine or keep a backup before the logs are deleted, cctrail export FILE saves the sessions cctrail reads into one SQLite file, and cctrail import FILE on the other machine adds them to every report, the interactive view included. The file holds what the numbers need (times, models, tokens, directories) and the swear counts, never a prompt's or answer's text; paths under your home are kept as ~/โ€ฆ and read back in the new one. An import is copied into ~/.local/share/cctrail (XDG_DATA_HOME; %LOCALAPPDATA% on Windows), once per file; a session still in the local logs is read from them, an imported one fills in what the logs no longer have.

Swearing

The Swears view: how often you scold each model, adjusted for how much you used it.

  • Text: your own prompts in main sessions. Not the harness's (tool output, slash commands and their output, reminders, environment context, skills, notifications, compaction summaries), not the prompts agents get from a model, not codex exec or the Claude Agent SDK, which scripts send.
  • Pastes: these go: code in backticks or ``` fences, quoted lines (> ), and runs of 3+ lines that aren't prose (few letters, times, dates, paths, key: value, table rows, code). Harness paste markers (Claude Code's [Pasted text #N], pastedContents in history.jsonl) aren't used: dictation tools insert text through the clipboard, so dictated prompts arrive marked as pastes and would be dropped.
  • Swearing: a word in en.txt, ru.txt or the insult lists insult-en.txt, insult-ru.txt. One entry a line: word, stem* (every word it starts), !word or !stem* (never: a stem's false positives), >word in an insult list (only next to an addressee). A word written as an entry in a prompt (stem*, from a pasted list) isn't swearing.
  • Directed: a prompt with an insult anywhere, or a swear word within 3 words of ั‚ั‹/you and their forms, or of a model's or agent's name (ะฐัั‚ั€ะฐ, claude, ะฐะณะตะฝั‚, modelโ€ฆ).
  • Attribution: to the model that answered last before the prompt, the first ones of a session to the first to answer; a prompt that a fork or copied file repeats counts once.
  • Columns: Msgs and Words, then % dir: messages scolding the model ยท % any: messages with any swearing ยท Score: % dir adjusted for few messages, (dir + 30 ร— overall) / (msgs + 30) ร— 100, overall being your % dir in the period, so a few messages can't move a model far from your average. Shares need 10 messages; messages to no known model are <unknown>.
  • Privacy: each prompt keeps only counts and a hash, never its text, for this view and cctrail export and import.
  • Your lists: ~/.config/cctrail/swear/*.txt, insults in insult-*.txt. Lists for other languages are welcome as pull requests.

Time

Every message opens a five-minute window; overlapping windows merge, and time spent in several projects at once is split between them. Tables show 8h 14m, or 45d 8h 14m from a day on.

Cost

An estimate at models.dev prices, each request at the price of its day, so a later price cut doesn't reprice old usage. Prices come from the models.dev git history and are refreshed in the background once a day (cctrail update-pricing does it now, CCTRAIL_NO_UPDATE=1 turns it off). codex-auto-review, which has no price, counts as gpt-6-luna.

pi's and fx's models read and are priced alike whatever the provider (Bedrock's us.anthropic.claude-opus-4-6-v1 as claude-opus-4-6, a router's openai/gpt-5.4 as gpt-5.4, fx's codex/gpt-6-astra as gpt-6-astra), at the harness's own estimate for a model models.dev lacks; an fx session in Fast mode counts at the fast rate throughout. Tokens on other unpriced models are listed below the report.

๐Ÿค Contributing

Pull requests are welcome, and so are your agents: point them at agents.md.

Installing a branch
cargo install --git https://github.com/vladkens/cctrail --branch feat/NAME --locked  # a PR branch
cargo install --git https://github.com/vladkens/cctrail --locked --force             # back to main
cargo install --path . --locked                                                      # a local checkout
cargo uninstall cctrail                                                              # remove it

๐Ÿ™ Credits

  • models.dev (MIT): the model prices, read from its git history for the price of each day.
  • ratatui (MIT): the interactive view.
  • SQLite (public domain) through rusqlite (MIT): cctrail export and import.

๐Ÿ“ License

Distributed under the MIT License.

About

Active time, tokens and estimated cost per project from local Claude Code, Codex, pi and fx history. Rust CLI with an interactive TUI.

Topics

Resources

Stars

12 stars

Watchers

0 watching

Forks

Releases

Packages

Used by

Contributors

Languages