The problem
Claude's subscription plans cap use in two rolling windows: a five-hour session window and a weekly one, shared by claude.ai, Claude Code and the Claude desktop app (see Anthropic's help centre for your plan's details). You can run out of either first. Checking means opening the usage page in Claude's settings or typing /usage in a session, so most people find out they're close when a long task stops halfway.
How Pairbar solves it
- Look at the ringThe ring in the sidebar header shows how much of your plan's tightest limit is used right now: whichever of the 5-hour and weekly windows is fuller. Orange from 50%, red from 80%.
- Hover or click it for the limits cardThe card shows the current session (5-hour) window, the weekly window for all models, and the weekly windows for specific models, each with its reset time.
- Install live status for ClaudeSettings → Integrations → Live status for Claude (hooks) → Install… also runs Claude Code's status line through Pairbar's small helper, which keeps the 5-hour and weekly percentages Claude Code hands it (on Pro and Max plans, after a session's first answer). Your own status line, if you have one, looks exactly the same. See Where the numbers come from.
- Let the context card warn youWhen a limit is low, the focused chat's context line shows a gauge, and its card's Now row says so ("Claude 12% left") once it's under 20%.
- Keep scheduled work from eating your planGive a workflow Skip under N% (20% by default) and its scheduled runs are skipped when less than that is left. Run now skips the limit check; required startup answers must still be supplied.
Where the numbers come from, in order
| Source | When it's used | Cost |
|---|---|---|
| Claude Code's status line | after you install live status for Claude; it runs in Claude Code in a terminal | nothing: Claude Code hands over the numbers |
| The Claude app's own record of the 5-hour window | when you use the Claude desktop app, whose Code tab may not run the status line; weekly windows from an earlier reading stay until they reset | nothing: it's on your Mac |
claude -p /usage | only as a last resort, when neither has anything from the last 6 hours; at most every 15 minutes | no chat turn, costs nothing |
A reading counts as current for 15 minutes (a minute when you open the card). The status line doesn't carry the weekly limits for specific models, so the card keeps those from the last /usage reading until they reset. Pairbar never edits Claude's settings to read them; see Claude's settings stay yours.
Also on the card: this Mac
Under the plan limits, On this Mac shows the memory and CPU the Claude app and everything it started are using, like Activity Monitor, measured only while the card is open. See On this Mac.
If you use only Codex
The header shows a Codex ring instead, from the newest rate-limit report in Codex's local session files, and the card lists each of Codex's windows with reset times and your plan. Use both apps and you get two rings side by side, and Pairbar can suggest which app to start a chat in from the headroom left; see monitoring Claude and Codex limits together, and for the other cross-app extras, switching between Claude Code and Codex.
Without Pairbar
Without Pairbar:
- Claude's usage page (Settings → Usage in the Claude app or on claude.ai) shows the current session and weekly usage.
/usageinside a Claude Code session prints the same numbers.- A custom status line in Claude Code can print usage in the terminal, while that terminal is open.
Frequently asked questions
- Does checking my Claude Code limit use up my plan?
- No. Normally Pairbar reads Claude Code's status line or the Claude app's own record and starts no
claudeat all. The last-resortclaude -p /usageuses no chat turn and costs nothing. - Why doesn't the ring match the 5-hour number?
- The ring shows the tightest limit: whichever of the 5-hour and weekly windows is fuller. The card shows each window separately.
- Do I need the claude command-line tool?
- Not for the 5-hour window when you use the Claude app: Pairbar reads the app's own record. The status line and the last-resort
/usagecome from Claude Code, and without any reading the card says so and links to install it. - I only use Codex. Does this work for me?
- Yes, with Codex's numbers: the ring reads Codex's own local session files. Pairbar works with Claude Code alone, Codex alone, or both.
Related
- DocsLimitsUsage rings, the limits card, how limits are read, memory and CPU on this Mac
- Glossary5-hour usage windowClaude's session limit: a five-hour period after which your session allowance resets, shared by claude.ai, Claude Code and Claude Desktop.
- GlossaryPlan usage limitsThe caps a Claude or ChatGPT subscription puts on Claude Code and Codex use, measured over a five-hour window and a weekly window.
- Use caseKeep an eye on your Claude and Codex plan limits while you workUsage rings for both plans, a limits card with each window's reset time, and limit-aware chat suggestions and workflows.
- GuideSet up live status hooks for Claude and CodexTurn on instant status from Claude Code and Codex hooks: what Install writes, what is sent, how to check events arrive, repair and uninstall.
Try Pairbar free for 7 days
One sidebar for the Claude and Codex desktop apps. Everything on for 7 days, no card needed; then $49/year ($39 first year with LAUNCH), $9/month or $129 lifetime (first 200 buyers). macOS 26 or later, Apple silicon.