Claude Code statusline
Show your model, git branch, context window and Claude Code limits under the prompt.
The Clauder statusline is a bash script that Claude Code runs to draw the line under its prompt. It shows the model, git branch, context window, and your 5-hour and weekly limits. Install it with one curl command, then point Claude Code at it.
Below: installing it, turning it on, what each element means, and the files that control it.
How do I install the Claude Code statusline?
Run the installer in a terminal:
curl -fsSL https://clauder.fyi/api/scripts/install | bashIn VS Code or Cursor, Clauder: Install Shell Integration runs the same command in a new terminal and adds your license key to the URL when one is set. The installer writes these files:
~/.claude/statusline-command.sh: the statusline itself~/.claude/statusline-config.json: which elements show, and in what order~/.claude/clauder.conf: cache time, sound settings, and your license key if you have one~/.claude/scripts/: helper scripts for fetching usage, sounds and hooks
It also adds Claude Code hooks to ~/.claude/settings.json with jq or python3: a tool-use tracker, a prompt tracker, a terminal tab namer, and a completion sound when sounds are on. The trackers write to a local file; the data and privacy page explains what of it is ever sent.
How do I turn on the statusline in Claude Code?
Add a statusLine entry to ~/.claude/settings.json. The installer prints this block when it finishes:
{
"statusLine": {
"type": "command",
"command": "~/.claude/statusline-command.sh",
"padding": 0
}
}Or run Clauder: Toggle Progress Display in the editor. It writes the entry for you, and running it again moves the entry aside to switch the statusline off.
What does the statusline show?
Elements appear in two groups: context (about the current session) and metrics (about your limits). Claude Code passes the model and context window data to the script on each render.
| Element id | Shows | Default |
|---|---|---|
model | Model display name from Claude Code | On |
gitBranch | Current git branch, with * when the working tree has changes | On |
contextWindow | Percentage of the context window in use | On |
fiveHourLimit | 5-hour usage percentage, a progress bar, and time until reset | On |
weeklyLimit | Weekly usage percentage, a progress bar, and the reset day | On |
prediction | Predicted time left before the 5-hour limit; needs a license key | Off |
Percentages change color at 40%, 60%, 80% and 90%, from tan to dark red. When a prediction comes from your trained survival model, it shows a lightning icon and the time by which you have a 70% chance of hitting the limit, for example (70%:~45m). How predictions work explains the model.
What does the cloud icon in the statusline mean?
☁✕ means the usage numbers could not be refreshed and are older than the cache time, usually because Anthropic rate-limited the usage endpoint. The next successful fetch clears it. In ASCII mode it reads (stale).
How do I configure the statusline?
Edit ~/.claude/statusline-config.json. Each element has an id, enabled, iconId, order and group. The top level sets Unicode or ASCII, progress bars, and how many metrics the carousel shows at once. An excerpt:
{
"elements": [
{ "id": "model", "enabled": true, "iconId": "diamond", "order": 0, "group": "context" },
{ "id": "fiveHourLimit", "enabled": true, "iconId": "percent", "order": 0, "group": "metrics" },
{ "id": "prediction", "enabled": false, "iconId": "tilde", "order": 2, "group": "metrics" }
],
"useUnicode": true,
"showProgressBar": true,
"carousel": { "enabled": true, "visibleCount": 1 }
}- ASCII mode: set
CLAUDER_ASCII=1. The script also falls back to ASCII when your locale is not UTF-8. - Cache time: the script reuses Anthropic usage data for 30 seconds by default before fetching again.
- Dashboard layout (Pro): arrange elements and icons at clauder.fyi/dashboard/extension, then rerun the installer with your license key. Without Pro, the installer writes the default layout.
Does the statusline work on Linux and Windows?
The script needs bash and jq. It reads usage from ~/.claude/usage-cache.json first. When that cache is old, its own fetch reads the Claude Code token from the macOS Keychain, so on Linux and Windows it relies on the Clauder editor extension to keep that cache fresh.
The editor extension itself reads the token on macOS, Windows and Linux.
How does the statusline stay up to date?
Every 4 hours the script asks clauder.fyi for the latest script version. When it differs from the installed one, it downloads the new scripts to temporary files and swaps them in, so a failed download never leaves a half-written script.