Get more out of every Claude Code session.

/plugin marketplace add meyusufdemirci/claude-code-session-tracker

/plugin install session-tracker@claude-code-session-tracker

$claude-code-session-tracker auto-continue on

$claude-code-session-tracker auto-continue off

> Add the export dialog

  ⎿  Usage limit reached · resets 3:00pm

  ⏸  Waiting for the reset · continues at 3:01pm

  ⏵  The usage limit that stopped this session has reset;
     continue the task you were working on

  ●  Picking up the export dialog where I left off…

1. 1

   Any terminal

   Claude Code wakes the session itself, so it works the same in VS Code, Ghostty, tmux, iTerm or Terminal.

2. 2

   Nothing else has to run

   The wait lives inside the session. No tab, menu bar or tracker needed — just leave the session open.

3. 3

   Checked before it wakes

   At the reset it makes sure the switch is still on, that you have not carried on yourself, and that the limit no longer reads as full.

4. 4

   Weekly limits too

   A session can wait up to eight days. Turning it on while sessions are already waiting still covers them.

1. 1

   The same percentage /usage shows

   Anthropic's own reading of each limit, the same number /usage shows.

2. 2

   Used is what you were billed for

   Input, output and new cache tokens, across every project and subagent. Cache reads are shown apart.

3. 3

   At this pace, it runs out at…

   Based on your recent pace, the card says when the window runs out — or where it will stand at reset.

4. 4

   Two ticks on the bar

   Red is time elapsed, blue is where you'll land. Fill past the red tick means you're spending too fast, and the bar turns red.

Offline or without a fresh reading, the bar falls back to your heaviest past window — and says so.

1. 1

   Off until you turn it on

   Nothing asks for permission until you flip a switch.

2. 2

   Once, then quiet

   One per interval: an hour for the session, four for the week.

3. 3

   Offered once

   Suggested once when a limit first appears.

A week with no reset from Claude stays silent.

1. 1

   Spend per day, week or month

   A bar per day, quiet days included — or folded into weeks or months for a long range. A mark under a bar is a day Claude refused a turn.

2. 2

   Hour of day, a month folded onto one week

   A month folded onto one week — when your window actually opens.

3. 3

   Your year, day by day

   A calendar year as a grid, shaded against your own busiest days. Step back a year with ‹ ›.

4. 4

   Every project and model, ranked by what it billed

   Ranked by billed tokens, with the full path under each project. Pick one to narrow everything to it.

5. 5

   Export a report

   Any range as a PDF or an .xlsx — daily, weekly or monthly, one project or all. Written in the browser, sent nowhere.

6. 6

   Share your year

   The year grid as an image, with a post for X or LinkedIn ready to paste it into. Nothing is posted for you.

Reuses the limit cards' read, so it costs almost nothing. Nothing polls — click Refresh.Bookmarkable: range, grouping, year and project live in the URL. Ranges reach back a year and a week.

• New

  Picks up after the limit resets

  A session that stopped on a limit continues by itself once it resets. Off until you turn it on.

• Both limits, at the top

  Your five-hour and weekly usage, when they reset, and when they run out.

• A heads-up before you hit one

  A desktop notification when a window is on course to run out. Off until you turn it on.

• Where the tokens went

  Spend per day, per half hour, per project, and a whole year as a grid. Pick a project to narrow the page.

• Reports and a year to share

  Export any range as a PDF or .xlsx. Share your year as an image for X or LinkedIn.

• What the spend was made of

  Oversized sessions, standing context, model mix — only when something is unusual.

• Active sessions, verified twice

  Checked against the OS, so working means working.

• Recent sessions, every project

  Title, prompts, model and branch — find the one worth resuming.

• A panel per session

  Counts, tokens, working time, subagents, and a copyable resume command.

• The standing cost, itemised

  What fills the window up front — CLAUDE.md, skills, tools, MCP — priced block by block.

• Open at login

  autostart on adds it to your login items. The page is waiting when you sit down.

• A menu bar switch and a widget

  On macOS: turn the tracker on and off from the menu bar, and see both limits as rings in a widget.

• A Claude Code plugin

  /session-tracker:status prints your limits in the session you are in. /session-tracker:open opens the page.

• Limits in your terminal

  status prints both limits, today's spend and the running sessions. open brings up the page.

• Token usage you can sort by

  Coloured by context share, so you see what's about to compact.

• Scriptable output

  --json prints the page's payload. The HTTP API is open too.

• Fully keyboard driven

  Filter, move, open and close — all from the keyboard.

• No dependencies, no install scripts

  Nothing to install or configure. Works the same on npm, pnpm, yarn and bun.

• Local by construction

  Loopback only, never writes to your Claude directory. Two outbound calls, both off with --offline.

$npx claude-code-session-tracker@latest menubar install --with-tracker

$claude-code-session-tracker menubar uninstall

1. 1

   A switch in the menu bar

   Turns the tracker on and off. The panel under it shows both limits, when they reset, and the sessions that are running.

2. 2

   A widget for the desktop

   The same two limits as rings, on the desktop or in Notification Center. Click it to open the page.

3. 3

   One command, from nothing

   --with-tracker installs the tracker first — with Homebrew, or npm where there is none. Leave it off when you already have it.

4. 4

   Checked before it is unpacked

   Downloaded from that version's GitHub release and no other. Anything that does not match the package's SHA-256 is refused.

/plugin marketplace add meyusufdemirci/claude-code-session-tracker

/plugin install session-tracker@claude-code-session-tracker

  Claude Code Session Tracker 0.11.0

  5-hour limit  12% used, resets in 3h
  Weekly limit  12% used, resets in 4d 9h
  Today         3.9M tokens in 637 turns

  Running       2 sessions
    busy     my-app      Add the export dialog
    waiting  my-api      Fix the flaky login test (input needed)

  Dashboard     http://127.0.0.1:3099

1. 1

   Ask, and Claude checks

   Ask how much of the weekly limit is left and Claude runs /session-tracker:status by itself. /session-tracker:open only runs when you type it.

2. 2

   Status starts nothing

   A running tracker is asked. When none is, the same numbers are read straight from your Claude directory.

3. 3

   No code of its own

   Each command, and the auto continue hook, runs the CLI — the copy on your PATH, otherwise npx.

4. 4

   The same two in any terminal

   status and open are ordinary commands, so they work outside Claude Code too.

• Never writes to your Claude directory

  It only reads what Claude Code already wrote.

• Loopback only

  Binds to 127.0.0.1 and rejects other hosts, so no website can reach it.

• Two outbound calls, and --offline

  Claude Code's usage endpoint, and the npm registry for the newest version number. No telemetry, no analytics. Your package manager runs only when you click Update. The macOS app is downloaded only when you ask for it.

• One thing that acts, and only when asked

  Auto continue, once you turn it on, wakes a session that stopped on a limit. Its switch and the waiting list live in the tracker's own folder.

• No dependencies, no install scripts

  Nothing third-party runs on your machine.