Everything above the prompt.

A multi-line band that shows what your Claude Code session is using, how fast, and what is running, right where you type.

/plugin install console-band --marketplace Derinbay-Labs/console-band
  • Model Opus 5.5, session cost $4.10
  • Main loop working, turn 2:06
  • Context 71% used
  • Session limit 52%, 8 points ahead of pace; weekly 60%, 2 points behind pace
  • Prompt cache: 4:40 left
  • 43 permission checks, 1 denied
  • 2 subagents running
  • Branch feat/rate-limit, 6 modified files
View on GitHubRun it at the Claude Code prompt. Free, MIT licensed. Sample session shown.

Facts

Runs
Only git, read-only
Network
None by default
Narrow terminals
Compact below 100 columns
Licence
MIT, open source

Close up: the work in flight.

Context, limits and cache sit in the band above. These rows show who is working and what they were allowed to do.

Watch subagents while they work

Each subagent gets a card: task, type and model, context and output tokens, requests and elapsed time. Running ones come first.

  • allowed
  • cleared by you
  • pending
  • denied

Tally every permission check

A strip of the latest verdicts on wide terminals, then allowed, cleared by you, pending and denied, with totals for file, shell and other.

Read the last three events

Spawns, hand-backs, edits, errors and refusals, timed to the second and tagged with who did it.

Context by category
System, tools, MCP, agents, memory, skills and messages, reserve dashed.
Limits with pace
Session and weekly use against an even pace, the gap signed.
Cache countdown
Green, amber, red, then cold. 5 or 60 minutes.

Installed in under a minute.

Three steps at the Claude Code prompt. The desktop app has its own route in the FAQ.

  1. Run the install command

    Paste it at the prompt of a Claude Code terminal session.

    /plugin install console-band --marketplace Derinbay-Labs/console-band

  2. Add the marketplace, pick a scope

    Answer y, then choose user scope to load the band in every session.

    y › user scope

  3. Keep working

    The band draws above the prompt. Update later with one command.

    /plugin update console-band

It reads your session. It sends nothing.

console-band only observes. Every hook passes its event on unchanged; none blocks, rewrites or answers for Claude Code.

Runs
Only git, with three fixed read-only commands in the working directory. Nothing else, and never a command it receives.git rev-parse --abbrev-ref HEADgit log -1 --format=%ctgit status --porcelain
Network
None by default. Set both latitude and longitude and it asks open-meteo.com for the weather every 30 minutes, sending only those two numbers.
Reads
Model, version, context breakdown, rate limits, session cost and the folder name. Kept in the session’s plugin state, never written to disk.
Credentials
None read. Tool inputs in the activity log pass a redaction step for common credential formats first.

Questions

Does it work in the desktop app?

Yes. /plugin does not run there: click + next to the prompt box, then Plugins, Add marketplace with Derinbay-Labs/console-band, then Add plugin.

What happens in a narrow terminal?

Below 100 columns the band collapses to six compact rows: model and cost, live state, context, limits, cache and folder.

Can I install it from a shell?

Yes: claude plugin install console-band --marketplace Derinbay-Labs/console-band

Can it block or change what Claude Code does?

No. Every hook passes its event on unchanged, and the band takes no part in permission decisions.

What can I configure?

brand sets the name in the header rule, cacheTtlMinutes matches a 5- or 60-minute cache, city adds a LOC row, and latitude with longitude add the weather.

Put the band above your prompt.

One command at the Claude Code prompt. Update it later with /plugin update console-band.

/plugin install console-band --marketplace Derinbay-Labs/console-band
View on GitHubRun it at the Claude Code prompt. Free, MIT licensed.