Skip to main content
statuslinesSource-backedReview first Safety Privacy

Daily Usage Percentage Tracker - Statuslines

Claude Code daily usage quota tracker showing percentage of daily limit consumed with visual progress bar, time remaining, and budget pacing indicators.

by JSONbored·added 2025-10-25·
HarnessClaude Code
Language:bash
Review first review before installing

Open the source and read safety notes before installing.

Citation facts

Source-backed facts for citing this resource, derived directly from the registry — also available as plain text for AI assistants.

Source URLs
https://code.claude.com/docs/en/statusline, https://github.com/JSONbored/awesome-claude/blob/main/content/statuslines/daily-usage-percentage-tracker.mdx
Safety notes
Runs as a Claude Code statusline command on every refresh and depends on the local shell environment; a failure only affects status rendering, not your session.
Privacy notes
Reads the Claude Code statusline JSON from stdin (model, workspace path, token usage) and renders it in the local terminal; it does not send data off-machine.
Author
JSONbored
Claim status
unclaimed
Last verified
2025-10-25

Decision playbook

Review trust signals before you adopt

Signals are present but mixed. Use the checklist below to confirm the source and operational safety for your environment.

Compare context
Selected

0

Current score

78

Baseline

Delta

No baseline selected

No major trust-signal divergence detected in the current selection.

Source and provenance checks

Complete

Confirm ownership and provenance before trusting install instructions.

  • Source link availableRequired

    Open the canonical repository and verify ownership.

    Done
  • Source provenance statusRequired

    Marked as source-backed.

    Done
  • Metadata reviewed

    Registry metadata indicates a reviewed listing.

    Done

Safety and privacy checks

Complete

Validate risk disclosures before installation or API wiring.

  • Safety notes presentRequired

    Review the listed safety guidance before running commands.

    Done
  • Privacy notes presentRequired

    Review data handling notes before connecting accounts or secrets.

    Done
  • Trust level risk gateRequired

    Trust level does not block evaluation.

    Done

Package and install checks

Needs review

Check package metadata and artifact integrity signals.

  • Install payload available

    Install or copy payload is available for review.

    Done
  • Package verification flag

    No package verification flag provided.

    Pending
  • Checksum metadata

    No checksum provided for downloaded artifact.

    Pending

Compare-driven decision checks

Needs review

Use compare context to validate trade-offs before adoption.

  • Compare tray has multiple entries

    Add at least one more entry to compare trust differences.

    Pending
  • Baseline comparison available

    No baseline peer selected yet.

    Pending
  • Diverging trust signals identified

    No major trust-signal divergence found.

    Pending

Setup at a glance

Config edit

Copy-ready — paste the snippet to get started.

Install command

Not provided

Config snippet

Provided

Copy snippet

Provided

Prerequisites

6 to clear

Platforms

1 listed

Difficulty

8/100

Adoption plan

Balanced adoption plan

Current risk score 16/100. Use staged verification before broader rollout.

Risk 16

Pre-adoption checks

Validate source and review signals before any execution.

  • Confirm source provenanceRequired

    Source URL/provenance metadata is present.

    Done
  • Confirm metadata review state

    Listing has review metadata.

    Done
  • Verify install payload

    Install/config payload exists and can be inspected.

    Done

Security checks

Confirm safety, privacy, and package integrity signals.

  • Review safety notesRequired

    Safety notes are present.

    Done
  • Review privacy notesRequired

    Privacy notes are present.

    Done
  • Verify package integrity metadata

    No package verification/checksum metadata.

    Pending

Rollout

Adopt in controlled steps based on the selected plan.

  • Run in isolated sandbox firstRequired

    Use a constrained sandbox and observe behavior across multiple tasks.

    Pending
  • Roll out graduallyRequired

    Roll out to a small cohort before wider usage.

    Pending
  • Set monitoring and fallback

    Define rollback path and monitor errors after adoption.

    Pending

Evidence readiness

Evidence readiness matrix · balanced

Required evidence gates are covered (5/6 signals complete).

Risk 15

Source provenance

Present

Source repository/provenance is listed.

Required in this preset

Metadata review

Present

Review metadata is present.

Required in this preset

Safety notes

Present

Safety notes are present.

Required in this preset

Privacy notes

Present

Privacy notes are present.

Optional in this preset

Package integrity

Missing

Package integrity metadata is missing.

Optional in this preset

Install payload

Present

