Five sessions across three projects is a team to manage. Shabash reads your Claude Code history and git on your Mac and keeps track for you: what's in flight, what's stuck, where your time went, and what shipped, written up and ready to share.
Claude writes the code. You decide what matters, keep track of what's in flight, notice what stalled, and tell people what shipped. That used to be a product manager's job. Now it's yours, and by tomorrow the only record is a stack of terminal tabs you're scared to close.
Close your terminals at night. In the morning, Shabash shows every thread you left unfinished and what was still open. Check the ones that matter today and press Start. Each one opens in Claude Code, in the right folder, resuming the session where it stopped.
You decide what's important. Star a thread to keep it at the top until it's done.
Sessions become threads: the features, fixes and investigations they add up to. Each thread shows what's done, what stalled, and the loose ends nobody closed. Mark things done or archive them, and your calls stick when new work comes in.
Point Shabash at a project's spec, PRD or plan. It checks each section against the real threads of work: what's done, what's in progress, what nobody has touched, and what got built that isn't in the spec at all. No spec? You still get a week-by-week record of what actually got done.
Set each project's priority. Shabash measures hands-on time from your prompts and puts the two side by side, in plain numbers.
Claude Code deletes session transcripts after 30 days by default. Shabash keeps a compressed copy of every session you typed in, so a thread from last spring can still be resumed with its full history.
No account needed to see your own work, and nothing is uploaded to organize it.
~/.claude/history.jsonl, the prompts you typed~/.claude/projects, your session transcriptsgit log in each projectEvery prompt you type is in ~/.claude/history.jsonl. Full session transcripts are in ~/.claude/projects, one folder per project directory and one .jsonl file per session.
Claude Code deletes transcripts older than cleanupPeriodDays, which is 30 days by default. You can raise it in ~/.claude/settings.json. Shabash also keeps its own compressed copy of every session you typed in.
Run claude --resume with the session id from the folder the session started in. In Shabash you check a thread and press Start, and it opens the right session in the right folder.
Start opens your own Claude Code, signed in as you, exactly as if you had typed the command. Shabash's own writing runs on its own account with Anthropic and is included in the plan.
No. It writes a draft and you copy it where you want it. The sentence about why the work mattered is always yours.
Those skills help Claude manage your tasks: writing specs, tickets and plans. Shabash helps you manage Claude: it reads what your sessions actually did, across every project, and keeps the picture current without you writing anything down.
Shabash means "well done" in Hindi and Gujarati: what you say when someone finishes something. It also has a sha and a bash in it.
No. Shabash is an independent app that works with Claude Code. Claude Code is a product of Anthropic.
Shabash is in early access, with one monthly plan at launch. Join the waitlist and we'll email you when it's ready. Nothing else.