Claude Code agent teams use Jev as the script layer
Claude Code's Agent Teams split coding work across roles, while Jev handles mechanical actions like opening files and calling the CLI in 16ms without involving an LLM.
I don't understand why everyone isn't doing this yet. Anthropic released a guide for Claude that makes work much more efficient while burning a fraction of the tokens Main Idea: Agent Teams in Claude Code Instead of burning the expensive Opus 5.5 context on every line of code, tasks are delegated across an autonomous swarm: Architect (Opus 5.5, high effort): Plans the structure and handles final PR merges Developers (Sonnet 5.5, medium effort): Write code inside isolated git worktree environments (UI/UX, backend) Adversary / Critic (Fable 5.1): Steps in at contract boundaries, recurring test failures, and pre-PR audits to catch vulnerabilities Script Layer (Jev): Handles mechanical tasks (opening files, CLI invocations) in 16ms without involving LLMs Launch the team via terminal: claude --teammates ux,backend,adversary Configure my Claude Code workspace for autonomous agent teams: In ~/.claude/teams, generate missing roles: set workers to Sonnet (medium effort) in separate git worktree branches, and the adversary to Fable In ~/.claude/settings.json, set CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS=1 and lock the main session to effortLevel: high Initialize tasks.json with file-level locking for direct peer coordination In CLAUDE.md, add a rule requiring an adversary review before opening a PR. Show configuration diffs before applying edits > https://code.claude.com/docs/en/advisor
This post quotes another post: x.com/bober_smart/status/2078784709253841039