Skip to main content
statuslinesSource-backedReview first Safety Privacy

Git Status Statusline - Statuslines

Git-focused statusline showing branch, dirty status, ahead/behind indicators, and stash count alongside Claude session info

by JSONbored·added 2025-10-01·
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://git-scm.com/docs/git-status, https://github.com/JSONbored/awesome-claude/blob/main/content/statuslines/git-status-statusline.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-01

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

3/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 & runtime2Network & hosting2General2

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 and string manipulation)
  • jq command-line JSON processor (jq 1.6+ recommended for safe extraction with // defaults)
  • Git installed and accessible in PATH (git 2.0+ recommended for symbolic-ref and rev-list commands)
  • Terminal with ANSI color code support (256-color mode recommended for color-coded git status indicators)
  • Terminal with Unicode character support (for ✓, ✗, ↑, ↓, ⚑ icons, or use ASCII alternatives)

Schema details

Install type
config
Reading time
2 min
Difficulty score
3
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

# Git-Focused Statusline for Claude Code
# Emphasizes git status with visual indicators

# Read JSON from stdin
read -r input

# Extract Claude session data
model=$(echo "$input" | jq -r '.model // "unknown"' | sed 's/claude-//')
tokens=$(echo "$input" | jq -r '.session.totalTokens // 0')
workdir=$(echo "$input" | jq -r '.workspace.path // "."')

# Get git information from workspace
cd "$workdir" 2>/dev/null || cd .

if git rev-parse --git-dir > /dev/null 2>&1; then
  # Get branch name
  branch=$(git symbolic-ref --short HEAD 2>/dev/null || echo "(detached)")
  
  # Check if working directory is clean
  if [ -z "$(git status --porcelain)" ]; then
    status_icon="✓"
    status_color="\033[32m"  # Green
  else
    status_icon="✗"
    status_color="\033[33m"  # Yellow
  fi
  
  # Check ahead/behind status
  ahead_behind=$(git rev-list --left-right --count HEAD...@{upstream} 2>/dev/null)
  if [ -n "$ahead_behind" ]; then
    ahead=$(echo "$ahead_behind" | cut -f1)
    behind=$(echo "$ahead_behind" | cut -f2)
    if [ "$ahead" -gt 0 ]; then
      tracking="↑$ahead"
    fi
    if [ "$behind" -gt 0 ]; then
      tracking="${tracking}↓$behind"
    fi
  fi
  
  # Check stash count
  stash_count=$(git stash list 2>/dev/null | wc -l | tr -d ' ')
  if [ "$stash_count" -gt 0 ]; then
    stash_info=" ⚑$stash_count"
  fi
  
  git_info=" ${status_color}${branch}${tracking}${stash_info} ${status_icon}\033[0m"
else
  git_info=""
fi

# Build statusline
echo -e "\033[36m${model}\033[0m │ \033[35m${tokens}\033[0m${git_info}"
Full copyable content
{
  "statusLine": {
    "type": "command",
    "command": "$CLAUDE_PROJECT_DIR/.claude/statuslines/git-status-statusline.sh",
    "refreshInterval": 1000
  }
}

About this resource

Features

  • Git branch name with 🌿 icon
  • Dirty working directory indicator (✗)
  • Ahead/behind remote branch tracking (↑↓)
  • Stash count display when stashes exist
  • Model and token count in compact format
  • Color-coded status (green=clean, yellow=dirty, red=conflict)
  • Graceful fallback when not in git repository
  • Commit count display for current branch

Use Cases

  • Active development with frequent git operations
  • Working across multiple branches simultaneously
  • Monitoring uncommitted changes during AI pair programming
  • Tracking sync status with remote repository
  • Quick visual feedback for git workflow state
  • Code review preparation with branch status awareness

Requirements

  • Claude Code CLI installed and configured
  • Bash shell available (bash 4.0+ recommended for arithmetic operations and string manipulation)
  • jq command-line JSON processor (jq 1.6+ recommended for safe extraction with // defaults)
  • Git installed and accessible in PATH (git 2.0+ recommended for symbolic-ref and rev-list commands)
  • Terminal with ANSI color code support (256-color mode recommended for color-coded git status indicators)
  • Terminal with Unicode character support (for ✓, ✗, ↑, ↓, ⚑ icons, or use ASCII alternatives)

Configuration

{
  "statusLine": {
    "type": "command",
    "command": "$CLAUDE_PROJECT_DIR/.claude/statuslines/git-status-statusline.sh",
    "refreshInterval": 1000
  }
}

Examples

Enhanced Git Status Statusline with Conflict Detection

Extended version detecting merge conflicts and showing conflict count

#!/usr/bin/env bash

# Enhanced Git Status Statusline with Conflict Detection

input=$(cat)

model=$(echo "$input" | jq -r '.model.display_name // .model.id // "unknown"' | sed 's/claude-//')
tokens=$(echo "$input" | jq -r '.cost.total_tokens // .session.totalTokens // 0')
workdir=$(echo "$input" | jq -r '.workspace.current_dir // .workspace.project_dir // "."')

cd "$workdir" 2>/dev/null || cd .

if git rev-parse --git-dir > /dev/null 2>&1; then
  branch=$(git symbolic-ref --short HEAD 2>/dev/null || echo "(detached)")

  # Check for merge conflicts
  conflict_count=$(git diff --name-only --diff-filter=U 2>/dev/null | wc -l | tr -d ' ')

  # Check working directory status
  if [ "$conflict_count" -gt 0 ]; then
    status_icon="⚠"
    status_color="\033[31m"  # Red for conflicts
  elif [ -z "$(git status --porcelain 2>/dev/null)" ]; then
    status_icon="✓"
    status_color="\033[32m"  # Green
  else
    status_icon="✗"
    status_color="\033[33m"  # Yellow
  fi

  ahead_behind=$(git rev-list --left-right --count HEAD...@{upstream} 2>/dev/null)
  tracking=""
  if [ -n "$ahead_behind" ]; then
    ahead=$(echo "$ahead_behind" | cut -f1)
    behind=$(echo "$ahead_behind" | cut -f2)
    if [ "$ahead" -gt 0 ]; then
      tracking="↑$ahead"
    fi
    if [ "$behind" -gt 0 ]; then
      tracking="${tracking}↓$behind"
    fi
  fi

  stash_count=$(git stash list 2>/dev/null | wc -l | tr -d ' ')
  stash_info=""
  if [ "$stash_count" -gt 0 ]; then
    stash_info=" ⚑$stash_count"
  fi

  conflict_info=""
  if [ "$conflict_count" -gt 0 ]; then
    conflict_info=" ⚠$conflict_count"
  fi

  git_info=" ${status_color}${branch}${tracking}${stash_info}${conflict_info} ${status_icon}\033[0m"
else
  git_info=""
fi

if [ "$tokens" -gt 1000 ]; then
  tokens_formatted=$(printf "%'d" $tokens 2>/dev/null || echo $tokens)
else
  tokens_formatted=$tokens
fi

echo -e "\033[36m${model}\033[0m │ \033[35m${tokens_formatted}\033[0m${git_info}"

Git Status Statusline with Remote Status

Version showing remote repository name and URL

#!/usr/bin/env bash

# Git Status Statusline with Remote Status

input=$(cat)

model=$(echo "$input" | jq -r '.model.display_name // .model.id // "unknown"' | sed 's/claude-//')
tokens=$(echo "$input" | jq -r '.cost.total_tokens // .session.totalTokens // 0')
workdir=$(echo "$input" | jq -r '.workspace.current_dir // .workspace.project_dir // "."')

cd "$workdir" 2>/dev/null || cd .

if git rev-parse --git-dir > /dev/null 2>&1; then
  branch=$(git symbolic-ref --short HEAD 2>/dev/null || echo "(detached)")

  # Get remote name
  remote=$(git config --get branch.${branch}.remote 2>/dev/null || echo "origin")
  remote_url=$(git config --get remote.${remote}.url 2>/dev/null | sed 's/.*\/\([^/]*\)\.git$/\1/')

  if [ -z "$(git status --porcelain 2>/dev/null)" ]; then
    status_icon="✓"
    status_color="\033[32m"
  else
    status_icon="✗"
    status_color="\033[33m"
  fi

  ahead_behind=$(git rev-list --left-right --count HEAD...@{upstream} 2>/dev/null)
  tracking=""
  if [ -n "$ahead_behind" ]; then
    ahead=$(echo "$ahead_behind" | cut -f1)
    behind=$(echo "$ahead_behind" | cut -f2)
    if [ "$ahead" -gt 0 ]; then
      tracking="↑$ahead"
    fi
    if [ "$behind" -gt 0 ]; then
      tracking="${tracking}↓$behind"
    fi
  fi

  stash_count=$(git stash list 2>/dev/null | wc -l | tr -d ' ')
  stash_info=""
  if [ "$stash_count" -gt 0 ]; then
    stash_info=" ⚑$stash_count"
  fi

  remote_info=""
  if [ -n "$remote_url" ]; then
    remote_info=" @${remote_url}"
  fi

  git_info=" ${status_color}${branch}${tracking}${stash_info}${remote_info} ${status_icon}\033[0m"
else
  git_info=""
fi

if [ "$tokens" -gt 1000 ]; then
  tokens_formatted=$(printf "%'d" $tokens 2>/dev/null || echo $tokens)
else
  tokens_formatted=$tokens
fi

echo -e "\033[36m${model}\033[0m │ \033[35m${tokens_formatted}\033[0m${git_info}"

Git Status Statusline Installation Example

Complete setup script with Git verification and Unicode character testing

#!/bin/bash
# Installation script for Git Status Statusline

# Check if Git is installed
if ! command -v git &> /dev/null; then
    echo "Error: Git is not installed or not in PATH"
    echo "Install Git: https://git-scm.com/downloads"
    exit 1
fi

# Check if jq is installed
if ! command -v jq &> /dev/null; then
    echo "Installing jq for JSON parsing..."
    if [[ "$OSTYPE" == "darwin"* ]]; then
        brew install jq
    elif [[ "$OSTYPE" == "linux-gnu"* ]]; then
        sudo apt-get install -y jq || sudo yum install -y jq
    else
        echo "Please install jq manually: https://stedolan.github.io/jq/"
    fi
fi

# Test Unicode characters
if echo -e '✓ ✗ ↑ ↓ ⚑' &> /dev/null; then
    echo "Unicode characters supported"
else
    echo "Warning: Unicode characters may not be supported in your terminal"
    echo "Consider installing a Nerd Font for better icon support"
fi

mkdir -p .claude/statuslines

cat > .claude/statuslines/git-status-statusline.sh << 'SCRIPT_EOF'
#!/usr/bin/env bash

# Git-Focused Statusline for Claude Code
# Emphasizes git status with visual indicators

read -r input

model=$(echo "$input" | jq -r '.model.display_name // .model.id // "unknown"' | sed 's/claude-//')
tokens=$(echo "$input" | jq -r '.cost.total_tokens // .session.totalTokens // 0')
workdir=$(echo "$input" | jq -r '.workspace.current_dir // .workspace.project_dir // "."')

cd "$workdir" 2>/dev/null || cd .

if git rev-parse --git-dir > /dev/null 2>&1; then
  branch=$(git symbolic-ref --short HEAD 2>/dev/null || echo "(detached)")

  if [ -z "$(git status --porcelain 2>/dev/null)" ]; then
    status_icon="✓"
    status_color="\033[32m"
  else
    status_icon="✗"
    status_color="\033[33m"
  fi

  ahead_behind=$(git rev-list --left-right --count HEAD...@{upstream} 2>/dev/null)
  tracking=""
  if [ -n "$ahead_behind" ]; then
    ahead=$(echo "$ahead_behind" | cut -f1)
    behind=$(echo "$ahead_behind" | cut -f2)
    if [ "$ahead" -gt 0 ]; then
      tracking="↑$ahead"
    fi
    if [ "$behind" -gt 0 ]; then
      tracking="${tracking}↓$behind"
    fi
  fi

  stash_count=$(git stash list 2>/dev/null | wc -l | tr -d ' ')
  stash_info=""
  if [ "$stash_count" -gt 0 ]; then
    stash_info=" ⚑$stash_count"
  fi

  git_info=" ${status_color}${branch}${tracking}${stash_info} ${status_icon}\033[0m"
else
  git_info=""
fi

if [ "$tokens" -gt 1000 ]; then
  tokens_formatted=$(printf "%'d" $tokens 2>/dev/null || echo $tokens)
else
  tokens_formatted=$tokens
fi

echo -e "\033[36m${model}\033[0m │ \033[35m${tokens_formatted}\033[0m${git_info}"
SCRIPT_EOF

chmod +x .claude/statuslines/git-status-statusline.sh

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

echo "Git Status Statusline installed successfully!"
echo "Note: Ensure you're in a Git repository for git status to display"
echo "Set upstream branch for ahead/behind tracking: git branch --set-upstream-to=origin/main main"

Troubleshooting

Git branch not showing or shows '(detached)'

Ensure you're on a proper branch: git checkout main. Detached HEAD state is normal when checking out specific commits. Verify branch exists: git branch. Check symbolic-ref command: git symbolic-ref --short HEAD. If in detached state, create new branch: git checkout -b new-branch-name.

Ahead/behind indicators (↑↓) not appearing

This requires an upstream branch to be set. Run: git branch --set-upstream-to=origin/main main (adjust branch name as needed). Verify upstream is set: git branch -vv. Check remote exists: git remote -v. Ensure remote branch exists: git ls-remote origin main. If remote doesn't exist, push branch first: git push -u origin main.

Status always shows dirty (✗) even after commit

Check git status for untracked files or changes. The statusline reflects actual git state. Run git status -s to see what's detected. Check for untracked files: git status --porcelain. Verify all changes are committed: git diff HEAD. Check for ignored files that might be tracked: git ls-files.

Unicode icons showing as boxes

Install a Nerd Font or ensure terminal has Unicode support. Test with: echo '✓ ✗ ↑ ↓ ⚑'. Check terminal encoding: locale charmap (should be UTF-8). Set terminal to UTF-8: export LANG=en_US.UTF-8. Install Nerd Font: https://www.nerdfonts.com/. If Unicode not supported, modify script to use ASCII alternatives: + for clean, * for dirty, ^ for ahead, v for behind.

Stash count not showing or incorrect

Verify stashes exist: git stash list. Check stash count calculation: git stash list | wc -l. Ensure git stash command works: git stash list 2>/dev/null. If stashes exist but not showing, check script logic for stash_count variable. Verify wc and tr commands are available: which wc tr.

Token count not displaying or showing 0

Check JSON input structure: echo '$input' | jq .. Verify cost.total_tokens exists: echo '$input' | jq .cost.total_tokens. Check alternative field: echo '$input' | jq .session.totalTokens. Verify jq is installed: which jq. Test with sample JSON: echo '{"cost":{"total_tokens":1234}}' | jq -r '.cost.total_tokens // 0' (should return 1234).

Model name not displaying correctly

Check JSON input: echo '$input' | jq .model. Verify model.display_name exists: echo '$input' | jq .model.display_name. Check alternative: echo '$input' | jq .model.id. Verify sed command works: echo 'claude-sonnet-4.5' | sed 's/claude-//' (should return sonnet-4.5). Check model field structure in Claude Code JSON output.

Git statusline not appearing when not in git repository

This is expected behavior - script gracefully handles non-git directories. Verify git repository check: git rev-parse --git-dir (should return .git path or error). If you want git info in non-git directories, modify script to show 'no-git' indicator. Check workspace path: echo '$input' | jq .workspace.current_dir.

Source citations

Add this badge to your README

Show that Git Status Statusline - 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/git-status-statusline.svg)](https://heyclau.de/entry/statuslines/git-status-statusline)

How it compares

Git Status Statusline - Statuslines side by side with 3 alternatives on trust, install, platform support, and disclosed safety notes — all from reviewed registry metadata.

Field

Git-focused statusline showing branch, dirty status, ahead/behind indicators, and stash count alongside Claude session info

Open dossier

Clean, performance-optimized statusline with Powerline glyphs showing model, directory, and token count

Open dossier

Comprehensive multi-line statusline displaying detailed session information across two lines with organized sections and visual separators

Open dossier

Starship-inspired powerline statusline with Nerd Font glyphs, modular segments, and Git integration for Claude Code

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-012025-10-012025-10-012025-10-16
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.Runs as a Claude Code statusline command on every refresh and depends on the local bash environment, jq, and a Powerline-patched font; 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.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.Reads the Claude Code statusline JSON from stdin (model, workspace path, token count) and renders it in the local terminal; it does not send data off-machine.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, 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 and string manipulation)
  • jq command-line JSON processor (jq 1.6+ recommended for safe extraction with // defaults)
  • Git installed and accessible in PATH (git 2.0+ recommended for symbolic-ref and rev-list commands)
  • Claude Code CLI installed and configured
  • Bash shell available (bash 4.0+ recommended for string manipulation and arithmetic operations)
  • jq command-line JSON processor (jq 1.6+ recommended for safe extraction with // defaults)
  • Terminal with 256-color support (xterm-256color or screen-256color recommended for proper color display)
  • Claude Code CLI installed and configured
  • Bash shell available (bash 4.0+ recommended for string manipulation and conditional logic)
  • jq command-line JSON processor (jq 1.6+ recommended for safe extraction with // defaults)
  • Terminal with UTF-8 encoding support (required for box drawing characters: ┌│└)
  • Claude Code CLI installed and configured
  • Bash shell available (bash 4.0+ recommended for pattern matching and string manipulation)
  • jq command-line JSON processor (jq 1.6+ recommended for safe extraction with // defaults)
  • Git command (optional, for git branch and status display - git 2.0+ recommended)
Install
Config
{
  "statusLine": {
    "type": "command",
    "command": "$CLAUDE_PROJECT_DIR/.claude/statuslines/git-status-statusline.sh",
    "refreshInterval": 1000
  }
}
{
  "statusLine": {
    "type": "command",
    "command": "$CLAUDE_PROJECT_DIR/.claude/statuslines/minimal-powerline.sh",
    "refreshInterval": 500
  }
}
{
  "statusLine": {
    "type": "command",
    "command": "$CLAUDE_PROJECT_DIR/.claude/statuslines/multi-line-statusline.sh",
    "refreshInterval": 1000
  }
}
{
  "statusLine": {
    "type": "command",
    "command": "$CLAUDE_PROJECT_DIR/.claude/statuslines/starship-powerline-theme.sh",
    "refreshInterval": 1000
  }
}
Citations
ClaimUnclaimedUnclaimedUnclaimedUnclaimed
Open 4 picks in the interactive comparison tool

Related guides

Signals

Loading live community signals…

More like this, weekly

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