What you need
- Multimeter for macOS 13 or later, $19.99 once.
- Claude Code, signed in with a Claude Pro or Max plan. Claude Code only receives the 5-hour limit on those plans; the context number works with any sign-in.
jqfor picking numbers out of JSON. It comes with macOS 15 and later; on macOS 13 or 14 runbrew install jq.
Set it up
- Save this as
~/.claude/multimeter-statusline.sh. It sends the two numbers to Multimeter only when they change, and prints the line Claude Code shows at the bottom of the terminal:multimeter-statusline.sh#!/bin/zsh # Claude Code status line that also sends your usage to Multimeter. input=$(cat) five=$(jq -r '.rate_limits.five_hour.used_percentage // empty' <<<"$input") ctx=$(jq -r '.context_window.used_percentage // empty' <<<"$input") # Only send when a number changed, so Multimeter isn't pinged on every redraw. state="${TMPDIR:-/tmp}/multimeter-claude-last" if [[ "$five|$ctx" != "$(cat "$state" 2>/dev/null)" ]]; then print -r -- "$five|$ctx" > "$state" [[ -n $five ]] && open -g "multimeter://set?key=claude-limit&value=$five&min=0&max=100&unit=%25&label=CLAUDE" [[ -n $ctx ]] && open -g "multimeter://set?key=claude-context&value=$ctx&min=0&max=100&unit=%25&label=CONTEXT" fi # What Claude Code shows at the bottom of the terminal. print -r -- "$(jq -r '.model.display_name' <<<"$input") · ${ctx:-0}% context${five:+ · $five% of 5-hour limit}" - Make it runnable:Terminal (once)
chmod +x ~/.claude/multimeter-statusline.sh - Point Claude Code’s status line at it in
~/.claude/settings.json(add thestatusLinepart to what’s already there). Claude Code picks it up as soon as you save:settings.json{ "statusLine": { "type": "command", "command": "~/.claude/multimeter-statusline.sh" } } - In Multimeter, add a meter with the Sent Value source and the key
claude-limit. Add a second one with the keyclaude-contextif you want the context window too. - Set alerts to High values: warning at 75, critical at 90, and turn on Notify me when it goes critical. The script sends the range (0 to 100), the label and the % unit itself.
Multimeter settings
In Customize This Meter… (from the meter’s menu):
| Setting | Value |
|---|---|
| Source | Sent Value |
| Key | claude-limit (and claude-context for a second meter) |
| Range | 0 to 100, sent by the script |
| Alerts | High values: warning 75, critical 90, notify on critical |
| Label | CLAUDE and CONTEXT, sent by the script |
| Face | Ring, Level Bar or Label & Value |
Tested: Run on November 18, 2026 with the sample input from Claude Code’s status line documentation: it printed Opus · 8% context · 23.5% of 5-hour limit, sent multimeter://set?key=claude-limit&value=23.5&min=0&max=100&unit=%25&label=CLAUDE and the context link once, and sent nothing on a repeat of the same numbers.
More on this source, including every format it reads, in the Sent Value guide.
Limits
- Claude Code runs the status line when something happens in a session (a new message, a model change), not on a timer. The meters show the last numbers Claude Code saw, which is what the limit is until your next request.
- The 5-hour number appears after Claude Code’s first response in a session. Context belongs to one session; with several open, the last one to update wins.
- The status line runs on your Mac and doesn’t use any tokens.
Variations
Your weekly limit
Use .rate_limits.seven_day.used_percentage and a key like claude-week.
Session cost
Send .cost.total_cost_usd with unit=%24 to a key like claude-cost. Claude Code calls it an estimate at list price; it resets when /clear starts a new session.
When the limit resets
Add &formatted= with the time from .rate_limits.five_hour.resets_at (date -r <seconds> +%-l:%M%p), URL-encoded, so the meter’s menu shows it.
Troubleshooting
| Symptom | Cause | Fix |
|---|---|---|
| Claude Code’s status line is blank | The script isn’t runnable, or jq is missing. | Run chmod +x ~/.claude/multimeter-statusline.sh, then which jq. Test it with echo '{"context_window":{"used_percentage":8}}' | ~/.claude/multimeter-statusline.sh. |
| The CONTEXT meter updates, CLAUDE never does | Your sign-in doesn’t include the 5-hour limit (it comes with Pro and Max), or Claude Code hasn’t answered yet this session. | Send a message, then look again. With an API key there is no 5-hour limit to show; use the session cost variation instead. |
| The meter says to give it a key | The meter’s key doesn’t match the script. | In Customize, set the key to claude-limit exactly (case doesn’t matter). |
Questions
Does it work with the Mac App Store version of Multimeter?
Yes. Sent Value meters work in every version; nothing here needs the Script source.
Does it slow Claude Code down?
No. The script reads two numbers, and it only opens a multimeter:// link when one of them changed. Claude Code waits 300 ms between updates anyway.
Can it show Codex or other agents?
Any tool that can run a command can send a number the same way: open -g "multimeter://set?key=NAME&value=NUMBER". See the URL scheme guide.