Skip to content

Releases

v0.7.1

Choose a tag to compare

@github-actions github-actions released this 09 Oct 16:32
af0c0a6

Fixes

  • Ctrl+C exits quietly again (#126, #127). In v0.7.0, stopping cc-calendar with Ctrl+C printed a KeyboardInterrupt traceback and exited with a non-zero status. The server always shut down cleanly; only the message and the exit status were wrong. It now exits silently with status 0, as before, and still within a second while the page is open.

Upgrade

uv tool upgrade cc-calendar

Or with pipx: pipx upgrade cc-calendar. Then restart cc-calendar.

Full changelog: v0.7.0...v0.7.1

v0.7.0

Choose a tag to compare

@github-actions github-actions released this 09 Oct 16:26
39f3e55

New

  • Update notice (#121, #122): when a newer cc-calendar is on PyPI, the top bar shows vX.Y.Z available next to the version, linking to how to update, and the terminal prints a line about it. cc-calendar asks PyPI when it starts and once a day.

Note

This is cc-calendar's first network request. It carries only the running version (in the User-Agent) and nothing about your sessions. Turn it off with --no-update-check or CC_CALENDAR_NO_UPDATE_CHECK=1; then cc-calendar makes no network requests at all. See Privacy.

Fixes

  • Ctrl+C stops the server promptly while the page is open (#123, #124). The page's live update stream kept the server waiting until Ctrl+C was pressed again; it now exits in under a second.
  • No more flicker in the Pull requests pane (#119, #120). On each live update, the Pull requests, tool usage, cost and requests panes briefly showed "Loading…" and the page below jumped. They now keep their table until the new one is in.
  • PR titles such as $t (#117, #118). A PR opened with gh pr create --title "$t" (a shell variable) showed the variable instead of a title. Titles and branches built from shell expansions are no longer recorded. Where one command opened several PRs, each now gets its own title and branch, and a PR body that mentions gh pr create is no longer mistaken for the command.

Upgrade

uv tool upgrade cc-calendar

Or with pipx: pipx upgrade cc-calendar. Then restart cc-calendar. From this version on, the top bar tells you when an update is out.

Full changelog: v0.6.1...v0.7.0

v0.6.1

Choose a tag to compare

@github-actions github-actions released this 09 Oct 15:49
44e6337

New

  • Version in the top bar (#114, #115): the running cc-calendar version shows next to the logo and at the bottom of the keyboard shortcut list (?). After an update, it changes once cc-calendar is restarted, so you can tell whether the new version is running.

Docs

  • Update section in Getting started (#113): how to update with uv tool, uvx (uvx cc-calendar@latest), pipx, pip or a checkout, how to pin or go back to a version, and the restart needed afterwards.

Upgrade

uv tool upgrade cc-calendar

Or with pipx: pipx upgrade cc-calendar. Then restart cc-calendar.

Full changelog: v0.6.0...v0.6.1

v0.6.0

Choose a tag to compare

@github-actions github-actions released this 09 Oct 15:38
70fccea

This release is about cost and how a session went: where the money goes, what it bought, and where a session got stuck.

New

Cost

  • Cost per output (#74, #88): the Summary counts each project's commits and pull requests and shows $/commit. The list view adds a $/commit column and an Output → No output filter for sessions that cost money but produced nothing.
  • Cost per pull request (#75, #109): a Pull requests pane, and the same table on the project page, with each PR's sessions, active time, cost and commits. Later work on the PR's branch, such as review fixes, is added to it. The table exports as CSV or JSON.
  • Costs pane (#78, #91): cost by model and token type (input, output, cache write, cache read), with a row per day in the week and month views.
  • What-if cost (#85, #103): re-price the range as if one model's requests had run on another.
  • Idle re-cache (#83, #105): estimates what it cost to write the cache again after a break, per session and for the range.
  • Most expensive requests (#79, #92): a Top requests pane ranks prompts by cost. Click one to open the transcript there.
  • Monthly budget (#80, #102): the month view shows the spend so far, the daily average and the month-end projection, against an optional budget and plan price.

Time and activity

  • Compare with previous (#76, #101): the Summary shows each project next to the previous day, week, month or year.
  • Working vs waiting (#86, #108): active time splits into Claude's working time and the time it waited for you, with your median reply time. The day view adds a Parallel column with how many sessions ran at once.
  • Hours of the week (#81, #93): a weekday × hour heatmap of when you work.

How a session went

  • Ratings (#82, #94): mark a session ✓ Done, ◐ Partial or ✕ Failed, then filter and total by rating.
  • Friction (#87, #104): interrupts, API errors, prompts queued while Claude was working, and failed tool calls, per session and as a sortable list column.
  • Context size (#84, #106): a chart of the context each request resent. Sessions that keep resending more than 200k tokens are flagged as bloated.
  • Copy retrospective (#77, #107): copies the range as a prompt for Claude to draft a Keep / Problem / Try retrospective.

Export

  • New session fields: pull_requests, files_changed, lines_added, lines_removed, cost_per_commit, rating, idle_recache_usd, the friction counts and context_avg / context_peak / context_bloated. schema_version stays 1 (fields were only added). See Export format.

Fixed

  • A continued session counts only its own share of the cost record it carries over (#89, #90).
  • A continued session no longer counts the copy of the previous session that its log starts with (#96, #99).
  • A resumed session's cost now includes its earlier runs (#97, #100).
  • Prompts pasted as text, and prompts from the desktop app, are now counted (#95, #98).

Docs

  • Screenshots of the new features (#110, #111).

Upgrade

uv tool upgrade cc-calendar

Or with pipx: pipx upgrade cc-calendar. Then restart cc-calendar.

Full changelog: v0.5.0...v0.6.0

v0.5.0

Choose a tag to compare

@github-actions github-actions released this 07 Oct 04:37
5aedafe

cc-calendar now runs on Windows (#62).

New

  • Windows support (#70, #71). Tested on Windows 11 and covered by CI.
    • Sessions are read from %USERPROFILE%\.claude\projects\.
    • Notes are kept in %APPDATA%\cc-calendar\notes.json and the search index in %LOCALAPPDATA%\cc-calendar\search.db.
    • Copy resume command quotes Windows paths so the command works in cmd and PowerShell 7. In Windows PowerShell 5.1, replace the && with ;.

Fixed (Windows)

  • Checking whether a session is still running no longer risks sending Ctrl+C to running Claude Code processes (#70).
  • A corrupt full-text search index is now rebuilt instead of failing to be deleted (#70).
  • The first launch no longer crashes on consoles whose encoding cannot show the startup banner, such as Japanese Windows (#71).
  • Changes made to the notes file from elsewhere are no longer sometimes missed (#72).

Upgrade

uv tool upgrade cc-calendar

Or with pipx: pipx upgrade cc-calendar.

Full changelog: v0.4.1...v0.5.0

v0.4.1

Choose a tag to compare

@github-actions github-actions released this 04 Oct 10:51
1357f4d

Fixed

  • Viewing a transcript no longer contacts other hosts (#67).
    • An image linked in a transcript (![](https://…) or an <img> tag) used to be loaded by the browser. Now it is not loaded; it shows as a link you can open yourself.
    • The page also sends a Content-Security-Policy, so the browser loads nothing from other sites.

Docs

  • Install steps for pipx and pip (#68). uv is still the recommended way.

Upgrade

uv tool upgrade cc-calendar

Or with pipx: pipx upgrade cc-calendar.

Full changelog: v0.4.0...v0.4.1

v0.4.0

Choose a tag to compare

@github-actions github-actions released this 04 Oct 10:02
a2a65c9

cc-calendar is now on PyPI.

New

  • Full-text search (#12): tick Full text next to the search box to also search inside transcripts.
    • Searches assistant replies, tool inputs (commands, file paths, edits), tool output and subagent transcripts. Thinking is not searched.
    • Japanese and other languages without spaces work too.
    • Hits show a snippet in the list, the calendar tooltip and the detail pane. Open ↗ opens the transcript at the hit, and Matches steps through the rest.
    • The index is kept in an on-disk SQLite cache. It builds in the background and updates as logs grow. Move it with --search-index.
  • Notes and tags (#59): add a note and tags to a session in the detail pane.
    • Tags show in the list (Tags column and filter) and the calendar tooltip. The search box matches notes and tags.
    • Color by → Tag colors sessions by tag (#29). Exports include tags and notes.
    • They are saved in notes.json in your user data directory. Move it with --notes, e.g. to a synced folder.
  • Several config directories (#17): --claude-dir can be repeated to show sessions from several ~/.claude directories in one calendar.
    • Use it for directories synced from other machines, or for configs used with CLAUDE_CONFIG_DIR.
    • Each session shows where it came from: the Source column and filter, the detail pane, the tooltip and exports (#53). Color by → Source colors sessions by directory.
  • Project page (#28): click a project name to see it over all time. The page shows:
    • total active time and cost
    • activity by month
    • every session
    • its commit history
  • More list filters (#15): filter by model, git branch, date range and cost range.
  • Keyboard shortcuts (#10, #55):
    • ← / → move through ranges.
    • d / w / m / y pick the span.
    • j / k step through sessions, and Enter opens the transcript.
    • In a transcript, n / p step through events and ] / [ through prompts.
    • Press ? for the full list.
  • Views in the URL (#9): the address keeps the view, span, date, selected session and project page. Reloading keeps your place, Back and Forward work, and views can be bookmarked.
  • Desktop notifications (#24): turn on Notify to get notified, while the tab is in the background, when a session starts waiting for your input or ends without finishing.
  • Resume command (#23): Copy resume command copies cd <project dir> && claude --resume <session id>.

Fixed

  • Commits made with a heredoc message now get their SHA in the project page and the Markdown report, as they already did in the detail pane (#47).

Install

uv tool install cc-calendar
cc-calendar

Or run it without installing: uvx cc-calendar.

Upgrading from a git install of v0.3.0 or earlier: uv tool install --force cc-calendar. After that, update with uv tool upgrade cc-calendar.

Full changelog: v0.3.0...v0.4.0

v0.3.0

Choose a tag to compare

@atinfinity atinfinity released this 04 Oct 02:03
af2337f

New

  • Month and year views (#11): a month calendar and a GitHub-style yearly heatmap, one cell per day.
    • Cells are shaded by active time or cost.
    • Month cells list the day's busiest projects; the year view adds per-month totals.
    • Click a day or a month to open it.
  • Markdown report (#25): Copy report copies the displayed day, week, month or year as Markdown.
    • It lists active time and cost per project, each session's title, and the commits made in the range.
    • Issue and PR numbers such as #12 link to the repository's origin remote.
  • Tool usage (#14): the Tools pane covers the displayed range.
    • Most used tools, with error counts and rates.
    • Calls made inside subagents.
    • MCP servers.
    • Subagent runs by type, with their tokens and cost.
  • CSV / JSON export (#13): the list view can download the sessions shown, in the current filter and sort order.
    • Fields include start, end, active time, project, branch, status, prompts, tokens, cost, model, effort and Claude Code version.
    • JSON files carry a schema_version.
    • See the export format.
  • Cache efficiency (#26): each session shows its cache hit rate and roughly how much caching saved. Rates below 90% are highlighted.
  • Event marks (#27): marks on calendar bars show prompts, commits, compactions and API errors.
    • Click a mark to open the transcript at that point.
    • In the transcript, ‹ › step through each kind of event.
  • Effort and compactions (#33): the detail pane and transcript stats show the share of requests per effort level. Color by Effort is available too.
    • Each compaction shows its trigger and context size before → after, e.g. auto · 168k → 32k tokens.

Changed

  • /api/sessions now includes each session's Claude Code version and the cc-calendar version.

Project

Install

uv tool install git+https://github.com/atinfinity/cc-calendar@v0.3.0
cc-calendar

Upgrading from v0.2.0: uv tool install --force git+https://github.com/atinfinity/cc-calendar@v0.3.0

Full changelog: v0.2.0...v0.3.0

v0.2.0

Choose a tag to compare

@atinfinity atinfinity released this 03 Oct 20:43
9cb936e

New

  • Time and cost totals (#8, #19): each day in the calendar header shows its active time and cost. A new Summary pane breaks down active time per project per day, with cost and session counts for the displayed range. A session's cost is split across days by when its API requests ran.
  • Search match snippets (#20): when a search matches a prompt rather than the title, the list view and the calendar tooltip show the matching text, highlighted.
  • State explanations (#21): hover over a Session state check, the status badge or a status filter chip to see what it means.

Project

  • Security policy with private vulnerability reporting, issue forms and a pull request template.

Install

uv tool install git+https://github.com/atinfinity/cc-calendar@v0.2.0
cc-calendar

Upgrading from v0.1.0: uv tool install --force git+https://github.com/atinfinity/cc-calendar@v0.2.0

Full changelog: v0.1.0...v0.2.0

v0.1.0

Choose a tag to compare

@atinfinity atinfinity released this 03 Oct 19:39
1a1c5e1

First public release.

Features

  • Week and day calendar of Claude Code sessions, split into active periods, with an activity heat strip
  • Color by project, status, model or cost
  • Live status (Running / Waiting / Done / Interrupted) with the checks behind it
  • Detail pane: tokens, cost, context usage, requests with the commits that followed, files changed, pull requests, subagents and background tasks
  • Transcript viewer with Markdown rendering, subagent drill-down and per-transcript stats
  • Sortable, searchable list view
  • Live updates via server-sent events

Install

uv tool install git+https://github.com/atinfinity/cc-calendar@v0.1.0
cc-calendar

Everything runs locally: the server binds to 127.0.0.1, accepts only loopback Host headers, and reads your logs read-only. Costs are estimates — see the README.