Claude Powerline plugin
A statusline for Claude Code: token and cost usage, context left, rate limits and git branch in four styles and six themes
- 1,175 ★ on the repository
- Last commit
- MIT
Extended access
Why this level
- The line runs a package with npx -y and the latest tag on every refresh, so the machine executes a fresh unpinned npm version
- The /powerline wizard writes a settings file in ~/.claude and edits settings.json
- For usage and the cache timer it reads Claude Code session data and keeps a calculation cache in ~/.claude/powerline
Install
- Works in
In your terminal, with SkillFoxx CLI
npx skillfoxx add plugins/claude-powerlineDetects the agents on your machine, shows the access level and pins the version.
Other ways to install
Access and checks
How we reviewExtended accessThe tool runs code or makes network calls and only reads external data.
- The line runs a package with npx -y and the latest tag on every refresh, so the machine executes a fresh unpinned npm version
- The /powerline wizard writes a settings file in ~/.claude and edits settings.json
- For usage and the cache timer it reads Claude Code session data and keeps a calculation cache in ~/.claude/powerline
This is third-party code. Review the repository files before installing.
What it does
Claude Powerline is a vim-style powerline statusline for Claude Code. At the bottom of the terminal it shows how many tokens and dollars a session, a day and a month have used, how much context is left before auto-compact, which git branch you are on and which model answers. It plugs in as `statusLine` in `settings.json`: Claude Code hands the command the current session data and the command prints a colored line made of segments. Segments switch on one by one: directory, git (branch, `SHA`, ahead and behind counts, change counters), model, session, day, month, context, the five-hour and weekly limit windows, metrics (response time, message count, lines added and removed), Claude Code version, subagent, thinking mode, output style, prompt cache timer, tmux, session id and an environment variable value. There are four styles (`minimal`, `powerline`, `capsule`, `tui`) and six themes (`dark`, `light`, `nord`, `tokyo-night`, `rose-pine`, `gruvbox`). In `tui` you can build your own grid with breakpoints and segment templates. Budgets for the session, day, month and limit window give a percentage and a warning, by default from 80 percent. The `/powerline` wizard asks about theme, style, font, segments and budgets step by step, writes `~/.claude/claude-powerline.json` and edits `settings.json` itself. Settings can live in the project (`.claude-powerline.json`), in the home folder or under the XDG standard. Command-line flags beat environment variables, which beat files. Files are reread without a restart.
Who it is for. For people who use Claude Code every day and want to see spend, context and git state without calling separate commands.
Good fit when
- You want to see in Claude Code itself how many tokens and dollars a session, a day and a month have used, with a warning near your own budget
- You want to know how much context is left before auto-compact instead of guessing
- On a Pro or Max plan you need the remaining five-hour and weekly limit windows right in the line
- You want a line with your own theme or a `tui` grid set up with the wizard or the visual editor
- You work in several git worktrees: in such sessions the directory segment shows the original repository path
Not a fit when
- You need a statusline for another agent: the project is described only for Claude Code
- You need usage tables by day, week and project from local logs: `ccusage` builds them, while this line shows current figures only
- The machine has no Node.js 18 or newer or no Git 2.0 or newer: the line command runs on them
- You need a line that does not run a package from the network: the `statusLine` command calls `npx -y @owloops/claude-powerline@latest`
Example request
Set up a Claude Code statusline for me with the nord theme, session and daily spend and the context leftLimitations
- Node.js 18 or newer, Claude Code and Git 2.0 or newer are required. The icons are designed for a Nerd Font; without one, use the `--charset=text` flag and the line is drawn with ASCII characters.
- The five-hour and weekly limit segments appear only when Claude Code itself passes `rate_limits` data, which means Claude.ai Pro and Max subscribers. Without it these segments stay hidden.
- The cache timer updates when Claude Code reruns the line. To keep it ticking while idle, add `refreshInterval` in seconds, minimum 1, to the `statusLine` block.
- The dollar amount is computed one of two ways: `calculated` from a price table in the style of `ccusage`, or `official` from Claude Code hook data. The month segment is off by default, and without setup the month budget is 500 and the day budget is 50.
- The `modelContextLimits` table matters only for Claude Code older than 2.0.65: newer versions report the context window size themselves, including the million-token mode.
- The package version at the time of review is 1.32.4, license MIT.
How to disable. Remove the `statusLine` block from `~/.claude/settings.json` and Claude Code returns to its default line. The wizard plugin is removed through the Claude Code plugin manager. You can delete `~/.claude/claude-powerline.json` and the usage cache in `~/.claude/powerline` by hand.
FAQ
How do I show token and cost usage in the Claude Code statusline?
Enable the `session`, `today` and `month` segments and pick a `type` for each: `cost`, `tokens`, `both` or `breakdown`. `costSource` sets the method: `calculated` or `official`. A budget with an `amount` field adds a percentage and a warning at the `warningThreshold`.
How do I see how much context is left before auto-compact?
The `context` segment shows window fill with the `autocompactBuffer` reserve, 33000 tokens by default. If auto-compact is off on your side, set 0 and the line shows raw fill. `percentageMode` flips the count from remaining to used.
Why does the statusline not show the five-hour and weekly limits?
The `block` and `weekly` segments use the official `rate_limits` data that Claude Code passes to Claude.ai Pro and Max subscribers. Without that data the segments stay hidden. The `showPace` option adds the even-spend figure for the window next to the real one.
Why are there squares instead of icons in the line?
The unicode icons are designed for a Nerd Font. Install one or run the command with the `--charset=text` flag, and the branch, git status and segments are drawn with ASCII characters.
How do I style the line without editing JSON by hand?
The `/powerline` wizard asks for theme, style and segments and writes the settings file itself. There is also a visual editor, Powerline Studio at powerline.owloops.com: you toggle segments with a click, switch themes and copy the finished JSON. You can paste an existing file there and edit it.
Discussion
No questions or reviews yet.
Related
PluginsA customizable status line for Claude Code: model, git branch, context, usage limits and other widgets
A Claude Code plugin: a status line with context, 5-hour and 7-day limits, cost and usage of Codex, Gemini and z.ai
A real-time terminal monitor for Claude Code usage: tokens, messages and cost in the five-hour window, with forecasts and export
A marketplace of 17 Claude Code mods: token-spend breakdown, a rollback edit timeline, assumption tracking, a verification board and a live command feed
A Claude Code plugin that shows a session's CO2 estimate in the status line next to its cost
Counts token use and cost of Claude Code and Codex sessions from local logs and shows remaining limits in the status line
Comparison with similar tools
Entries that share the main search query, and how they differ.
| Entry | Official | Repository stars | Main difference |
|---|---|---|---|
| Claude Powerline (this entry) | no | 1,175 | |
| ccstatusline | no | 13,444 | the line is built from widgets in an interactive interface, including pull request CI status and Claude service state |
| Claude HUD | no | 28,981 | a plugin with a context and limits bar that shows tool activity, subagents and todo progress from the session log |
| ccusage | no | 19,238 | reports by day, week and session from the local logs of many agents, with the statusline as one feature |
README in short
The documentation opens with installation: the wizard through the plugin and a manual block for `settings.json`. It continues with a reference for every segment with a settings example, symbol tables for the `unicode` and text modes, budgets, auto-wrap and the `tui` layout with breakpoints, segment templates, a title bar and a footer. The repository holds ready settings templates for the plugin, `jest` tests, a timing script and the visual editor page. The package is declared dependency-free.