New in 0.7Spend spare quota on your agents

Will your pace last until the reset?

Pace tells you whether your current Claude Code pace will hit your plan limit before it resets — and when.

For Claude Pro & MaxmacOS 14 or laterv0.7.4Not affiliated with Anthropic

Pace popover in the at-risk state: ease off to 68% of your current pace; the session is 71% used and hits its limit in about an hour at this rate, with week windows and usage by project below.

The pace bar

One bar, three answers.

Every window in Pace is drawn the same way, so the question “can I keep going at this rate?” takes one glance.

Used

How much of the window you've spent, straight from Claude Code.

Even pace

Where you'd be if you spread usage evenly across the window. Short of the tick means room to spare.

At reset

Where the window ends if you keep your current burn rate.

Time to limitWhen you'd hit 100% at this rate, shown only if that's before the reset.
Sustainable rateWhat you can spend per hour from now and land on exactly 100% at reset.

The Day Ring

Speed up or ease off.

For every window Pace computes one number. You can only go as fast as the tightest limit allows, so the arrow follows the window with the smallest factor.

factor = sustainable ÷ current

Ease off×0.68

Ease off to 68% of your current pace, or you hit the limit before the reset. That is exactly the at risk condition.

Session (5h)A continuous ring: the session is the tight one.

Week (7d)Seven segments, one per day: the week is.

One status scale

Calm until it shouldn't be.

Every window gets one of four states. The menu bar, the cards and the notifications all come from the same value, so they never disagree.

Pace headline card in the Comfortable state

Comfortable

Projected below 85% at reset. Keep going.

Pace headline card in the Watch state

Watch

Projected to end at 85% or more. Worth a glance.

Pace headline card in the At risk state

At risk

At this rate you hit 100% before the reset, and Pace says when.

Pace headline card in the Limited state

Limited

At the limit. Pace shows when you're back.

Dashboard

The whole picture, one keystroke away.

⌘D opens the dashboard: each window’s burn rate now, over the last hour, 5 hours, 24 hours and the window average, all against the sustainable rate, and usage over the window with the even-pace line and where this pace lands.

Pace dashboard in the at-risk state: ease off to 68% of your current pace; session burn rate by horizon against the sustainable rate, and the week windows. Usage over the session, with the projection at this pace crossing the limit before the reset.

Projection New in 0.7

Project from any stretch.

A burst, a lunch break and a heavy afternoon don’t average into one honest rate. Drag across the chart to pick the stretch that looks like what comes next, and compare four ways to read it. Try it below; in the app, pinch zooms either axis.

Drag across the chart to pick a stretch.

MethodRateAt resetBandLimit
Average––––
Linear trend––––
Robust trend––––
Recent-weighted––––
AverageFirst to last reading, idle time included.
Linear trendLeast squares through every reading, with a 95% band.
Robust trendTheil–Sen: the median slope of all pairs. Shrugs off one burst.
Recent-weightedLeans toward how you’re working at the end of the stretch.

Resets New in 0.7

Plans for the reset you know is coming.

When a reset is announced early, the right pace changes. Tell Pace and every forecast aims at it instead.

  • Planned resets. Add a date for all limits, the session or the week. Projection, time to limit, even pace and the arrow all aim at it, and each card says how much would go unused by then.
  • Early resets, accepted. A drop of 10 points or more is taken as a reset once a second reading agrees, and burn rates start fresh from there.
  • Banked resets. Keep count of the ones you’ve been given, and mark one redeemed when you use it.
Week cards: 41% used, 43% unused at the planned reset on Friday.
The Resets card: two banked resets, and a planned weekly reset on Friday at 10:58 pm.

Spend New in 0.7

Spare quota, put to work.

When Pace sees a session or a week ending with quota unused, it offers work that’s always worth more of: docs, reviews, tests, ideas. Pick tasks and projects, and Pace hands them to Claude Code or Codex agents in Herdr, now, at the next reset, or overnight.

One click per batch

Nothing starts on its own. The window shows what’s spare now and next session, and checks the batch against it.

Guardrails built in

