Product1 publisher2 min readPublished
Claude Statuspane makes agent spend visible to one developer at a time
Anji Xu's open-source Claude Statuspane puts context use, five-hour and seven-day rate limits and session cost in a card above the Claude Code prompt. The readout lives on that one developer's screen, so whoever answers for a team's total agent spend still needs records kept somewhere central.
The Product Desk · Product desk
Drafted by a language model from the sources cited here and checked against its claim ledger before publication. How we use AISend a correction
What happened
- Statuspane is built on Claude Code's new mod system, which is still in early access, and its README warns that the API may change between Claude Code releases.
- With the GitHub CLI signed in, the card shows the latest GitHub Actions run for the current branch, checking every minute and every 10 seconds while a run is active.
- A progress API lets any script drop a small JSON file with a label, percentage, time-to-live and state, and the card shows the 20 most recent, refreshed every second.
- The progress folder accepts only JSON files up to 64 KB and strips control characters, bidirectional marks and zero-width characters from text fields.
- It needs Claude Code 2.1.287 or later and a terminal at least 70 columns wide, and it does not run in the Claude Code desktop app.
Compiled by The Product DeskSomething wrong?How this is made
Why it matters
- capability Developers can watch the context window fill and trigger /compact from the card before a session hits its limit, instead of learning about it when the work stops.
- constraint A team that standardizes on the card now signs up to repair it after Claude Code updates, because the mod API underneath may change between releases.
- exposure Any script on the machine that writes to the progress folder can put text into the agent's terminal, a route devops.com names as a possible path for injected content.
A developer starts a long task in Claude Code and turns back to other work. According to devops.com, the session draws down a context window, a five-hour rate limit, a weekly cap and a budget at the same time, and most of the time nobody notices until one of them runs out [1].
Claude Code already had one answer to this. Its statusLine setting runs a shell script and prints a single line of text [5]. Statuspane replaces the line with a card of gauges [6]. The context bar turns a warning color at 60% and an error color at 85% [6]. On a 1 million token window, those thresholds land at 600,000 and 850,000 tokens [1].
The CI feature deals with a smaller, daily chore. An agent pushes a change, and the developer opens a browser tab to see whether the pipeline passed [17]. Statuspane can instead follow runs started by git push or gh pr merge and keep them on screen, marked running, failed or deployed, for 10 minutes after they finish [10]. Those lookups use the developer's own GitHub CLI credentials, with no third-party service in between [19].
devops.com argues that as agents take on longer, more autonomous work, the people running them need the telemetry they already expect from build systems and production services [18]. Statuspane delivers a live readout for one person at one terminal. The same article calls the project useful at the individual level and says DevOps teams ultimately need centralized, auditable telemetry covering agent spend, limits and pipeline outcomes [16].
There is little evidence of use to judge it by. It is published on GitHub under an MIT license [2], and devops.com describes it as brand new with little adoption, to be treated as an experiment [15].
For whoever has to roll it out, a 2x2 sorts the decision. One axis is who is asking: the developer at the prompt, or the person who answers for the agent bill. The other is when the answer is needed: during the session, or later, as a record someone else can check. Statuspane fills one square, the developer during the session, with model, context, limits with reset countdowns, branch and running cost [3]. The other three squares need data that leaves the developer's machine.
If a team's open questions are mostly about whether a session will reach its five-hour cap before the task ends, a few developers trying the card costs little. If the questions are about what agents cost the whole team last month, they need the central record devops.com describes. Everything in Statuspane runs locally [14].
What to watch
- Whether Claude Code's mod system leaves early access, or a release changes the API and breaks the Statuspane card.
- Whether the project picks up adoption beyond its current small base now that it is public on GitHub.
- Whether a tool appears that gathers per-session cost and rate-limit data from many developers into one auditable record.