Panes

Runs 2-4 attempts at a task in parallel git worktrees, each with a different approach; compare their diffs and adopt the best.

Finds the commit that broke something: git bisect with your test command in a temporary worktree (your working tree is never touched), live progress in a pane, the culprit with its diff stat handed to Claude.

Gives Claude a screen to draw on: SVG diagrams and Markdown reports in a Canvas pane with history.

More than one mind: ask several models at once and get a synthesis, critique the last answer, and let Claude consult another model.

Look into CSV, TSV, JSON and JSON Lines files without dumping them into context: schema, stats, rows, filters, group counts and single-row lookups, exact and compact, streamed with caps; a /peek pane with column sparklines.

GitHub issues and pull requests in a pane — one press to have Claude work on an issue or review a PR — plus the current branch's PR checks in the status line.

An HTTP tool for API work: status, timing, trimmed headers and a body shaped to fit; localhost runs freely, other hosts ask once a session; an /http pane of the session's requests with replay and copy-as-curl.

A live plan Claude posts and keeps current: progress above the prompt, the full checklist and its history in a pane.

Search this project's past sessions: /recall for you (attach an old exchange to your next prompt), a tool for Claude to look up earlier decisions.

A compact, cached map of the repository for Claude: files by folder with sizes and each source file's symbols with line numbers, sized to a token budget, instead of reading files to get its bearings.

Works through a Markdown checklist item by item: one prompt per item, an optional check command, the box ticked when it passes.

Splits a task into independent parts, runs them as parallel subagents you launch and watch live, then hands their results back for integration.

Runs your dev server or watcher for the session, flags its errors above the prompt, and lets Claude read its output.

CI that fixes itself with your say-so: watches the branch's workflow run after a push, puts a failure with its error-dense log on the band with Fix it, surfaces new review comments, and can pre-review PRs you are asked to review.

The first session of your day starts with a briefing: what changed since you left, what waits on you, your work in flight, a first step and a standup draft.

Audits the project's dependencies once a day in the background (npm, pnpm, yarn, pip-audit, cargo audit) and flags high-severity vulnerabilities above the prompt, with details and a one-press safe upgrade by Claude.

Catches a broken dev environment before Claude trips on it: wrong Node/Python/Go versions, missing node_modules, .env gaps, merges or rebases in progress.

The things Claude told you to do yourself, never lost: captured from answers, kept per project, mirrored to .claude/follow-ups.md, one press to finish, snooze or hand back to Claude.

Notices when a session is getting heavy (full context, repeated compactions, slow turns, tool errors), prepares a handoff in the background, and offers a one-press fresh start that continues from it.

Claude gets better at your project without you writing rules: your corrections and the command errors Claude fixes become one-press lessons for CLAUDE.md.

Works your backlog while you are away: when idle, one worker at a time implements the next .claude/backlog.md task in its own git worktree under a strict tool policy and budget; in the morning you review, adopt or discard each branch.

Runs the tests related to each change (Claude's edits and yours) in the background; a failure caused by Claude's edit reaches Claude mid-turn, and the band offers Show and Fix it.

Say "this error", "the tests", "this file", "what you just did" or "the plan" and what it points at goes along with your prompt: the failing output, the test failures, the file, the diff, the plan. No model calls, size-capped, never twice, and Remove takes it back.

Keeps work flowing: when Claude stops mid-task ("Next I'll…") or asks an obvious yes ("Shall I continue?"), a 5-second countdown you can stop sends a short continue. Never for choices, missing info or risky steps.