Claudelike Bar — v0.9

Live status tiles for every Claude Code terminal. github.com/aes87/claudelike-bar · Open VSX

Status indicators

Waiting — amber blink (needs input, hasn't been seen)
Ignored — red slow pulse, dashed border (was waiting, you looked elsewhere)
Working — green pulse
Done — cyan static (parked, sinks to bottom of auto-sort)
Idle — no dot

Theme colors (left border)

Cyan
Green
Blue
Magenta
Yellow
Red
White (default)

Context window badge

ctx 22% Blue — under 60%
ctx 63% Amber — 60–79%
ctx 84% Red — 80%+
Mark as done
Clone terminal
🎨 Set color
Kill terminal

Right-click any tile NEW

Mark as done parks a session you're not working with right now. The tile sinks to the bottom of auto-sort, its dot goes quiet, and — critically — background Stop / Notification / PreToolUse events from that Claude won't re-surface it or trigger passive-aggressive judgement. It stays parked until you submit a new prompt in that terminal; the next UserPromptSubmit is the only thing that un-parks it.

Clone terminal spawns a fresh copy of the same profile (cwd, shell, args). Set color picks a per-terminal theme override — click a swatch, no file editing needed. Kill terminal disposes it entirely.

Drag & drop to reorder NEW

Grab any tile, drop it where you want. A blue rail shows the insertion point. The order is saved to .claudelike-bar.jsonc and survives window reloads.

⋮⋮ yeet-to-prod
⋮⋮ world-domination
⋮⋮ print-go-brrr

Sort modes NEW

Explicit sortMode switch. Auto floats "needs input" to the top. Manual respects your drag order. Dragging automatically flips the mode.

"auto"
"manual"

Auto-sort ranks by status: waiting → ignored → ready → working → done → idle. Manual uses per-terminal order values.

Auto-start terminals NEW

Mark projects with "autoStart": true and they spin up automatically on window open. Each terminal can have its own "command" to cd into the right directory and launch Claude.

Pair with VS Code's enablePersistentSessions and your Claude processes survive window reloads — no context loss.

Debug log

Flip "debug": true in the config. The extension streams hook events, state transitions, and auto-start decisions to a Claudelike Bar output channel. The hook and statusline scripts also write {os.tmpdir()}/claude-dashboard/debug.log. Useful when a tile seems stuck.

Windows / PowerShell support v0.9.2

Auto-start no longer assumes bash. CLAUDELIKE_BAR_NAME flows through VS Code's createTerminal({env}) API — cross-platform, no export noise. Per-terminal shellPath lets you pin git-bash (or pwsh, or cmd) when your command needs a specific shell.

Standalone statusline with backup + restore v0.9.2

Context % comes from a completely-independent statusline script. Installing it is opt-in — if you already have one, a modal shows both the command being overwritten and the one being installed before you confirm. Your prior statusline backs up to ~/.claude/.claudelike-bar-statusline-backup.json; a Restore Previous Statusline palette command (or Claude, via chat) puts it back.

Configure it by talking to Claude

The config file is .claudelike-bar.jsonc in your workspace root — JSON with comments, auto-created when you first open a terminal. You can edit it by hand, but the easier path is to just tell Claude Code what you want. After installing, open a Claude terminal and say: "Walk me through configuring the Claudelike Bar."

You
Switch to passive-aggressive mode and rename yeet-to-prod to "deploy".
Claude
Done. Two edits to .claudelike-bar.jsonc:
"mode": "chill", "mode": "passive-aggressive", "terminals": { "yeet-to-prod": { "color": "yellow", "nickname": null, "nickname": "deploy", "autoStart": true } }
The extension picked them up live — no reload needed.
You
Auto-start world-domination, print-go-brrr, brain-dump, and spore-drive. Each should cd into its project directory and launch Claude.
Claude
Four terminals configured with per-terminal command overrides:
"world-domination": { "autoStart": true, "command": "cd ~/projects/world-domination && claude" }, "print-go-brrr": { "autoStart": true, "command": "cd ~/projects/print-go-brrr && claude" }, ...
Next time you open VS Code, all four launch and run Claude automatically.
You
sourdough-ops needs different flags — it should run Claude with the MCP plugin.
Claude
Added a per-terminal command override:
"sourdough-ops": { "color": "green", "autoStart": true, "command": "cd ~/projects/sourdough-ops && claude --mcp-config mcp.json" }
You
Something's weird — print-go-brrr is stuck on "Working" forever. Can you figure out what's wrong?
Claude
Turning on debug logging:
"debug": false, "debug": true,
Open the Claudelike Bar output channel (Ctrl+Shift+U) and run a prompt in print-go-brrr — I'll watch for hook events and state transitions — if the hook never fires or the project name doesn't match the tile, we'll see it in the trace.

Everything you see in these conversations is plain JSONC in one file. Comments, section headers, and defaults are preserved by the extension's round-trip save — feel free to hand-edit. But most days it's easier to just ask.