claude-statusline

A custom two-line truecolor statusline for Claude Code, plus one-command installers for Linux, macOS, and Windows.

What it shows

Line 1: model + effort · thinking mode · output style · context-usage bar · session cost · code velocity (+added/-removed) · 5-hour rate limit (with local reset time) · 7-day rate limit (with a countdown to reset, e.g. 6d14h)

Line 2: current directory · current git branch (or, in a worktree session, the worktree name and its original branch)

Normal session, early on (low context usage)

Inside a Claude Code worktree session, deep into a session (high context usage)

When a session uses Claude Code's worktree-isolation feature (the EnterWorktree tool — an isolated checkout on its own branch, used for parallel/experimental work), line 2 swaps the plain branch name for the worktree's name and the branch it originally forked from.

Install

Linux / macOS

git clone https://github.com/GoSlowPoke168/claude-statusline.git
cd claude-statusline
./install.sh

Windows

git clone https://github.com/GoSlowPoke168/claude-statusline.git
cd claude-statusline
powershell -ExecutionPolicy Bypass -File install.ps1

Uses a native PowerShell port of the script — no Git for Windows, bash.exe, or jq required. Only git.exe is needed, and only for the branch segment; everything else works without it.

Running Claude Code inside WSL instead of natively? Use the Linux instructions above from inside your WSL distro.

Restart Claude Code (or start a new session) after installing, either way.

What the installer does

1. Copies the statusline script (statusline-command.sh or .ps1) to ~/.claude/ (or $CLAUDE_CONFIG_DIR if you've set that env var).
2. Linux/macOS only: makes sure jq is installed, via your platform's package manager if it's missing (apt/dnf/yum/pacman/zypper/brew).
3. Merges a statusLine key into settings.json — it only touches that one key, so any other settings you already have are left alone.

Requirements

• Linux/macOS: bash, jq (auto-installed if missing).
• Windows: nothing beyond PowerShell itself (built into every Windows install). git.exe is only needed for the branch segment to resolve — install it however you like (Git for Windows, winget, scoop, etc.), bash is never invoked.

Notes

• The bash version uses GNU date -d, with a fallback to BSD date -r for macOS, to render local rate-limit reset times.
• The context-usage segment has a commented-out (used/max token count) sub-feature — e.g. (116k/1M) next to the percentage. It's disabled by default; uncomment the block in both scripts (search for "Token count") to turn it back on.
• To customize colors or layout, edit statusline-command.sh (Linux/macOS) or statusline-command.ps1 (Windows) directly, then re-run the installer to redeploy it.
• The two scripts are kept in sync by hand — if you change one, mirror the change in the other.