Keyboard shortcuts

Press ← or β†’ to navigate between chapters

Press S or / to search in the book

Press ? to show this help

Press Esc to hide this help

🏠 Back to Blog

CC4E #7: Your Status Line Is Empty (Let’s Fix That)

Author: Hannah Stulberg | Published: 2026-03-13

Turn the bottom of your terminal into a personal command center. Only available in the CLI (not VS Code/Cursor extensions).

Core Argument

Every time you stop to check something (model, folder, context usage, branch, email, calendar), you break flow. The status line makes critical info always visible.

Configuration

Lives in ~/.claude/settings.json (global, applies across all projects).

  • Mac/Linux: Inline commands in settings.json (requires restart)
  • Windows: Write a Node.js script at ~/.claude/statusline.js (updates automatically)

Part 1: Core Dashboard

Basic Elements

  • Current folder and model name
  • Custom labels, emoji icons, Unicode symbols

Visual Styles

  • Plain text with pipes – clean, works out of the box
  • Powerline – segmented colored blocks with arrow separators (requires Nerd Font, e.g., JetBrains Mono Nerd Font)

Context Progress Bar (Essential)

Color-coded bar showing context window fullness:

  • Green (< 50%) – keep going
  • Yellow (50-70%) – start wrapping up or plan a compact
  • Red (> 70%) – stop and compact now

Usage Tracking

  • API users: Session cost in USD
  • Max/Pro plan users: 5-hour and 7-day rolling utilization percentages
    • Data from https://api.anthropic.com/api/oauth/usage (undocumented, may change)

Part 2: External Data

Two universal principles:

  1. Caching – fetch external data on intervals (every 5-15 min), not every few seconds
  2. Conditional display – show/hide based on conditions (time of day, whether an event is on)

Three Data Sources

SourceExamplesSetup
WebWeather, air quality, stocks, sports, transit, countdown timersNone
CLI toolsGit branch, uncommitted files, open PRs (via gh)Install tools
MCP/APIGmail count, calendar events, Slack unreadsOne-time MCP setup

Google Workspace MCP Setup (~15 min)

  1. Create a Google Cloud project
  2. Configure OAuth consent screen
  3. Create OAuth credentials (Desktop app type)
  4. Add yourself as a test user
  5. Enable Google APIs (Gmail, Calendar, Drive, Docs, Sheets, Slides)
  6. Add credentials to Claude Code
  7. Authenticate via browser
  8. Restart Claude Code

Once connected, Google data is available for everything, not just the status line.

Key Takeaway

Start with the basics (model, folder, context bar) and add more as you notice what keeps pulling you out of your workflow. The pattern is always: tell Claude what you want to see, Claude figures out how to get the data.