If you're using Claude Code regularly, you've probably noticed the default CLI experience is pretty minimal. You get your conversation, but not much visibility into what's happening under the hood.
I wrote a small bash script that dramatically improves this by adding a rich statusline. Here's what mine looks like:
[Sonnet 4.5] Context: 0% | 5h: 8% → 3h22m | 7d: 6% → 5d23h | main
At a glance, I can see:
When you're orchestrating multiple AI conversations throughout the day, these details matter:
API limits - The 5-hour window resets on a rolling basis. Knowing I'm at 8% with 3h22m until reset helps me decide whether to continue a conversation or switch to a different model/account.
Context usage - When you're at 85% context, you know the next big feature request might blow the window. Time to start fresh or summarize.
Git branch awareness - I can't count how many times I've started work in Claude only to realize later I'm on the wrong branch. Now it's right there.
The script is a Claude Code statusline hook. You can grab it from my GitHub Gist.
Requirements:
jq (for JSON parsing) - install with brew install jqcurl (for API requests) - built into macOSgit (optional, for branch display) - built into macOSSetup steps:
~/.claude/statusline.shchmod +x ~/.claude/statusline.shThat's it! Claude Code automatically detects and runs ~/.claude/statusline.sh if it exists.
For more details on statusline hooks, see the official Claude Code documentation.
The script caches API usage data for 60 seconds to avoid rate limiting. Colors adjust automatically based on usage thresholds (green < 60%, yellow < 80%, red ≥ 80%).
The script does a few clever things:
It's about 230 lines of well-commented bash that just works.
If you're a casual Claude Code user who opens it once a week, probably not worth the setup.
But if you're like me—running multiple sessions daily, working across projects, orchestrating agent workflows—this little script has become indispensable. It's one of those quality-of-life improvements that seems minor until you try working without it.
Check out the full script on GitHub. Feel free to adapt it to your needs.
–Jeremy
Thanks for reading! I'd love to hear your thoughts.
Have questions, feedback, or just want to say hello? I always enjoy connecting with readers.
Get in TouchPublished on January 02, 2026 in tech