Show Claude Code session usage, cost, model, and burn rate.
statuslineCommunity project19,077 repo starsRepo updated Oct 20, 2026
Show model, context, cost, or git information in the terminal status line.
15 selected entries
Browse all Claude pluginsShowing 15 entries
Show Claude Code session usage, cost, model, and burn rate.
statuslineCommunity project19,077 repo starsRepo updated Oct 20, 2026
Configure model, context, cost, and git widgets through a terminal setup UI.
statuslineCommunity project13,346 repo starsRepo updated Oct 19, 2026
Configure a Rust status line with Git, model and context segments through a terminal editor.
statuslineCommunity project3,476 repo starsRepo updated Mar 14, 2026
Install a compact shell status line for quota, working directory and Git context.
statuslineCommunity project1,398 repo starsRepo updated Apr 3, 2026
Choose status-line features interactively, including Git, model and session usage information.
statuslineCommunity project646 repo starsRepo updated Feb 16, 2026
Build a configurable Rust status line with native session modules and optional Starship segments.
statuslineCommunity project430 repo starsRepo updated Sep 6, 2026
Display session context, active components and optional detail rows with a Python status line.
statuslineCommunity project243 repo starsRepo updated Oct 18, 2026
Customize model, context and usage widgets with Classic, Powerline or Capsule layouts.
statuslineCommunity project239 repo starsRepo updated Oct 12, 2026
Compare subscription usage with remaining reset time in a Bash-based status line.
statuslineCommunity project238 repo starsRepo updated Sep 24, 2026
Use Starship prompt styling to build a Claude Code status line with configurable palettes.
statuslineCommunity project153 repo starsRepo updated Apr 30, 2026
Show Git state, model, context and prompt-cache information with a single Node.js renderer.
statuslineCommunity project119 repo starsRepo updated Oct 19, 2026
Keep model, context and usage indicators compact, with optional directory and Git fields.
statuslineCommunity project55 repo starsRepo updated Oct 14, 2026
Render a compact Rust status line with Git branch, context bar and session cost.
statuslineCommunity project42 repo starsRepo updated Jul 5, 2026
Display model and context information in a configurable status line.
statuslineCommunity project8 repo starsRepo updated Oct 13, 2026
Configure a Go status line for project, model, context and optional account usage rows.
statuslineCommunity project2 repo starsRepo updated Oct 19, 2026
Claude Code can run a status line command and display its output near the bottom of the terminal. A line can show the active model, current directory, git branch, context use, or session cost. The command receives session data as JSON on standard input, so scripts should parse only the fields they need and print a short readable line.
Pick the information you actually check during a session. Model and context use help with session awareness, while a branch label helps when you switch repositories. A status line is a compact display, so a few stable fields are easier to read than a long row of counters that wraps in a narrow terminal.
These scripts format data supplied by Claude Code; they do not change the model or enforce a spending limit. The sample cost value is session telemetry, not an invoice. If you need to control a budget or change permissions, configure that separately rather than expecting the display to take action.
Add a `statusLine` command to your Claude Code settings or run a maintained setup tool. The selected projects provide different tradeoffs: a compiled binary, an interactive widget editor, and a usage-focused renderer. Read the source instructions because installing a package alone may not register it in settings. Restart or reload the session to see changes.
The shell examples below require sh and jq; the branch example also uses git. Start with one script. For session cost, save the downloaded file as ~/.claude/statusline-cost.sh, then merge the shown statusLine object into ~/.claude/settings.json. Calling it through sh means you do not need to make the file executable.
Run the fixture command before opening Claude Code. It should print Example model | $1.25 session. That value is deliberately synthetic, so the test does not need a real session or any credentials. Once the script prints correctly, reload Claude Code and compare the live line with the settings you selected.
Model and context
{
"statusLine": {
"type": "command",
"command": "jq -r '[.model.display_name, ((.context_window.used_percentage // 0 | floor | tostring) + \"% context\")] | join(\" | \")'"
}
}Session cost
#!/bin/sh
input=$(cat)
model=$(printf '%s' "$input" | jq -r '.model.display_name // "Claude"')
cost=$(printf '%s' "$input" | jq -r '.cost.total_cost_usd // 0')
printf '%s | $%.2f session\n' "$model" "$cost"
Git branch
#!/bin/sh
input=$(cat)
directory=$(printf '%s' "$input" | jq -r '.workspace.current_dir // .cwd // "."')
branch=$(git -C "$directory" branch --show-current 2>/dev/null || true)
printf 'git: %s\n' "${branch:-detached or not a repository}"
~/.claude/settings.json · session cost
{
"statusLine": {
"type": "command",
"command": "sh \"$HOME/.claude/statusline-cost.sh\""
}
}Test with sample input · terminal
printf '%s\n' '{"model":{"display_name":"Example model"},"cost":{"total_cost_usd":1.25}}' | sh "$HOME/.claude/statusline-cost.sh"The images below come from a listed maintainer’s repository and show real terminal layouts from that project. Use them to compare information density before installing. A screenshot is a preview, not a promise of identical fonts, colors, or values on your machine. Your terminal theme, width, configuration, and Claude Code version all affect the final appearance.
Compare the screenshot with your typical terminal width. A layout that works in a wide window may hide useful fields beside a split editor. Start with a plain-text line to confirm the data, then add separators or color only when the baseline display is working reliably.
The repository demo below belongs to ccstatusline, while the small scripts on this page are standalone examples. Installing the project is optional if you only need one of the shown fields. Use the demo to compare layouts rather than assuming the sample scripts reproduce that full interface.

If no line appears, check that the command runs on its own and that the executable is on your PATH. Then inspect `statusLine` in settings and restart Claude Code. If a line is slow, prefer a local binary or cached data. If cost or context looks wrong, compare the underlying JSON fields and the project’s documented assumptions before changing your configuration.
If the fixture works but the live line is blank, check which settings file is active and whether a later configuration overrides statusLine. Use an absolute script path or the quoted home-directory path shown here. A command that works from your current terminal folder may fail when launched from a different working directory.
If Git information is wrong, use workspace.current_dir from the incoming JSON and run git with -C for that directory. The example reports a fallback outside a repository or on a detached HEAD. If output is slow, remove network calls and expensive repository scans before adding caching or other complexity.
Claude Code documentationA mod is a plugin with JavaScript or TypeScript function hooks running inside Claude Code. It can change the interface or how session events are handled. Skills and MCP servers are separate extension types.
This is an independent directory. Some entries link to Anthropic repositories; others come from community maintainers. Check the source of each entry before installing.
Extensions can read files, run commands, or connect to external services. Review the source and permissions, especially for hooks and MCP servers. A listing here is not a security guarantee.
They describe the linked GitHub repository. A plugin inside a repository does not have its own separate star count or update date.