Parallel tabs
Each tab is its own Claude Code process. Ctrl+T, Ctrl+W and Ctrl+Tab work like a browser.
⚡ Gets things done
Claude Code, with a crew.
The same official Claude Code you signed in to, with helper crabs, tabs that don't collide, undo for any turn and checks he runs himself. Nothing to migrate, nothing to give up.
4conversations side by side
Nways to try one task with /tries
0force-pushes, ever
1click to undo a whole turn
Helper crabs
Every subagent gets a crab.
When Claude sends out a subagent, it walks out of his shell as a helper crab: its own lane in the panel and its own crab on your desktop.
Helper crabs
Each subagent gets its own lane and its own crab. Click a helper on the desktop to jump to its conversation.
Your crew
Every agent type becomes a lasting crew member with a name, a hat and a record: runs, failures, tokens and findings Claude acted on. They level up and earn hats.
Crew view
Each lane shows its task, live activity, tool count, tokens and time. A helper's permission card shows up in its own lane, labelled with which crab is asking.
Your code, safe
Work in parallel without stepping on yourself.
A copy for each tab
A tab can move into a git worktree on its own branch the first time it changes a file. Bring it home merges it back, never with a force-push.
Clashes, spotted early
When two copies change the same file, both tabs get a ⚠ and he says so once, before you bring them home.
Undo any turn
Each turn ends with the files it changed. Undo puts them back, including what a script or npm install did, and never touches your staging area.
Undo to here
Every step that changes files gets a checkpoint, so you can roll back to just before any one of them.
Try again from any turn
Branch any message into a new tab with the files exactly as they were then. Run two approaches side by side and keep the one you like.
Try it N ways
/tries 3 fix the flaky login test sends the same task to three copies at once, runs each one's tests and ranks them.
Side by side
Split (Ctrl+\) puts up to four conversations on screen, or pops one out into its own window.
A review inbox
A tab that finished a turn with changes waits under Ready to review until you've looked.
He checks it himself
Green before it comes home.
Run checks on any turn runs the project's own tests (plus a typecheck or build if there is one) and stamps the verdict on that turn. Optionally after every turn, and before a copy comes home.
A verdict on every turn
✅ Checks passed · npm run test 12s, or ❌ 2 failing with their names. Works with npm,
cargo test,go testand pytest.Before and after pictures
With a dev server up, he photographs the page as the turn starts and again when it ends. Slide between them on the turn's changes.
Crit hits
Critical hit! when one turn takes a red suite to green; Clean landing when a copy comes home green on the first try. Never for skipping or deleting tests.
Correct Claude the same way twice in one project, and a card offers to make it a rule in that project's CLAUDE.md, in your own words.
Talk to it your way
Keyboard first. Voice too.
Comment on the diff
Click a line number (Shift+click for several) and say what should change. Comments collect across files and turns and go back as one follow-up.
Say it instead
Hold Ctrl+Alt+Space and say the task. Windows' offline recognizer hears it, on your PC.
Ctrl+K for everything
Stop, undo, rewind, try it another way, bring it home, compact, change mode, start the dev server, run a routine.
Queue and steer
Enter queues a message while he's busy, and Claude reads it at his next step, so you can change course mid-task.
Every slash command
All of Claude Code's own commands, each with what it does. Esc Esc, ! and @ work like the terminal.
While you were away
Back after an hour? A recap of what finished, what failed and what's waiting on you.
The Toolbox
Everything Claude Code can use, in one place.
Every skill, agent, command, MCP server, mod, hook, rule and CLAUDE.md, with an editor for each. Whatever you set up here works in your terminal too.
Skill Shop
Every plugin in your marketplaces, most popular first. Each install asks first in an isolated confirmation window.
Prompt snippets
Save what you ask for again and again, then type
/reviewor runshellby do @review.Mods
Claude Code mods with a switch each, saying in plain words what they can do.
Team packs
Save snippets, workflows, hooks and rules as
.shellby/team.json; anyone opening the repo can set up the same way.
Lean Shell
More out of your plan.
What every conversation carries
How many tokens a new conversation carries before your first word: Claude Code's prompt, every plugin's listings, your CLAUDE.md.
Plugins, priced
What each plugin adds to every conversation. Unused for 21 days? Marked idle, with a Turn off that's easy to undo.
What each turn cost
this turn: 18k tokens · ~3% of your 5-hour window · 41% of context.
A heads-up before a big one
"This usually takes about 20% and you've 12% left." Send anyway, or send after the reset.
Before it gets crowded
Past 60% full, he offers Compact or Start fresh with a summary while there's still room.
The prompt cache
A dot says whether this conversation's cache is warm, cooling or cold, and what that means for your next message.
Claude Code everywhere
In your terminal and editor too.
With the plugin he reacts to Claude Code in VS Code, Cursor, Windsurf, Zed, JetBrains and Windows Terminal, and sits in its status line. Continue in a terminal carries a conversation on with claude --resume, and /shellby:handoff brings one back.
$ /plugin marketplace add x-salmon/shellby $ /plugin install shellby@shellby # status line, right under the prompt: 🦀💨 Shellby working · Lv 5 Claw Coder ▰▰▰▱▱ · 🥵 GPU 84°C · +25 XP
And more
The small things that add up.
File links
src/x.js:42 in a reply opens in VS Code, Cursor or Windsurf at that line.
Open in VS Code
Any file's diff opens in VS Code's own side-by-side view, editable when the file is unchanged.
Push from the folder menu
Fetches, merges anything the remote has (never a rebase), then pushes. It never force-pushes.
Look over my changes
A read-only security read of work you haven't pushed, worst first. It changes nothing.
On your other computers
Work with Claude Code on a server or another PC over ssh. Claude Code doesn't even have to be on this PC.
Chats you can tick off
Mark a conversation done so the finished twenty stop burying the two you haven't.
Next
🗂️ Runs your dev day
Get Shellby. It's free.
Free for Windows 10 and 11. Bring your Claude Pro or Max plan, or just keep him for company.