Panes

Plan-limit bars with burn rate and time-to-empty, session cost, cache hit ratio and tokens-per-turn sparkline.

A separate agent conversation in Claude Code's right-hand pane, forked from the current context.

A live typing speedometer above the prompt, a result card after each prompt (WPM, CPM, accuracy, personal bests) and a /typing stats pane

A Minecraft-inspired HUD for Claude Code: hearts for context, armor for safety nets, XP for verified work, and 60 advancements that persist across sessions

Sessions of this project, their worktrees and PRs, with check-ins, in a side pane.

Edit .env files in a pane inside Claude Code. Claude manages keys and asks you for values without ever seeing them.

Liquid-filled rings above the Claude Code prompt for the 5-hour and 7-day limit windows, context fill and prompt-cache lifetime, a fighter jet that shows the model's effort, and a pane of recent turns, their cost, their share of the 5-hour window and what filled it.

Keeps a brief of the session above the prompt: what it is for and where it stands; /brief adds what was done and decided, what waits on you, and what comes next

Autonomous optimize-measure-keep/discard loop: skill, run/log/stats tools, and a live experiment dashboard

Autonomous experiment loop for Claude Code: run, measure, keep or discard. A port of pi-autoresearch.

claude review: the session's latest reply in a calm reading pane docked beside the conversation, with its plan, question and tasks one key away

Obsidian Workspace — project-scoped vault productivity (capture / notes / PM). Skills own folder layout and templates; /obw:pm splits a spec into blocking tickets; /issue is a Claude Mod pane that lists a view of the project's dashboard, draws Mermaid as text diagrams, and can open a card in the browser through viz. Vault I/O uses the Obsidian CLI via the official obsidian-cli skill.

btop-style live dashboard for Claude Code internals: /cctop opens it in a side pane, cctop-insights lets the session answer questions from its numbers

Read-only side chat: /aside opens a pane beside the transcript where you ask about the session so far; answers come from a tool-less fork of the session's own transcript and nothing is written back into the main thread.

Play Word Exchange Plaza's levels as a text game beside Claude while it works

/explain: get answers as ASD-STE100 prose, a diagram, an HTML page, or a 3b1b-style video

Claude Clubhouse: a toolbar above the prompt, rooms for usage, agents, commands, tool rules and colors, and whole-window themes on macOS

Turns xcodebuild and swift build output into a live pane of errors grouped by file, and hands Claude the diagnostics instead of the raw log.

Buttons above the prompt: retell recent turns in plain words, or open what a background check flagged that you might miss. Results go to Claude Code's own pane; nothing enters the transcript or the model's context.

A pixel-art monster in a side pane that eats tokens and shows context, limits and activity at a glance

Guided modernization for any legacy codebase: start with /modernize, get an assessment, an interactive map, the business rules mined from the code, and a plan you approve, then an upgrade, a rewrite or a rebuild with independent proof that the new code behaves like the old. Includes security hardening, a one-page report, specialist agents, and an optional live progress pane (early access).

Painel ao lado da conversa com agentes, diffs como no VS Code, contexto, turnos com os comandos, árvore de arquivos ao vivo e inventário de plugins, e uma linha de resumo colorida acima do prompt. Só observa.

A pane counting this repo's open GitHub issues, coloured by issue type and by who they are assigned to

Toolbox for Claude Code's Workflow tool — author deterministic multi-agent workflow scripts (workflow-composer, with the @workflow-toolbox compile-time pattern toolkit as its standard library), scaffold a build-clean workflow skeleton from a spec (toolkit-scaffold), diagnose a failed run from its journal and decide whether resumeFromRunId helps (workflow-debugger), re-verify the runtime...