v1.4.3

What's Changed

Bug fix release.

• fix: read live effort level from stdin JSON (effort.level) — the statusline now reflects effort changes made via the in-session /effort <level> slash command immediately, instead of staying on the previously persisted settings.json value until restart. Falls back through CLAUDE_CODE_EFFORT_LEVEL → settings.json effortLevel → medium when the stdin field is absent. Thanks @MIT0101 (#42).

Full Changelog: v1.4.2...v1.4.3

v1.4.2

What's Changed

Maintenance release — no user-facing behavior changes.

• Reverted the INSTALL.md lead-in sentence added to the README's Installation section just after v1.4.1 (#37 → #38). The v1.4.1 layout is restored: a direct Ask Claude Code: block with the INSTALL.md reference inside the trailing paragraph.

Full Changelog: v1.4.1...v1.4.2

v1.4.1

What's Changed

• Fix — Windows installs that land on the default Restricted ExecutionPolicy (or a corporate AllSigned one) were failing silently: powershell.exe refused to run the unsigned statusline.ps1 and Claude Code shows no error. The Windows install command in INSTALL.md now passes -ExecutionPolicy Bypass (process-scoped; the machine policy is untouched), leads with pwsh and falls back to Windows PowerShell 5.1, and uses the ~/.claude/statusline/statusline.ps1 path that Claude Code v2.1.47+ now expands on Windows. Closes #25 — thanks @SacrilegeTx for the diagnosis and tested fix (#36).
• Fix — The update check touches statusline-version-cache.json before calling the GitHub API as a stampede lock. If the fetch failed (network blip, rate limit, 5-second timeout), the touched file was left on disk at zero bytes with a fresh mtime, and the 24-hour TTL then suppressed every update check for a full day. Drop the empty lock in the failure path so the next render retries (#30).
• UX — The Update available: <tag> line now ends with Tell Claude: "Find my installed status bar and update it" instead of a repo URL, so a Pro/Max user can copy-paste straight into Claude and let it run the documented update flow (#31). README Updating section aligned with the same wording.
• Docs — Dropped the paste-install alternative from the README (#33) — the clone flow is the only path the update check and the runtime Claude prompt rely on, and a paste install left users stranded on older copies. Removed the now-leftover Recommended subheading since there is nothing left to be recommended over (#35).
• Docs — Refreshed screenshot.png to a current v1.4.0 render and cropped the trailing Now using extra usage tag so the preview fits on narrower pages without horizontal scroll (#29, #32, #34).

Full Changelog: v1.4.0...v1.4.1

v1.4.0

What's Changed

• Fix extra-usage rendering when Claude Code supplies rate_limits on stdin — previously some Pro/Max sessions didn't show the extra-credits segment even when the data was available. Thanks @daniel3303 in #27.
• Lead the README with the clone-based install flow and split the full step-by-step guide into a dedicated INSTALL.md so Claude Code has an authoritative, executable reference when the user asks it to install the status line.
• Bake the target clone path (~/.claude/statusline/) and a pointer to INSTALL.md into the suggested install prompt, so copy-pasting it into a fresh Claude Code session no longer leaves the destination directory ambiguous (#28).

Full Changelog: v1.3.0...v1.4.0

v1.3.0

What's Changed

• Render new xhigh effort level with its own color (purple) — distinguishes it from high (green) and max (red). Claude Code v2.1.111+ introduced xhigh for Opus 4.7. Thanks @FZ1010 in #24.
• Updated README screenshot to showcase the new xhigh color.

Full Changelog: v1.2.0...v1.3.0

v1.2.0

What's New

• Builtin rate limits support — The status line now reads rate_limits directly from Claude Code's JSON input as the primary source for 5h/7d usage display, avoiding the OAuth API call entirely when available. Falls back to OAuth when the data is absent. (#17)
• Empty cache fix — Prevents an empty cache file from blocking usage data fetch (#13)

v1.1.0

What's New

Update Notifications

The status line now checks GitHub for new releases every 24 hours. When a newer version is available, a second line appears below the status bar showing the new version and a link to the repository. The check is cached and fails silently if the API is unreachable.

Effort Level Display Fix

The status line now displays the actual effort level value (low, medium, high, max) instead of hardcoded strings. A new red color is used for max effort, completing the intensity scale:

Level	Color
low	dim
medium	orange
high	green
max	red

Files Changed

• statusline.sh — Bash/Zsh script
• statusline.ps1 — PowerShell script
• README.md — Updated documentation