Claude Code multi-agent teams: Jev handles 16ms mechanical decisions
Using /teammates to assemble an Opus 5.5 lead, parallel Sonnet 5.5 workers and a Fable 5.1 adversary, Jev takes over decisions that need no reasoning, such as which file to open or which tool to invoke.
Claude Code official tip: once Opus 5.5 runs your main session, stop letting your secondary model quotas rot while burning expensive Opus context on grunt work Sonnet 5.5 can swarm in parallel spin up an autonomous team with /teams claude --teammates ux,backend,adversary Opus 5.5 acts as the lead architect, scoping architecture and validating pull requests Sonnet 5.5 teammates take isolated git worktrees and hammer out implementations at medium effort Fable 5.1 monitors the peer-to-peer bus 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 calling done: 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 > Opus 5.5 on high coordinates the session and synthesizes PRs > teammate-ux builds client state inside a separate git worktree > teammate-back writes endpoints and handles Redis atomic locks > teammate-adv runs invariant fuzzing and catches replay vulnerabilities > all teammates communicate directly over peer-to-peer messaging without coordinator drag > tasks.json manages file-level mutex locks so nobody steps on another worktree paste the setup and this prompt into Claude Code below: "Configure my Claude Code workspace for autonomous agent teams: 1. Audit ~/.claude/teams and .claude/teams for teammate profiles fitting ux, backend, and adversary > Generate definitions only for missing roles > Pin model: sonnet, effort: medium for workers, and model: fable for adversary > Assign each worker an isolated git worktree branch to eliminate file conflicts 2. Enable agent teams in ~/.claude/settings.json: > Set CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS=1 > Lock main session effortLevel to high 3. Initialize tasks.json in repo root with atomic file locking, allowing teammates to claim subtasks and resolve contracts directly over inter-agent messaging without coordinator intervention 4. Add a team rule to ~/.claude/CLAUDE.md: teammates must request an adversary security review before opening a pull request for the lead session Show every configuration diff first. Do not apply edits until confirmed" ↳ http://code.claude.com/docs/en/agent-teams
This post quotes another post: x.com/marfinxx/status/2103801809428955509