cs-statusline-setup

Install a multi-line PowerShell statusline for Claude Code on Windows.

1|Updated Jun 12, 2026
One-click install
npx skills add https://github.com/Sampi314/Sam-Plugin-Marketplace --skill cs-statusline-setup
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cs-statusline-setup
Source: https://github.com/Sampi314/Sam-Plugin-Marketplace/tree/main/Claude%20Setup/skills/cs-statusline-setup
Command: npx skills add https://github.com/Sampi314/Sam-Plugin-Marketplace --skill cs-statusline-setup

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Claude Code's default statusline lacks visibility into session costs, context window usage, and API rate limits, making it difficult to track spending and avoid hitting limits during long work sessions.

Core Features & Use Cases

  • Multi-line statusline: Displays model name, effort level, session cost, project cost, and version on line 1; context fill bar and burn rate on line 2; 5-hour and weekly usage bars with reset countdowns on lines 3 and 4; and work duration with lines added/removed on line 5.
  • Customisable palettes: Choose from six built-in colour schemes (Sam, Monochrome, HighContrast, Solarized, Nord, Dracula) with visual previews available in the skill documentation, or add your own palette by editing the installer.
  • Two variants: Install the Classic single-script version (~860 lines, stable and well-tested) or the Extended widget-host platform with 14 bundled widgets, Braille sparklines, mode-aware layouts, skill-aware overlays, and an NDJSON events stream for external observability.
  • Use Case: A developer working on a long refactoring session can watch the context bar fill, see the 5-hour rate limit approach, and track cumulative project cost without leaving the terminal.

Quick Start

Use the cs-statusline-setup skill to install Sam's multi-line PowerShell statusline into your Claude Code setup by running the installer script with your preferred palette and bar width options.

Frequently Asked Questions about cs-statusline-setup

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I display Claude Code session costs and context usage in my Windows terminal?

You can display session costs and context usage in your Windows terminal by installing a multi-line PowerShell statusline. It shows model information, session costs, context window fill, and API rate limits directly in your Claude Code prompt.

Can I track 5-hour and weekly API rate limits directly in the Claude Code prompt?

Yes, you can track 5-hour and weekly API rate limits directly in the Claude Code prompt by installing a multi-line PowerShell statusline. It visualizes usage bars with reset countdowns so you can monitor spending and avoid hitting limits during long sessions.

Does the Claude Code statusline for Windows require specific PowerShell versions or dependencies?

The statusline requires PowerShell 5.1+ and Windows Credential Manager access for OAuth fallback. It writes configuration to the Claude settings.json file with backup and rollback support, but requires no external dependencies.

How do I customize the color scheme of my Claude Code terminal statusline?

You can customize the color scheme by choosing from six built-in palettes like Solarized, Nord, Dracula, or HighContrast when running the installer script. You can also add your own custom palette by editing the installer script directly.

What is the difference between the Classic and Extended statusline variants for Claude Code?

The Classic variant is a stable single-script version, while the Extended variant offers a widget-host platform with 14 bundled widgets, Braille sparklines, mode-aware layouts, and an NDJSON events stream for external observability of your terminal usage.

Why does my Claude Code statusline stop working or fail to update during a long refactoring session?

If the statusline fails to update, it may be due to Windows Credential Manager access issues preventing OAuth fallback, or PowerShell version incompatibility. The installer provides backup and rollback support for the settings.json configuration to recover from errors.