Skip to main content

Claude Code statusline with real subscription usage data

Project description

Claude Vibeline

CI codecov PyPI Downloads Python License Built with Claude Code

A custom statusline for Claude Code that shows session details, prompt cache status, and rate limits — designed for Pro, Max, and Team users.

my-project │ Opus 4.7 (xhigh) │ cache ◷ 4m │ ctx 1M [###-----] 42% │
sess [##------] 19% 3h12m │ week [--------] 3% 5d20h

Sections wrap to multiple lines based on --columns width, with a trailing to indicate continuation.

Note: This project was developed almost entirely through AI-assisted coding with Claude Code, with human oversight over all design decisions, architecture, and code review.

Features

From Claude Code's session data:

  • Project & model - project name, active model, and effort level (resolved from session transcript with settings.json fallback)
  • Context window - how much of the context window is used, with size indicator (e.g. 200k, 1M)
  • Prompt cache - 5-minute prompt cache TTL, shown as a live countdown
  • Session limit - 5-hour rate limit utilization with reset countdown
  • Weekly limit - 7-day rate limit utilization with reset countdown

Opt-in via --usage-api (from Anthropic's OAuth API):

  • Per-model limits - weekly Opus and Sonnet limits with reset countdowns
  • Extra usage - spend against your monthly extra usage cap with reset countdown

Every section is individually toggleable via CLI flags.

Installation

Available on PyPI. We recommend using uv.

To install:

uv tool install claude-vibeline

To update:

uv tool upgrade claude-vibeline

Setup

Add to ~/.claude/settings.json:

{
  // ...
  "statusLine": {
    "type": "command",
    "command": "claude-vibeline",
    "refreshIntervalSeconds": 30
  }
}

refreshIntervalSeconds tells Claude Code to re-invoke the statusline at the given interval so the prompt cache countdown stays current.

Options

Flag Description
--columns N Terminal width in characters (default: 80)
--bar-width N Progress bar width in characters (default: 8)
--currency S Currency symbol for extra usage (default: )
--no-project Hide project name
--no-model Hide model and effort level
--no-cache Hide prompt cache status
--no-context Hide context window usage
--no-session Hide session (5h) rate limit
--no-weekly Hide weekly (7d) rate limit
--usage-api Fetch per-model and extra usage from OAuth API (off by default)
--opus Show weekly Opus rate limit (requires --usage-api)
--sonnet Show weekly Sonnet rate limit (requires --usage-api)
--extra Show extra usage spend (requires --usage-api)
--no-update Hide update notification
--debug Log each statusline output to debug file

Example with all API sections enabled:

{
  // ...
  "statusLine": {
    "type": "command",
    "command": "claude-vibeline --usage-api --opus --sonnet --extra --currency $"
  }
}
my-project │ Opus 4.7 (xhigh) │ cache ◷ 4m │ ctx 1M [###-----] 42% │
sess [##------] 19% 3h12m │ week [--------] 3% 5d20h │
opus [#-------] 10% 5d20h │ sonnet [--------] 2% 5d20h │
extra 1.23/20$ 7d0h

Rate limits

Stdin rate limits

Session and weekly limits are read directly from Claude Code's session data — no API call or authentication needed. Shown by default; disable with --no-session or --no-weekly.

OAuth API usage

Per-model and extra usage data is fetched from an undocumented Anthropic OAuth endpoint (see Limitations).

  • Requires a valid OAuth token from a Claude Pro, Max, or Team subscription.
  • Responses are cached locally for 60 seconds, and the cache is reused when the token expires or the API is unavailable.
  • If no token or cache exists, sections render as pending.
  • The API is only called when --usage-api is passed with at least one of --opus, --sonnet, or --extra.

Prompt cache

Tracks the 5-minute prompt cache TTL. Each user message or tool use result resets the timer. Computed from timestamps in the session transcript.

Status icons:

  • — warm
  • — warm, but expiring soon
  • — expired
  • — expired at some point since the last user message (prefix)

The countdown is live (◷ 4m, ⚠ 47s, ✗ 0s), so set refreshIntervalSeconds in your statusline config to keep it current.

Pending and reset states

Segments with no data yet or with a rolled-over window always render their label rather than disappearing. Two placeholders distinguish the states:

  • pending. No data yet (fresh session before the first message, or API fetch failed with no cache). Applies to sess, week, cache, opus, sonnet, and extra.
  • reset. The rate-limit window has rolled over and a fresh number is on the way. Applies to sess, week, opus, sonnet, and extra (new calendar month).

extra is the one exception: when the API reports is_enabled: false or omits the field (account has no extra usage configured), the segment is omitted entirely rather than rendered as pending.

Message line

A second line below the statusline carries update notifications and error messages. When both could apply, errors take precedence — only one message is shown at a time.

Update notifications

When a newer version is published on PyPI:

my-project │ Opus 4.7 (xhigh) │ ctx 1M [###-----] 42%
update available: 2.0.0 → 2.0.1 · uv tool upgrade claude-vibeline

PyPI is queried on the first render of a new session, and at most once per 24 hours overall. The cached latest version is reused on every render in between. Disable with --no-update.

Error messages

CLI parse errors (unknown flag, invalid value, missing argument), unexpected render failures, and malformed stdin JSON are prefixed with the program name so it's unambiguous where the error comes from:

my-project │ Opus 4.7 (xhigh) │ ctx 1M [###-----] 42%
claude-vibeline: Unrecognized arguments: --bogus

The statusline still renders with defaults when the args are bad, so a bad flag no longer silences the output entirely. When stdin JSON is unparseable there is nothing to render and only the error message appears. Error messages are always shown — there is no opt-out.

Session data caching

Claude Vibeline caches per-session data to avoid redundant transcript parsing on every invocation. The cache stores:

  • Effort level — the resolved effort and the timestamp of the latest transcript entry processed, so subsequent invocations only scan new entries instead of re-reading the entire transcript.
  • Last user message timestamp — used by the prompt cache countdown as a fallback when the transcript cannot be read.

Stale session files (older than 30 days) are cleaned up whenever a new session writes its first cache entry.

All locally cached data (usage responses, session state, update check) is version-stamped and automatically invalidated on upgrade.

Limitations

  • Undocumented API — the OAuth usage endpoint is undocumented and may break without notice.
  • Limited stdin data — the statusline process receives only a JSON blob on stdin. Claude Code's own CLI arguments (e.g. --model) and internal environment variables are not accessible.
  • Effort level is inferred — effort is not provided in stdin. It is resolved from the session transcript by scanning for /model and /effort commands, with a settings.json fallback. After session resume, effort is shown with a ? suffix until /effort or /model is used.
  • No session fork support — forked sessions share a transcript file. The prompt cache countdown and effort detection may be inaccurate because messages from all forks are interleaved.
  • No subagent tracking — subagents run in separate sessions with their own prompt cache, but the statusline only tracks the main session's cache.

Development

Requires uv.

Clone and setup:

git clone https://github.com/hstojanovic/claude-vibeline.git
cd claude-vibeline
uv sync

Run checks:

uv run ruff format --check
uv run ruff check
uv run ty check
uv run pytest --cov

Build:

uv build

Pass --debug to log each statusline invocation as JSONL, including the stdin input, parsed arguments, resolved effort, usage data, and rendered output.

License

This project is licensed under the MIT license.


Claude Vibeline is an independent project and is not affiliated with or endorsed by Anthropic.

Project details


Download files

Download the file for your platform. If you're not sure which to choose, learn more about installing packages.

Source Distribution

claude_vibeline-3.1.0.tar.gz (17.4 kB view details)

Uploaded Source

Built Distribution

If you're not sure about the file name format, learn more about wheel file names.

claude_vibeline-3.1.0-py3-none-any.whl (22.6 kB view details)

Uploaded Python 3

File details

Details for the file claude_vibeline-3.1.0.tar.gz.

File metadata

  • Download URL: claude_vibeline-3.1.0.tar.gz
  • Upload date:
  • Size: 17.4 kB
  • Tags: Source
  • Uploaded using Trusted Publishing? Yes
  • Uploaded via: twine/6.1.0 CPython/3.13.12

File hashes

Hashes for claude_vibeline-3.1.0.tar.gz
Algorithm Hash digest
SHA256 a575570a58261451a1c4a6553d59ecd7482c6bc78fd09e017cf8bfbaadf218b1
MD5 f6a568c9f590b8a1e0fae96d3e78987e
BLAKE2b-256 71480dc0d230177ba2b229dc02ad3fa1395d9e18203ea7af9dd03bebd98b2473

See more details on using hashes here.

Provenance

The following attestation bundles were made for claude_vibeline-3.1.0.tar.gz:

Publisher: publish.yml on hstojanovic/claude-vibeline

Attestations: Values shown here reflect the state when the release was signed and may no longer be current.

File details

Details for the file claude_vibeline-3.1.0-py3-none-any.whl.

File metadata

File hashes

Hashes for claude_vibeline-3.1.0-py3-none-any.whl
Algorithm Hash digest
SHA256 bdcb6b16a5ba53c29abdb51fafeb9b95709201aeb9e09410c31b08067e3188cc
MD5 36a4953584606ffa5715dde2f193f572
BLAKE2b-256 e74f1c4dcb2c269ac80f159bacacea8c886168f95415d93738df017c6d14093a

See more details on using hashes here.

Provenance

The following attestation bundles were made for claude_vibeline-3.1.0-py3-none-any.whl:

Publisher: publish.yml on hstojanovic/claude-vibeline

Attestations: Values shown here reflect the state when the release was signed and may no longer be current.

Supported by

AWS Cloud computing and Security Sponsor Datadog Monitoring Depot Continuous Integration Fastly CDN Google Download Analytics Pingdom Monitoring Sentry Error logging StatusPage Status page