Each job works on its own pace/* branch in a fresh worktree, never touches your changes, and never merges, pushes or deploys.

Follows through

Jobs survive a relaunch; Pace tracks each one to Done, flags any that need you, and can wait for the reset or a time you choose.

What you get

Quiet by default, detailed on demand.

Built for people who run Claude Code all day, often several agents at once.

Reads usage the way Claude Code does

Pace runs Claude Code's own /usage command locally ($0, no tokens spent) and listens to its status line for updates after every response.

Live pace, not stale numbers

Token counts in your local Claude Code transcripts calibrate the burn rate, so it reacts within ~30 s of a burst instead of waiting for the next reading.

Every window, one verdict

Session (5h), Week (7d) and per-model week windows, each with used %, an even-pace marker, projected % at reset, time to limit and sustainable rate.

Where it's going

A dashboard (⌘D) with burn rate across horizons, usage over the window you can zoom and project from, activity by project, and Claude Code's own findings, like “63% of usage was at >150k context”.

Warns before, not after

A notification when you're on track to hit a limit, while there's still time to slow down. Another when a limit is reached, and when a tight window resets.

Out of the way

⌃⌥P opens Pace from anywhere; from there ⌘D is the dashboard and ⌘E is Spend. Launch at login. A monochrome menu bar that only takes colour when something needs your attention.

Private by construction

No credentials.
Nothing leaves your Mac.

Pace reads your limits through Claude Code itself: its local /usage command and its status line. Claude Code makes its own request, as it would anyway. Pace only reads the result.

$ claude -p "/usage" --safe-mode \
  --no-session-persistence --output-format json
# num_turns: 0 · total_cost_usd: 0
  • No passwords, cookies, API keys or OAuth tokens touched.
  • Pace never calls an Anthropic endpoint itself.
  • No analytics, no update pings. Nothing is sent anywhere.
  • Status line relay keeps your existing status line exactly as it was, and Disconnect restores it.
  • Spend only talks to Herdr on your Mac, and nothing starts without your click.

What’s new

Changelog.

Pace moves quickly. Here’s what changed, newest first.

v0.7.4Latest
  • Model week in the menu bar. A ring and a percentage for the model-scoped weekly limit, such as Fable, alongside the 5-hour and weekly ones.
  • Ring shapes. Each ring can be a circle or a heptagon, continuous or in seven segments. The model week defaults to a segmented heptagon.
  • Status for agents. Pace writes its forecast to status.json, and pace-bridge status --json prints it, so Claude Code, Codex or a script can check what's left before starting big work.
v0.7.3
  • Plans without a 5-hour limit. When Claude reports only the weekly limit, as on Ultra, Pace hides the session card and its menu bar ring, and Spend plans against the week alone.
v0.7.2
  • Sustainable rate near the reset. In the last day before a weekly reset, or the last hour of a session, Pace shows what's left and how long you have, instead of a rate that runs away.
v0.7.1
  • Spend scheduling fixes. Waiting for a reset or a time now always waits, the budget bar matches when a batch starts, and a failed start no longer leaves a pane behind.
v0.7
  • Spend. When quota would go unused, hand safe, repeatable tasks to agents in Herdr, one click per batch.
  • Project from any stretch. Drag across the usage chart and compare average, linear, robust and recent-weighted fits. Pinch to zoom either axis.
  • Planned and banked resets. Forecasts aim at an announced reset; early resets are accepted and rates restart after them.
  • Menu bar items. Rings, percentages, countdowns, headroom and sessions left this week, each on or off, in your order.
v0.6
  • The Day Ring. Used % as the arc, speed up or ease off as the arrow.
  • Dashboard (⌘D) with the burn rate over five horizons against the sustainable rate.
v0.5
  • Pace, rebuilt. Reads Claude Code’s own /usage and status line. No cookies, no tokens, nothing leaves your Mac.
  • A live burn rate calibrated from local transcripts.

FAQ

Questions, answered.

Still curious? Read how Pace works, all the way down to the maths.

Does Pace need my Claude password, cookie or API key?

No. Pace reads your limits through Claude Code itself: its local /usage command and its status line. It never touches a credential and never calls an Anthropic endpoint.

Does checking usage cost anything?

No. /usage is a local command: no model turn, no tokens, $0. The status line relay only copies what Claude Code already reports after each response.

Which plans does it work with?

Claude Pro and Max, with Claude Code installed and signed in. Pace follows the 5-hour session, the week and the per-model week windows your plan has.

What does the arrow in the menu bar mean?

It's your pace factor: sustainable rate ÷ current rate. Level means you're on pace, tilted up means there's room to go faster, tilted down means ease off before the limit. It follows whichever limit is tightest.

What if a limit resets early, or I have some banked?

Pace accepts a confirmed drop of 10 points or more as an early reset and restarts its rates from there. Add an announced reset on the dashboard and every forecast aims at it; keep your banked count there too.

Does Spend run things on its own?

No. Spend suggests work for quota that would otherwise go unused, and every batch starts with your click. Jobs run in Herdr on your Mac, each on its own pace/* branch, and never merge, push or deploy.

How do I remove it?

Settings → Disconnect puts your original status line back exactly as it was. Then quit Pace and move it to the Bin; its data lives in ~/Library/Application Support/Pace.

Pace app icon

Keep your pace.

Pace lives in your menu bar and stays quiet until there's something worth knowing.

  • macOS 14 or later
  • Claude Code installed and logged in
  • Claude Pro or Max plan