Install payload is available.

Required in this preset

Required evidence gates are covered for this preset.

Decision timeline

Decision timeline · balanced

5/6 steps complete with no blocking gaps for this preset.

Risk 14

triage

Confirm source provenanceRequired

Source/provenance metadata is available.

Done

triage

Check metadata review statusRequired

Review metadata is available.

Done

verify

Review safety notesRequired

Safety notes are available.

Done

verify

Review privacy notes

Privacy notes are available.

Done

verify

Validate package integrity metadata

Package integrity metadata is missing.

Pending

rollout

Verify install payload and commandsRequired

Install payload is available.

Done

No required blockers for this timeline preset.

Prerequisite readiness

Prerequisite readiness

6 prerequisites to line up before setup.

0/6 ready
Install & runtime1Network & hosting1General4

Safety & privacy surface

Safety & privacy surface

1 safety and 1 privacy notes across 1 risk area. Review closely: credentials & tokens.

1 area
  • SafetyCredentials & tokensRuns as a Claude Code statusline command on every refresh and depends on the local shell environment; a failure only affects status rendering, not your session.
  • PrivacyCredentials & tokensReads the Claude Code statusline JSON from stdin (model, workspace path, token usage) and renders it in the local terminal; it does not send data off-machine.

Safety notes

  • Runs as a Claude Code statusline command on every refresh and depends on the local shell environment; a failure only affects status rendering, not your session.

Privacy notes

  • Reads the Claude Code statusline JSON from stdin (model, workspace path, token usage) and renders it in the local terminal; it does not send data off-machine.

