Claude Code tip: stop burning Opus 5.5 context on tasks Sonnet 5.5 can swarm, while Fable 5.1 sits idle spin up an autonomous team with --agent claude --agent architect Opus 5.5 acts as the lead architect, scoping the work and validating every worktree before it merges Sonnet 5.5 teammates... take isolated git worktrees and hammer out implementations at medium effort Fable 5.1 sits on the team as a dedicated adversary, only stepping in at three critical moments: → before a contract locks: does the frontend payload match the backend schema? → when a test breaks twice: are we patching the bug or just hiding the symptom? → before the merge: what attack surface or edge case did everyone overlook? Sonnet 5.5 builds. Fable 5.1 challenges. Opus 5.5 merges and ships Jev engineering runs the identical pattern one layer down: mechanical decisions that need no reasoning (which file to open, which tool to invoke, retry or abort) execute in 16ms, so the frontier models only wake up when execution paths actually diverge Plan on high. Delegate on medium. Keep the adversary on peer-to-peer call. - the full team setup > architect runs the main session on Opus 5.5 at high effort > teammate-ux builds client state inside its own git worktree > teammate-back writes endpoints and migrations inside a separate worktree > teammate-adv runs on Fable 5.1, read-only, and attacks every diff > teammates message each other by name without routing through the lead > tools: Agent(ux, backend, adversary) locks the architect to spawning only its own team paste the setup and this prompt into Claude Code below: "Configure my Claude Code workspace for an autonomous agent team: 1. Audit ~/.claude/agents and .claude/agents for definitions fitting architect, ux, backend and adversary > Generate definitions only for missing roles > Pin model: sonnet, effort: medium, isolation: worktree for ux and backend, and model: fable with read-only tools for adversary > Give architect model: opus, effort: high and tools: Agent(ux, backend, adversary) 2. Check ~/.claude/settings.json and my env: > Report CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS if it's set, since it turns named subagents into teammates without worktrees > Report CLAUDE_CODE_SUBAGENT_MODEL_FORCE and CLAUDE_CODE_EFFORT_LEVEL, which can override the pinned models and effort 3. Write each role's prompt so ux and backend own separate folders, message each other by name when a contract changes, and hand every diff to adversary before reporting back 4. Add a team rule to ~/.claude/CLAUDE.md: no worktree merges until adversary has reviewed it Show every configuration diff first. Do not apply edits until confirmed" save itshow more

Khairallah AL-Awady

78,761 subscribers

分享 下载