· ↑ 37.0k ↓ 1.4k cache 7.0k · session ↑ 111.0k ↓ 4.2kEach turn's tokens and the session's running total, in color at the end of the hint line under the prompt.
What this mod can do
- Reviewed at commit a2babd9
1 thing it can do
- Runs on a timer
Good to know (3)
- Change the 50% and 75% thresholds with the warnAt and dangerAt settings in /config
- Before the first response, and after a compaction or rewind, it shows an estimate marked ~
- The footer is left as it is, and anything else drawn above the prompt stays above the meter
Preview
Terminal
context 22% [-]Claude Desktop
What it does
In the author's words
The session's context window fill, right above the prompt: gray while there is room, yellow when it is time to /compact, red when a new session is better.
- What you see
- A context N% readout at the right end above the prompt
- Works in
- Terminal and Claude Desktop
- Slash commands
- None
- Uses your tokens
- No
- Changes files
- Nothing
- Network access
- None
- Reviewed commit
- a2babd9
- Preview recorded with
- Claude Code 2.1.309
How it works
- Takes a first reading from $.session.usage() when the session starts
- Updates from context.percent after each response that moves it
- Rereads usage every 2 seconds, since a resume or rewind raises no event
- Draws context N% above the prompt: gray, yellow from 50%, red from 75%
Common questions
How do I see context window usage in Claude Code?
The /context command counts it on demand. This mod keeps the figure on screen instead: context N% sits at the right end of the band above the prompt and updates after each response that changes it.
When should I run /compact in Claude Code?
This mod turns yellow from 50% full, which its README calls a good moment for /compact, and red from 75%, when it suggests compacting now or starting a new session. Both thresholds are the warnAt and dangerAt settings in /config.
Why does the meter show a ~ before the number?
Before the first response of a fresh or resumed session, and right after a compaction or a rewind, Claude Code has no reading yet. The meter counts the window once, as /context does, and marks that estimate with ~ until the next response brings the real figure.
Badge for your README
Own this listing? Add it to your README. The badge shows the install count as it grows.
[](https://staging.statuslin.es/mods/context-meter?utm_source=readme-badge)
Or show the preview card:
[](https://staging.statuslin.es/mods/context-meter?utm_source=readme-badge)
More like this
Your context window as a stacked bar above the prompt, a color per category, with token counts and the compaction point. /context-bar shows or hides it.
⎿ cache-tax: keepwarm on for 6h00m, a ping 50m after each idle stretch keeps the cache read, not
re-written
⎿ cache-tax: claude-opus-5-5
state warm, 1h00m left
context 44,000 tokens
cold cost $0.35 to re-write it (warm turn $0.01)
keepwarm on, 6h00m left · ping in 50m
break-even up to 40 pings at the read rate cost one cold write, about 33h20m of idle at one
ping per 50m
guard ask first (/cache-tax guard warn to only show the price)
session 0 cold writes paid, $0.00
[>] cache-tax · warm · keepwarm 6h00m left · ping in 50m [-]A Claude Code mod that keeps the one-hour prompt cache warm during breaks and asks before a cold send, showing its estimated rewrite cost. Warming uses model requests and costs tokens. Requires Claude Code 2.1.287+.
⎿ context-inspector: Context Inspector pane opened (shown in the terminal and the desktop app).
╭────────────────────────────────────────────────────────────────────────────────────────────────✕─╮
│ Context Inspector — main context │
│ Live ≈3.0k tokens in 12 items · 1 turn(s) · 0 compaction(s) · waste ≈0 │
│ ≈ = estimate (chars/4 × k=1.00, 0 calibration segment(s)); figures without ≈ are measured or en… │
│ │
│ Top occupants (live, by category) │
│ attachment:skill_listing ≈1.5k 50% █████░░░░░ 1 item(s) │
│ attachment:agent_listing_de… ≈685 23% ██░░░░░░░░ 1 item(s) │
│ attachment:environment ≈180 6% █░░░░░░░░░ 1 item(s) │
╰──────────────────────────────────────────────────────────────────────────────────────────────────╯
⚠ context-inspector: ctx 22% · waste≈0Context waste analyzer for Claude Code: what fills the window, re-reads, near-duplicate outputs, what compaction kept, advice
Opus 4.8 ▓▓░░░░░░░░ 22%Model plus a 10-block context-usage bar. Example statusline inspired by the Claude Code docs (code.claude.com/docs/en/statusline).
5h ▓░░░░ 🟢
A minimal 5-slot block bar showing context-window usage with a green/yellow/red status dot. Source: github.com/gwiener/claude-burn-bars
Opus 4.8 high ✦ │ ctx 22% │ app (main) │ PR #1287 ● │ $0.41 · 10m +128 -34
Session ● ● ● ● ● ● ● ● ○ ○ ○ 74% left Resets in 2h 6m
Weekly ● ● ● ● ● ● ● ● ● ● ○ 93% left Resets in 2d 0h
Feature-rich bash status line with model, context bar, session cost (read live from Claude Code, so it stays correct on any model), rate-limit bars, and live tool/agent activity that adapts to terminal width. Source: github.com/JungHoonGhae/claude-statusline
✧ ███████████▋ 73% 🗝 Ultima Weapon ✦ app ∙ main
♥ ████████████████████████ 100% 「SAVE POINT」 ✶ Limit Form ◉ 41
Claude Code plan-usage HP bar that reads the Claude auth token to show remaining usage.