Prerequisites

  • Claude Code CLI installed and configured
  • Bash shell available (bash 4.0+ recommended for arithmetic operations)
  • jq command-line JSON processor (jq 1.6+ recommended for safe extraction with // defaults)
  • bc calculator (bc 1.07+ required for floating point calculations - script will fail without bc)
  • Terminal with ANSI color code support (256-color mode recommended for color-coded usage indicators)
  • Write access to home directory (~/.claude-code-usage) for persistent daily usage tracking files

Schema details

Install type
config
Reading time
3 min
Difficulty score
8
Troubleshooting
Yes
Breaking changes
No
Skill and platform metadata
Retrieval sources
https://code.claude.com/docs/en/statusline
Runtime and command metadata
Script language
bash
Script body
#!/usr/bin/env bash

# Daily Usage Percentage Tracker for Claude Code
# Tracks progress toward daily usage limits

# Read JSON from stdin
read -r input

# Extract session cost
session_cost=$(echo "$input" | jq -r '.cost.total_cost_usd // 0')

# Daily usage tracking file (resets at midnight)
USAGE_DIR="${HOME}/.claude-code-usage"
mkdir -p "$USAGE_DIR"

# Get current date for daily reset
current_date=$(date +%Y-%m-%d)
USAGE_FILE="${USAGE_DIR}/daily-${current_date}.usage"

# Initialize usage file if doesn't exist
if [ ! -f "$USAGE_FILE" ]; then
  echo "0" > "$USAGE_FILE"
fi

# Read cumulative daily usage
daily_usage=$(cat "$USAGE_FILE")

# Update with current session cost (simple addition)
# Note: This is per-session tracking, may need deduplication for accuracy
updated_usage=$(echo "$daily_usage + $session_cost" | bc)
echo "$updated_usage" > "$USAGE_FILE"

# CONFIGURABLE: Set your daily budget limit (default $10/day)
DAILY_LIMIT=10.00

# Calculate percentage of daily limit used
if (( $(echo "$DAILY_LIMIT > 0" | bc -l) )); then
  usage_percentage=$(echo "scale=1; ($updated_usage * 100) / $DAILY_LIMIT" | bc)
else
  usage_percentage=0
fi

# Convert to integer for comparisons
usage_percentage_int=$(echo "$usage_percentage / 1" | bc)

# Cap percentage at 100 for display (can exceed in practice)
if [ $usage_percentage_int -gt 100 ]; then
  display_percentage=100
  OVERFLOW=true
else
  display_percentage=$usage_percentage_int
  OVERFLOW=false
fi

# Calculate remaining budget
remaining=$(echo "$DAILY_LIMIT - $updated_usage" | bc)

# Color coding based on usage percentage
if [ $usage_percentage_int -lt 50 ]; then
  USAGE_COLOR="\033[38;5;46m"   # Green: <50% used
  USAGE_ICON="✓"
  USAGE_STATUS="ON TRACK"
elif [ $usage_percentage_int -lt 80 ]; then
  USAGE_COLOR="\033[38;5;226m"  # Yellow: 50-80% used
  USAGE_ICON="⚠"
  USAGE_STATUS="PACING HIGH"
elif [ $usage_percentage_int -lt 100 ]; then
  USAGE_COLOR="\033[38;5;208m"  # Orange: 80-100% used
  USAGE_ICON="⏰"
  USAGE_STATUS="NEAR LIMIT"
else
  USAGE_COLOR="\033[38;5;196m"  # Red: >100% used (over budget)
  USAGE_ICON="✗"
  USAGE_STATUS="OVER BUDGET"
fi

# Build progress bar (20 characters wide)
bar_filled=$(( display_percentage / 5 ))  # Each char = 5%
bar_empty=$(( 20 - bar_filled ))

if [ $bar_filled -gt 0 ]; then
  bar=$(printf "█%.0s" $(seq 1 $bar_filled))$(printf "░%.0s" $(seq 1 $bar_empty))
else
  bar="░░░░░░░░░░░░░░░░░░░░"
fi

# Calculate hours remaining in day for pacing
current_hour=$(date +%H)
hours_remaining=$((24 - current_hour))

# Pacing indicator (are we on track for 24-hour period?)
expected_percentage=$(( (24 - hours_remaining) * 100 / 24 ))
if [ $usage_percentage_int -gt $expected_percentage ] && [ $hours_remaining -gt 0 ]; then
  PACING="📈 ahead of pace"
elif [ $usage_percentage_int -lt $expected_percentage ] && [ $hours_remaining -gt 0 ]; then
  PACING="📉 below pace"
else
  PACING=""
fi

# Format remaining budget
if (( $(echo "$remaining > 0" | bc -l) )); then
  remaining_display="\$${remaining} left"
else
  remaining_display="\$0.00 left"
fi

RESET="\033[0m"

# Output statusline
if [ "$OVERFLOW" = true ]; then
  echo -e "${USAGE_ICON} Daily: ${USAGE_COLOR}${bar}${RESET} ${usage_percentage}% | ${USAGE_STATUS} | ${remaining_display}"
else
  echo -e "${USAGE_ICON} Daily: ${USAGE_COLOR}${bar}${RESET} ${usage_percentage}% | ${remaining_display} ${PACING}"
fi
Full copyable content
{
  "statusLine": {
    "type": "command",
    "command": "$CLAUDE_PROJECT_DIR/.claude/statuslines/daily-usage-percentage-tracker.sh",
    "refreshInterval": 2000
  }
}

About this resource

Features

  • Daily usage quota tracking against configurable budget limit (default $10/day)
  • Percentage of daily limit consumed with visual 20-char progress bar
  • Remaining budget calculation updated in real-time
  • Budget pacing indicator comparing actual vs expected usage by hour
  • Automatic daily reset at midnight (date-based tracking files)
  • Color-coded status (green <50%, yellow 50-80%, orange 80-100%, red >100%)
  • Overflow detection and warnings when exceeding daily budget
  • Persistent usage storage per day in ~/.claude-code-usage

Use Cases

  • Budget management for daily Claude Code spending limits
  • Preventing unexpected overspending with real-time alerts
  • Tracking usage pacing throughout the day
  • Setting and monitoring daily cost budgets
  • Team cost allocation per developer per day
  • Identifying days with abnormally high usage for analysis

Requirements

  • Claude Code CLI installed and configured
  • Bash shell available (bash 4.0+ recommended for arithmetic operations)
  • jq command-line JSON processor (jq 1.6+ recommended for safe extraction with // defaults)
  • bc calculator (bc 1.07+ required for floating point calculations - script will fail without bc)
  • Terminal with ANSI color code support (256-color mode recommended for color-coded usage indicators)
  • Write access to home directory (~/.claude-code-usage) for persistent daily usage tracking files

Configuration

{
  "statusLine": {
    "type": "command",
    "command": "$CLAUDE_PROJECT_DIR/.claude/statuslines/daily-usage-percentage-tracker.sh",
    "refreshInterval": 2000
  }
}

Examples

Enhanced Daily Usage Tracker with Session Deduplication

Extended version with session ID tracking to prevent duplicate cost additions

#!/usr/bin/env bash

# Enhanced Daily Usage Tracker with Session Deduplication

input=$(cat)

session_cost=$(echo "$input" | jq -r '.cost.total_cost_usd // 0')
session_id=$(echo "$input" | jq -r '.session_id // ""')

USAGE_DIR="${HOME}/.claude-code-usage"
mkdir -p "$USAGE_DIR"

current_date=$(date +%Y-%m-%d)
USAGE_FILE="${USAGE_DIR}/daily-${current_date}.usage"
SESSION_FILE="${USAGE_DIR}/daily-${current_date}.sessions"

# Initialize files if don't exist
if [ ! -f "$USAGE_FILE" ]; then
  echo "0" > "$USAGE_FILE"
fi

if [ ! -f "$SESSION_FILE" ]; then
  touch "$SESSION_FILE"
fi

# Check if session already tracked
if [ -n "$session_id" ] && grep -q "^$session_id:" "$SESSION_FILE" 2>/dev/null; then
  # Session already tracked, don't add again
  daily_usage=$(cat "$USAGE_FILE")
else
  # New session, add cost and track session
  daily_usage=$(cat "$USAGE_FILE")
  updated_usage=$(echo "$daily_usage + $session_cost" | bc 2>/dev/null || echo "$daily_usage")
  echo "$updated_usage" > "$USAGE_FILE"

  if [ -n "$session_id" ]; then
    echo "$session_id:$session_cost" >> "$SESSION_FILE"
  fi
fi

DAILY_LIMIT=${DAILY_USAGE_LIMIT:-10.00}

if (( $(echo "$DAILY_LIMIT > 0" | bc -l 2>/dev/null || echo "0") )); then
  usage_percentage=$(echo "scale=1; ($daily_usage * 100) / $DAILY_LIMIT" | bc 2>/dev/null || echo "0")
else
  usage_percentage=0
fi

usage_percentage_int=$(echo "$usage_percentage / 1" | bc 2>/dev/null || echo "0")

if [ $usage_percentage_int -lt 50 ]; then
  USAGE_COLOR="\033[38;5;46m"
  USAGE_ICON="✓"
elif [ $usage_percentage_int -lt 80 ]; then
  USAGE_COLOR="\033[38;5;226m"
  USAGE_ICON="⚠"
elif [ $usage_percentage_int -lt 100 ]; then
  USAGE_COLOR="\033[38;5;208m"
  USAGE_ICON="⏰"
else
  USAGE_COLOR="\033[38;5;196m"
  USAGE_ICON="✗"
fi

bar_filled=$((usage_percentage_int / 5))
bar_empty=$((20 - bar_filled))

if [ $bar_filled -gt 0 ]; then
  bar=$(printf "█%.0s" $(seq 1 $bar_filled))$(printf "░%.0s" $(seq 1 $bar_empty))
else
  bar="░░░░░░░░░░░░░░░░░░░░"
fi

remaining=$(echo "$DAILY_LIMIT - $daily_usage" | bc 2>/dev/null || echo "$DAILY_LIMIT")

if (( $(echo "$remaining > 0" | bc -l 2>/dev/null || echo "0") )); then
  remaining_display="$${remaining} left"
else
  remaining_display="$0.00 left"
fi

RESET="\033[0m"

echo -e "${USAGE_ICON} Daily: ${USAGE_COLOR}${bar}${RESET} ${usage_percentage}% | ${remaining_display}"

Daily Usage Tracker with Custom Budget Limit

Configurable daily budget limit via environment variable

#!/usr/bin/env bash

# Daily Usage Tracker with Custom Budget Limit

DAILY_LIMIT=${DAILY_USAGE_LIMIT:-10.00}

input=$(cat)

session_cost=$(echo "$input" | jq -r '.cost.total_cost_usd // 0')

USAGE_DIR="${HOME}/.claude-code-usage"
mkdir -p "$USAGE_DIR"

current_date=$(date +%Y-%m-%d)
USAGE_FILE="${USAGE_DIR}/daily-${current_date}.usage"

if [ ! -f "$USAGE_FILE" ]; then
  echo "0" > "$USAGE_FILE"
fi

daily_usage=$(cat "$USAGE_FILE" 2>/dev/null || echo "0")
updated_usage=$(echo "$daily_usage + $session_cost" | bc 2>/dev/null || echo "$daily_usage")
echo "$updated_usage" > "$USAGE_FILE"

if (( $(echo "$DAILY_LIMIT > 0" | bc -l 2>/dev/null || echo "0") )); then
  usage_percentage=$(echo "scale=1; ($updated_usage * 100) / $DAILY_LIMIT" | bc 2>/dev/null || echo "0")
else
  usage_percentage=0
fi

usage_percentage_int=$(echo "$usage_percentage / 1" | bc 2>/dev/null || echo "0")

if [ $usage_percentage_int -lt 50 ]; then
  USAGE_COLOR="\033[38;5;46m"
  USAGE_ICON="✓"
elif [ $usage_percentage_int -lt 80 ]; then
  USAGE_COLOR="\033[38;5;226m"
  USAGE_ICON="⚠"
elif [ $usage_percentage_int -lt 100 ]; then
  USAGE_COLOR="\033[38;5;208m"
  USAGE_ICON="⏰"
else
  USAGE_COLOR="\033[38;5;196m"
  USAGE_ICON="✗"
fi

bar_filled=$((usage_percentage_int / 5))
bar_empty=$((20 - bar_filled))

if [ $bar_filled -gt 0 ]; then
  bar=$(printf "█%.0s" $(seq 1 $bar_filled))$(printf "░%.0s" $(seq 1 $bar_empty))
else
  bar="░░░░░░░░░░░░░░░░░░░░"
fi

remaining=$(echo "$DAILY_LIMIT - $updated_usage" | bc 2>/dev/null || echo "$DAILY_LIMIT")

if (( $(echo "$remaining > 0" | bc -l 2>/dev/null || echo "0") )); then
  remaining_display="$${remaining} left"
else
  remaining_display="$0.00 left"
fi

RESET="\033[0m"

echo -e "${USAGE_ICON} Daily: ${USAGE_COLOR}${bar}${RESET} ${usage_percentage}% | ${remaining_display} (limit: $${DAILY_LIMIT})"

Daily Usage Percentage Tracker Installation Example

Complete setup script with usage directory creation and bc verification

#!/bin/bash
# Installation script for Daily Usage Percentage Tracker

mkdir -p .claude/statuslines

# Check for bc (required for floating point calculations)
if ! command -v bc &> /dev/null; then
  echo "Installing bc for floating point calculations..."
  if [[ "$OSTYPE" == "darwin"* ]]; then
    brew install bc
  elif [[ "$OSTYPE" == "linux-gnu"* ]]; then
    sudo apt-get install -y bc || sudo yum install -y bc
  else
    echo "Please install bc manually: https://www.gnu.org/software/bc/"
  fi
fi

# Create usage directory
mkdir -p ~/.claude-code-usage

echo "Usage directory created: ~/.claude-code-usage"

cat > .claude/statuslines/daily-usage-percentage-tracker.sh << 'SCRIPT_EOF'
#!/usr/bin/env bash
# Paste the full statusline script from the primary example above before running this installer.
SCRIPT_EOF

chmod +x .claude/statuslines/daily-usage-percentage-tracker.sh

# Add to settings.json
if [ ! -f .claude/settings.json ]; then
  echo '{"statusLine":{"type":"command","command":"$CLAUDE_PROJECT_DIR/.claude/statuslines/daily-usage-percentage-tracker.sh","refreshInterval":2000}}' > .claude/settings.json
else
  jq '.statusLine = {"type":"command","command":"$CLAUDE_PROJECT_DIR/.claude/statuslines/daily-usage-percentage-tracker.sh","refreshInterval":2000}' .claude/settings.json > .claude/settings.json.tmp
  mv .claude/settings.json.tmp .claude/settings.json
fi

echo "Daily Usage Percentage Tracker installed successfully!"
echo "Note: Set custom daily limit: export DAILY_USAGE_LIMIT=25.00 (default: $10/day)"
echo "Usage files stored in: ~/.claude-code-usage/"

Troubleshooting

Usage percentage not updating or stuck at 0%

Verify cost.total_cost_usd field exists: echo '$input' | jq .cost.total_cost_usd. Check usage file exists: cat ~/.claude-code-usage/daily-$(date +%Y-%m-%d).usage. Ensure bc is installed: which bc. Script uses simple addition - may need session deduplication for accuracy across multiple statusline updates. Verify file is writable: touch ~/.claude-code-usage/test && rm ~/.claude-code-usage/test.

Daily limit showing OVER BUDGET when under actual budget

Default DAILY_LIMIT is $10.00. Configure your actual limit in script: DAILY_LIMIT=25.00 (for $25/day budget) or export DAILY_USAGE_LIMIT=25.00. Verify limit calculation: usage_percentage = (updated_usage * 100) / DAILY_LIMIT. Check usage file value matches expected spending: cat ~/.claude-code-usage/daily-$(date +%Y-%m-%d).usage.

Usage not resetting at midnight

Script uses date-based filenames: daily-YYYY-MM-DD.usage. Each new day creates new file automatically. Old files remain for history. Check current file: ls ~/.claude-code-usage/daily-*.usage. If date command timezone incorrect, reset may occur at wrong time. Verify: date +%Y-%m-%d. Check system timezone: timedatectl (Linux) or systemsetup -gettimezone (macOS).

Pacing indicator showing incorrect ahead/below pace status

Pacing compares actual usage % vs expected % based on hours elapsed. Formula: expected = (24 - hours_remaining) * 100 / 24. At noon (12 hours), expected is 50%. If actual usage is 40%, shows 'below pace'. Adjust logic if you have non-24-hour daily windows. Verify current_hour calculation: date +%H. Check hours_remaining calculation: hours_remaining=$((24 - current_hour)).

Remaining budget showing negative or incorrect values

Remaining = DAILY_LIMIT - updated_usage. If negative, script displays '$0.00 left' and OVER BUDGET status. Verify DAILY_LIMIT setting matches your actual budget. Check updated_usage calculation: cat ~/.claude-code-usage/daily-$(date +%Y-%m-%d).usage. bc arithmetic: echo '$DAILY_LIMIT - $updated_usage' | bc. Ensure bc is working: echo '10.00 - 4.50' | bc (should return 5.50).

Multiple sessions causing duplicate cost additions

Script adds session_cost every update - can over-count if same session updates multiple times. For accuracy, track by unique session_id and update (don't add) session totals. Use enhanced version with session deduplication. Alternative: integrate with official usage API if available. Current implementation optimized for real-time awareness, not perfect accounting. Check session_id exists: echo '$input' | jq .session_id.

Progress bar showing all filled or all empty incorrectly

Verify usage_percentage calculation: usage_percentage=$(echo "scale=1; ($updated_usage * 100) / $DAILY_LIMIT" | bc). Check bar_filled calculation: bar_filled=$((usage_percentage_int / 5)) (each char = 5%). Test: usage=50%; bar_filled=$((50 / 5)); echo $bar_filled (should be 10). Verify Unicode block characters work: echo '█░'.

Usage file not being created or permission denied

Check home directory writable: touch ~/test && rm ~/test. Verify ~/.claude-code-usage directory exists: mkdir -p ~/.claude-code-usage. Check directory permissions: ls -ld ~/.claude-code-usage. Ensure script has permission to create files: touch ~/.claude-code-usage/test && rm ~/.claude-code-usage/test. Check disk space: df -h ~.

Source citations

Add this badge to your README

Show that Daily Usage Percentage Tracker - Statuslines is listed on HeyClaude. Paste this Markdown into your README — it renders the badge and links back to this page.

Listed on HeyClaude
[![Listed on HeyClaude](https://heyclau.de/badge/statuslines/daily-usage-percentage-tracker.svg)](https://heyclau.de/entry/statuslines/daily-usage-percentage-tracker)

How it compares

Daily Usage Percentage Tracker - Statuslines side by side with 3 alternatives on trust, install, platform support, and disclosed safety notes — all from reviewed registry metadata.

Field

Claude Code daily usage quota tracker showing percentage of daily limit consumed with visual progress bar, time remaining, and budget pacing indicators.

Open dossier

A Claude Code statusline script (bash) that reads cost.total_duration_ms from the statusline JSON on stdin via jq, converts it to elapsed minutes, and renders a 20-character progress bar, a percent-used figure, and a countdown against a 300-minute (5-hour) ceiling, with green/yellow/red ANSI color coding at the 50%.

Open dossier

Claude 5-hour conversation block tracker with visual countdown, expiration warnings, and color-coded indicators to prevent unexpected session terminations.

Open dossier

Multi-provider AI performance dashboard with context occupancy tracking, truncation warnings, TTFT latency, tokens/min rate, and model comparison metrics.

Open dossier
Next steps
Trust
Review statusReviewedMaintainer reviewedReviewedMaintainer reviewedReviewedMaintainer reviewedReviewedMaintainer reviewed
Package trustPackage not verifiedPackage not verifiedPackage not verifiedPackage not verified
Source provenanceSource-backedSource-backedSource-backedSource-backed
Submitter
Install riskReview firstReview firstReview firstReview first
Notes Safety Privacy Safety Privacy Safety Privacy Safety Privacy
Brand
Categorystatuslinesstatuslinesstatuslinesstatuslines
Sourcesource-backedsource-backedsource-backedsource-backed
AuthorJSONboredJSONboredJSONboredJSONbored
Added2025-10-252025-10-252025-10-232025-10-23
Platforms
Claude Code
Claude Code
Claude Code
Claude Code
Source repo
Safety notesRuns as a Claude Code statusline command on every refresh and depends on the local shell environment; a failure only affects status rendering, not your session.The installation example runs package-manager commands with elevated privileges (brew install jq, sudo apt-get/yum install jq) and writes an executable script plus statusLine config into .claude/. Review it before running. The installation example overwrites the statusLine key in .claude/settings.json (via a jq rewrite and mv), which replaces any existing statusline configuration. The statusline command executes on every refresh (refreshInterval 1000ms) and shells out to jq and seq each time.Runs as a Claude Code statusline command on every refresh and depends on the local shell environment; a failure only affects status rendering, not your session.Runs as a Claude Code statusline command on every refresh and depends on the local shell environment; a failure only affects status rendering, not your session.
Privacy notesReads the Claude Code statusline JSON from stdin (model, workspace path, token usage) and renders it in the local terminal; it does not send data off-machine.The enhanced example writes per-session timestamp files keyed by session_id into ~/.claude-code-windows on local disk; these persist until manually deleted. The script parses the statusline JSON Claude Code passes on stdin (session_id, cost.total_duration_ms); it stays local and makes no network calls.Reads the Claude Code statusline JSON from stdin (model, workspace path, token usage) and renders it in the local terminal; it does not send data off-machine.Reads the Claude Code statusline JSON from stdin (model, token usage, context occupancy) and renders it in the local terminal; it does not send data off-machine.
Prerequisites
  • Claude Code CLI installed and configured
  • Bash shell available (bash 4.0+ recommended for arithmetic operations)
  • jq command-line JSON processor (jq 1.6+ recommended for safe extraction with // defaults)
  • bc calculator (bc 1.07+ required for floating point calculations - script will fail without bc)
  • Claude Code CLI installed and configured
  • Bash shell available (bash 4.0+ recommended for arithmetic operations)
  • jq command-line JSON processor (jq 1.6+ recommended for safe extraction with // defaults)
  • Terminal with ANSI color code support (256-color mode recommended for color-coded window indicators)
  • Claude Code CLI installed and configured
  • Bash shell available (bash 4.0+ recommended for arithmetic operations and C-style for loops)
  • jq command-line JSON processor (jq 1.6+ recommended for safe extraction with // defaults)
  • date command with epoch conversion support (macOS: -j flag, Linux: -d flag)
  • Claude Code CLI installed and configured
  • Bash shell available (bash 4.0+ recommended for arithmetic operations)
  • jq command-line JSON processor (jq 1.6+ recommended for safe extraction with // defaults)
  • date command with epoch conversion support (macOS: -j flag, Linux: -d flag)
Install
Config
{
  "statusLine": {
    "type": "command",
    "command": "$CLAUDE_PROJECT_DIR/.claude/statuslines/daily-usage-percentage-tracker.sh",
    "refreshInterval": 2000
  }
}
{
  "statusLine": {
    "type": "command",
    "command": "$CLAUDE_PROJECT_DIR/.claude/statuslines/five-hour-window-tracker.sh",
    "refreshInterval": 1000
  }
}
{
  "statusLine": {
    "type": "command",
    "command": "$CLAUDE_PROJECT_DIR/.claude/statuslines/block-timer-tracker.sh",
    "refreshInterval": 1000
  }
}
{
  "statusLine": {
    "type": "command",
    "command": "$CLAUDE_PROJECT_DIR/.claude/statuslines/ai-model-performance-dashboard.sh"
  }
}
Citations
ClaimUnclaimedUnclaimedUnclaimedUnclaimed
Open 4 picks in the interactive comparison tool

Signals

Loading live community signals…

More like this, weekly

A short, calm digest of reviewed Claude resources. Unsubscribe any time.