kaivectorf

THIS IS AN ACTUAL F*CKING GOLD Anthropic just shared one of the best tricks for Claude Code. The idea: run Opus 5.5 and Sonnet 5.5 subagents at once, each one handling an independent piece of the same codebase-wide change. Parallel work and less clutter in the lead's context, because every task lands in its own worktree. You just launch Claude Code like this: claude --model opus here's the split: → Opus 5.5 runs the session, scopes the migration and reviews the plan → Sonnet 5.5 subagents apply the changes in parallel, each in a separate worktree → /batch maps the repo and proposes 5 to 30 independent units before spawning workers → you stop burning Opus 5.5 context on walking through every repetitive edit Opus 5.5 makes the big calls at three moments: → before a plan locks → when the same error shows up twice → before calling it done Sonnet 5.5 migrates. Worktrees isolate. Opus 5.5 reviews. /batch takes the same move one layer down: the changes spread across your repo (old API calls, import paths, JavaScript files) become independent units, and each worker implements and tests its piece in its own context the full tree > Opus 5.5 runs the main session and coordinates the migration > /batch researches the repo and presents the proposed units for approval > Sonnet 5.5 workers handle UI, API or test-file units that can change independently > each unit gets its own subagent and isolated worktree > each worker implements its change, runs tests and reports the result > Opus 5.5 reviews the collected diffs and checks compatibility before sign-off paste the tree and this prompt into Claude Code ↓ "Reconfigure my Claude Code setup around this tree: 1. Run the main session on Opus 5.5. Verify that Opus 5.5, Sonnet 5.5 and /batch are available in my setup. 2. Propose project-local env settings: CLAUDE_CODE_SUBAGENT_MODEL=sonnet and CLAUDE_CODE_SUBAGENT_MODEL_FORCE=1. Flag a restart and verify worker models through /tasks. 3. Prepare a /batch instruction for a concrete migration I choose. Split it into 5 to 30 independent units; keep shared configuration changes separate from the parallel work. 4. Add one rule to CLAUDE.md: use /batch for codebase-wide changes with independent units, keeping implementation and test output in worker contexts. 5. Confirm the committed base for the worktrees. Require plan approval before workers start, collect their local diffs and test results, and review compatibility before integration. No pushes or PRs without my permission. Show me every change as a diff first. No edits until I say go." ↳ code.claude.com/docs/en/comm… save it, it'll come in handy.