statusline — the savings, always visible

Package scope and prerequisites

This catalog ships instructions, not the executable runtime. Python modules, scripts, local services and optional tools named below must be installed separately from the upstream project. Check their availability before running commands; if they are missing, explain the prerequisite instead of claiming execution or results. The host agent may use model tokens while following these instructions.

python -m skills.statusline .              # one line, safe to embed anywhere
python -m skills.statusline --compact .    # number only, for narrow surfaces
python -m skills.statusline --json .       # ambient-status-v1 contract

🧦 botte · 12,480 tok saved (host) · 41 cache hits · 17L/3C · 2 escalated

Reads the same scoped ambient-status-v1 snapshot as [[dashboard]]. Routing savings come from the host control ledger; route/cache/escalation activity comes from the selected project's .botte/events.jsonl. The scopes stay explicit in JSON and the human line label host counters. Check the installed runtime and data sources rather than treating displayed estimates as measured provider savings. Invalid host counters render as unavailable, never zero. render() never raises.

Wiring it into Claude Code's statusline

This module does not modify your Claude Code settings — wire it in yourself (or ask an agent to, via the update-config skill) by adding to .claude/settings.json:

{
  "statusLine": {
    "type": "command",
    "command": "python -m skills.statusline"
  }
}

The CLI also accepts a JSON payload on stdin (Claude Code's statusline hook convention) and best-effort reads cwd/workspace/project_dir from it, so it works whether invoked with an explicit path or piped session context.

Design

• Best-effort, never blocks the prompt — any failure (missing file, malformed JSON, no .botte dir) falls back to a plain 🧦 botte rather than raising or hanging.
• Local-file reading design — inspect the installed implementation and any forwarding/export configuration; host model usage remains separate.

Related: [[events]] (the data source), [[demo]], [[dashboard]] (the richer views), [[ambient-hud]] (the passive top-center desktop view).