Rich statusline for Claude Code — watch your tokens burn.

• Cache TTL countdown ⭐ — progress bar + MM:SS timer tracking the 5-minute prompt cache window. When half the time is gone, Burnbar fires a notification using Claude Code's own notification settings (terminal bell, iTerm2, Ghostty, Kitty — whatever you have configured). No more paying to re-warm a cache you didn't know had expired.
• Context window progress bar with color gradient (green → yellow → red)
• Partial block characters (▏▎▍▌▋▊▉) for smooth, sub-cell precision
• Token count showing current context size, color-matched to usage level
• Cost tracking — per-message input cost estimate and cumulative session total
• Model-aware pricing — auto-detects Opus/Sonnet/Haiku and applies correct rates
• user@host:cwd header line for quick orientation
• Zero configuration — auto-configures on install; backs up any existing statusline

In Claude Code, run:

/plugin marketplace add devnix/burnbar
/plugin install burnbar@burnbar

Then restart Claude Code. The statusline appears automatically.

Burnbar installs a SessionStart hook that auto-configures your statusline in ~/.claude/settings.json — but only if no statusline is already set. If you already have one, Burnbar won't touch it.

To switch to Burnbar when you already have a statusline, use the /burnbar skill — it backs up your current config and lets you restore it later.

The statusline script is symlinked to ~/.claude/burnbar-statusline.sh. On each session start, the symlink is recreated pointing to the current plugin version — so updates take effect immediately if the plugin directory is edited in place, or on the next restart after a version upgrade.

Secondary Claude profiles are supported: if CLAUDE_CONFIG_DIR is set, Burnbar uses it instead of ~/.claude for settings, the stable script, and all cache state files. Set it in the environment when launching Claude Code so hooks and the statusline inherit it. Paths in this README show the ~/.claude default — substitute your config dir if you use a profile.

• jq — JSON processor (most systems have it; apt install jq / brew install jq)
• A terminal with ANSI color support (virtually all modern terminals)

If you prefer not to use the plugin system:

1. Copy statusline.sh somewhere permanent (e.g., ~/.claude/statusline.sh)
2. Add to ~/.claude/settings.json:

   {
     "statusLine": {
       "command": "bash ~/.claude/statusline.sh",
       "refreshInterval": 1
     }
   }

3. Restart Claude Code

The plugin includes a /burnbar skill for managing the statusline from within Claude Code:

Burnbar works out of the box with sensible defaults. All configuration is via environment variables — set them in your shell profile or inline in the statusline command.

Format string for the statusline. Use {tag} placeholders for dynamic values, \n for newlines, and \033[...]m...\033[00m for ANSI colors. Any other text is rendered as-is.

Default (when BURNBAR_FORMAT is not set):

'\033[01;32m{user}@{host}\033[00m:\033[01;34m{cwd}\033[00m\n{model}  {bar}  {pct}  {ctx}  {next}  {total}  {cache}  {spark}  {delta}'

Examples:

# Hide costs (useful when screen sharing)
export BURNBAR_FORMAT='\033[01;32m{user}@{host}\033[00m:\033[01;34m{cwd}\033[00m\n{model}  {bar}  {pct}  {ctx}'

# Minimal — just the bar and percentage
export BURNBAR_FORMAT='{bar}  {pct}'

# Custom separator and emoji
export BURNBAR_FORMAT='{model} ·· {bar} {pct} 🔥 {ctx}  {next}'

# Single line, no header
export BURNBAR_FORMAT='{model}  {bar}  {pct}  {ctx}  {next}  {total}  {cache}'

Progress bar width in terminal cells. Default: 30.

export BURNBAR_BAR_WIDTH=20

You can set variables inline in your ~/.claude/settings.json:

{
  "statusLine": {
    "command": "BURNBAR_FORMAT='\\033[01;32m{user}@{host}\\033[00m:\\033[01;34m{cwd}\\033[00m\\n{model}  {bar}  {pct}  {ctx}' bash /path/to/statusline.sh"
  }
}

The prompt cache has a 5-minute TTL — after expiration, your next message reprocesses the entire conversation (higher latency, higher cost). The {cache} tag shows a progress bar that drains over 5 minutes with a MM:SS countdown, so you can decide whether to keep going or start fresh.

The timer resets on every API call — when you submit a message (UserPromptSubmit) or Claude uses a tool (PostToolUse). Before your first interaction, the bar renders in a neutral grey state with --:--.

When the cache is created, Burnbar records the current model and effort level (per-session, using session_id). If you switch models or effort without sending a new message, a ⚠ model or ⚠ effort alert appears — the existing cache may not apply. The alert clears on your next API call.

Each workspace gets its own cache timer. On session start, the cache is cleared automatically so stale data from previous sessions never causes false alerts. Timestamp files live at ~/.claude/.cache-ts-<hash> (or $CLAUDE_CONFIG_DIR/.cache-ts-<hash> for secondary profiles). Clean up with rm ~/.claude/.cache-ts-*.

Cache progress bar width in terminal cells. Default: 10.

export BURNBAR_CACHE_WIDTH=15

The {spark} tag draws a compact bar chart of how much each turn cost, so spending spikes stand out at a glance:

total:$3.42  ⣀⣀⣀⣸⣀⣠⣀⣀

Each turn's cost (the delta of cost.total_cost_usd between responses) is scaled against the most expensive turn in the visible window. In the default braille/octant modes, each terminal cell packs two turns side by side — the default 8 cells cover the last 16 turns.

The sparkline always renders at its full configured width — unused cells show the same grey background as the unfilled bar sections, so the layout stays stable as turns accumulate.

The first data point appears after Claude's second response (one full turn must complete to measure its cost). The {delta} tag shows the numeric value of the most recent turn's cost.

Rendering mode. Default: auto.

export BURNBAR_SPARK=blocks

Sparkline width in terminal cells. Default: 8 (= 16 turns in braille/octant, 8 in blocks).

export BURNBAR_SPARK_WIDTH=12

Cost estimates use the following rates (per 1M tokens):

The total cost uses Claude Code's authoritative cost.total_cost_usd field. The next cost is an estimate of the current context input cost.

In Claude Code, run:

/plugin uninstall burnbar@burnbar

To restore your previous statusline, use /burnbar restore or manually delete the "statusLine" key from ~/.claude/settings.json.

Fistro Public License v1.0 "Diodená" — haz lo que te salga del fistro duodenarl.