Using Jev to route decisions for a Claude Code multi-agent team

mercante @merccanteOriginally posted 2026.10.10

Open original on X

holy hell. Anthropic move for Claude Code: stop staffing agent teams with Opus and Sonnet 5.5 only when Haiku 5.5 can flood the peer bus at 340 tok/s stand the squad up with /teams claude --teammate-mode auto Opus 5.5 takes the architect chair, maps the system and signs the pull requests Sonnet 5.5 teammates each grab an isolated git worktree and grind the implementation on medium effort Haiku 5.5 rides the peer bus as scout and fuzzer, and only steps in at three gates: → before a contract seals: does the client payload still match the server schema? → when the same test dies twice: are we fixing the fault or painting over the symptom? → before anyone calls done: which race or attack path did the worktrees miss? Sonnet 5.5 writes. Haiku 5.5 swarms. Opus 5.5 stamps and ships Jev runs the same pattern one floor down: forks that need no thinker (which file to open, which tool to call, retry or abort) clear in 16ms, so the frontier models only wake when a path actually splits Plan on high. Hand off on medium. Leave Haiku 5.5 live on the P2P line. the team layout Opus 5.5 on high runs the room and folds the PRs teammate-ux builds client state inside its own git worktree teammate-back writes the endpoints and Redis atomic locks teammate-scout fuzzes invariants and walks the AST on Haiku 5.5 at 340 tok/s teammates talk straight over peer messages, no lead sitting in the middle tasks.json holds file mutexes so one worktree never steps on another paste the layout and this prompt into Claude Code: "Set my Claude Code workspace up for autonomous agent teams: Turn on experimental agent teams in ~/.claude/settings.json: Set CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS to 1 in the env block Set teammateMode to auto Pin the lead model: opus with effortLevel: high Check ~/.claude/agents and add teammate profiles for ux, backend, and scout: teammate-ux: model: sonnet, effort: medium, isolation: worktree teammate-back: model: sonnet, effort: medium, isolation: worktree teammate-scout: model: haiku, tools: Read, Grep, Glob, SendMessage Wire shared task coordination in ~/.claude/CLAUDE.md: Init tasks.json for dependencies and atomic file mutexes Let teammates settle contracts over peer messages without the lead in the loop Require a Haiku scout schema check before any teammate marks a task done Quality gate: Opus lead reads the synthesized worktree diffs and the test suites before the final merge Print every config diff first. Do not apply edits until I confirm"

This post quotes another post: x.com/merccante/status/2105040815537971408