ServicesAI AutomationPortfolioContactBlogStoreWhatsApp Me

The Missing CLI for Claude Code: Meet cs

April 17, 2026

If you're using Claude Code, Anthropic's CLI for AI-assisted coding, you already know it's a game-changer. It's fast, it's agentic, and it lives where we do: in the terminal.

But if you're like me and use it dozens of times a day across multiple projects, you've likely hit a wall. Claude Code saves your history, but finding that specific refactoring session from three days ago — or resuming a complex debugging thread on your phone — can feel like finding a needle in a haystack.

To solve my own "session fatigue," I built 

cs
(Claude Sessions). It's a lightweight CLI tool designed to turn Claude's flat history file into a searchable, taggable, and organized library.

Why build a wrapper for a CLI?

Claude Code stores everything in 

~/.claude/history.jsonl
. It's great for the machine, but not exactly human-friendly when you have 100+ entries. I needed three things:

  1. Searchability: Find sessions by keywords.
  2. Organization: Tag "Work," "SideProject," or "Refactor" so I can filter out the noise.
  3. Resumability: A quick, numbered list where I can just type 
    cs r 3
    and get back to work.

How it works

cs
is a hybrid of Bash and Python. It's designed to be fast and zero-config.

  • The Parser: A Python script reads the 
    history.jsonl
    file provided by Claude Code.
  • The Tag Engine: Since I didn't want to mess with Claude's internal files, 
    cs
    maintains a separate, lightweight JSON file for your custom tags and bookmarks.
  • The UI: Everything is optimized for the terminal. It uses a compact, numbered list format that is especially phone-friendly if you're SSHing into your dev box or using Termux.

The workflow

Here is how 

cs
fits into a daily dev cycle:

1. The quick glance

Just run 

cs
to see your most recent sessions. No more guessing which session ID belongs to which project.

cs

2. Finding your place

Need to find that session where you were working on the API?

cs s "api fix"

3. Staying organized

Tag a session so you can find it later, or bookmark it for high-priority tasks.

cs t 1 "refactor"  # Adds the 'refactor' tag to session #1
cs b               # View all bookmarks

4. Seamless resuming

Once you find the session number, resuming is a single command. 

cs
handles the heavy lifting of passing the session ID back to Claude.

cs r 5

Mobile-first (sort of)

One of the unexpected benefits of 

cs
is how it performs on mobile. When I'm away from my desk and need to check a session via a phone terminal, I don't want to type long UUIDs. The numbered list (
1
, 
2
, 
3
...) makes it incredibly easy to navigate and resume threads with just a few taps.

Get started

If you're a heavy Claude Code user, give 

cs
a spin. It's open source and easy to install.

Check out the repo here: github.com/devdarren7/cs-claude-sessions

Happy coding (and session managing).

Want this set up for your team?

cs
is one small piece of how I run Claude across my own business and my clients'. The bigger wins come from memory, skills, hooks, and workflows tuned to the specific work your team does every day.

If you're paying for Claude but not sure you're getting your money's worth, I do a one-week Claude Ops Audit — fixed price, fixed deliverable, your team leaves with a setup built around your work, not a generic template.

R4,999 · 7 working days · three slots a month.

→ Book a Claude Ops Audit