Claude Code Status Line

• Claude Code Status Line
  • Introduction
  • Installation
    • Configuration
    • Upgrade
  • Features
    • Segments
      • Segment breakdown
      • Detected languages
    • Caching
  • Development
    • Testing
    • Build and publish
      • Configure Publishing to Pypi
      • Publishing to Test Pypi
      • Publishing to Pypi

Introduction

Powerline-style status line for Claude Code.

Requires a Nerd Font installed and setup as your terminals default font.

Recommendation is to install either:

• FiraCode Nerd Font
• JetBrainsMono Nerd Font

Installation

pip install cc-statusline

On newer Linux systems, install with:

pip3 install --break-system-packages cc-statusline

It is recommended to install this status line with the cost tracking hook:

• cc-costtrack

see cc-costtrack.

Configuration

Add to ~/.claude/settings.json:

{
  "statusLine": {
    "type": "command",
    "command": "cc-statusline"
  }
}

Upgrade

Upgrade with pip regularly:

pip install cc-statusline -U

On newer Linux systems, install with:

pip3 install --break-system-packages cc-statusline -U

Features

Segments

project   >   branch_name   >   ai_model   >   ctx% | tokens | cost   >   quota / usages / enterprise   >   cli | mcp

Example (Pro/Max plan):

 my-app   >   feat/abc123   >   Opus 4.6   >   12% | 58.3k | 1.42$   >   34% (2h05m)   >   61% (4.2d)   >   cli | mcp

Example (Enterprise plan / Anthropic API key):

 my-app   >   feat/abc123   >   Opus 4.6   >   12% | 58.3k | 1.42$   >   $78.50 22d   >   cli | mcp

Segment breakdown

* Cost is estimated, and requires the cost tracking hook to function.

Detected languages

The branch segment appends an icon for the detected project language:

• Terraform
• Node.js
• TypeScript
• Python
• Rust
• Go
• Java
• Perl
• Shell

Caching

Data is cached at multiple tiers to keep the status line fast:

Development

Set up a virtual environment:

python3 -m venv .venv

Activate the virtual environment before running any of the steps below:

source .venv/bin/activate

Testing

pip install -e ".[test]"
pytest

Build and publish

Build the distribution:

pip install -e ".[package]"
python -m build

This creates dist/ with .tar.gz and .whl files.

Configure Publishing to Pypi

Configure PyPI credentials in ~/.pypirc:

[distutils]
index-servers =
    pypi
    testpypi

[pypi]
username = __token__
password = pypi-<your-api-token>

[testpypi]
repository = https://test.pypi.org/legacy/
username = __token__
password = pypi-<your-test-api-token>

API tokens can be created at:

• PyPI: https://pypi.org/manage/account/token/
• TestPyPI: https://test.pypi.org/manage/account/token/

Alternatively, set credentials via environment variables instead of ~/.pypirc:

export TWINE_USERNAME=__token__
export TWINE_PASSWORD=pypi-<your-api-token>

To target TestPyPI, override the repository URL:

export TWINE_REPOSITORY_URL=https://test.pypi.org/legacy/

Publishing to Test Pypi

To publish to TestPyPI first:

pip install -e ".[package,publish]"

# Using ini file:
twine upload --repository testpypi dist/*

# Or, with environment variables:
export TWINE_REPOSITORY_URL=https://test.pypi.org/legacy/
twine upload dist/*

Publishing to Pypi

Publish to PyPI:

pip install -e ".[publish]"
twine upload dist/*