Install

Paste this into Claude Code. It installs the script, wires Claude Code up to it, and checks the result.

Install the statusline from https://github.com/alp82/claude-statusline for me.
Run: curl -fsSL https://alp82.github.io/claude-statusline/install.sh | bash
Then check that bash, jq and curl are present, confirm ~/.claude/settings.json
points statusLine at ~/.claude/statusline.sh, and tell me what to do next.

Claude reads the installer before it runs it, tells you what changed, and fixes anything missing. Re-paste it any time to upgrade.

curl -fsSL https://alp82.github.io/claude-statusline/install.sh | bash

curl -fsSL https://raw.githubusercontent.com/alp82/claude-statusline/main/statusline.sh \
  -o ~/.claude/statusline.sh
chmod +x ~/.claude/statusline.sh

{
  "statusLine": {
    "type": "command",
    "command": "~/.claude/statusline.sh"
  }
}

Uninstall

The same prompt in reverse:

Uninstall the statusline from https://github.com/alp82/claude-statusline for me.
Run: curl -fsSL https://alp82.github.io/claude-statusline/install.sh | bash -s -- --uninstall
Then confirm ~/.claude/statusline.sh is gone and ~/.claude/settings.json no longer
has a statusLine entry, and show me which .bak files it left behind.

curl -fsSL https://alp82.github.io/claude-statusline/install.sh | bash -s -- --uninstall

What it shows

Left to right:

• dir ⎇ branch — the current directory's name, and the git branch you are on. In a linked git worktree the glyph becomes an amber ⎇+, so a worktree never looks like the main checkout:

  copy

  claude-statusline ⎇ main          ← the main checkout
  claude-statusline-fix ⎇+ fix/bar  ← a linked worktree
  

• ★ Model — the active model's display name

• Ctx — how full the context window is, 0–100%, and the token count in thousands

• 5h / 7d — your 5-hour and 7-day rate-limit windows: how much you have used, how much of the window has gone by, and ↻ the time until it resets. The distance between the two halves is the number to read

• Fable — the same, for Fable's own weekly quota. It resets with the 7-day window, so it shows no ↻ of its own

How to read it

Usage against time

The top half of each cell is how much of the window you have used. The bottom half is how much of the window has gone by. The distance between the two is the number to read.

If the top reaches further right than the bottom, you are spending faster than the clock and you will run out before the window resets. Drop an effort level and the spend rate falls with it, which is what the loop above shows: high effort until the gap opens, then low, and the clock catches back up. If the bottom reaches further right, you are leaving quota you will not get back, so you can afford to think harder.

Colour follows usage: green under 50%, yellow 50–80%, red above 80%.

Context window

Turns yellow at 25% and red at 50% — sooner than the limit bars, because a full context window stops you working right away. The bar fills in eighths of a character, so it moves before the number does.

When a window resets

At the end of a 5-hour window both halves drop back to zero, the colour goes back to green, and the countdown starts again at 5h0m.

The Fable window

Fable has its own weekly quota. Spend it early and nothing gives it back before the week is over, so the blue half is the useful one: it tells you how long the wait is. The window resets with the 7-day one, which is why it shows no ↻.

Claude Code does not send this one. The script reads it from ~/.claude.json and only asks the API for a fresh value in the background, at most every ten minutes — so it stays out of the TUI's way.

On macOS that refresh needs the OAuth token from the Keychain, because Claude Code stores it there instead of in ~/.claude/.credentials.json. The first read can open a Keychain dialog. Click Always Allow once and it stops asking. To skip the Keychain read altogether, set CLAUDE_STATUSLINE_NO_KEYCHAIN=1 — the Fable bar then follows the CLI's own cache only.

Requirements

• bash
• jq — parses the statusline JSON from stdin
• curl — only for refreshing the Fable weekly quota

How it works

Claude Code pipes a JSON blob to the script on stdin (docs). Everything but the Fable window comes straight from that payload. The Fable weekly quota isn't in it, so the script reads the CLI's own cached copy from ~/.claude.json and only hits /api/oauth/usage itself — in the background, throttled — when that copy is stale.

License

MIT