Eleven specialists, one coordinator

Complex work does not go to a single generalist model. A coordinator reads the request and delegates to the agent built for each part of it: an architect plans, a database specialist designs the schema, a staff reviewer reads the result. Each agent has its own prompt and can run on a different model.

When the team runs

The agent team is used for tasks the Builder classifies as complex, when it is switched on for your session and your plan's auto mode allows it. Simple and medium tasks go straight to one model; that is faster and cheaper, and the result is the same. The list below is generated from the same catalog the coordinator uses, so it cannot drift from what actually runs.

• Architect

  delegate_architect

  Plans the project structure and the implementation order before any file is written.

  Called: First, on complex build requests.

• Debugger

  delegate_debugger

  Reads errors and stack traces and finds the root cause.

  Called: When you report a bug, an error, or behaviour that does not match what you asked for.

• Frontend Specialist

  delegate_frontend_specialist

  Component structure, styling and accessibility.

  Called: UI work: layout, responsive behaviour, forms, accessibility questions.

• Refactoring Agent

  delegate_refactoring_agent

  Plans restructuring and deduplication without changing behaviour.

  Called: When code has grown messy and you ask to clean it up or reorganise it.

• Test Writer

  delegate_test_writer

  Plans test coverage, test files and cases.

  Called: When you ask for tests, or before a change that needs a safety net.

• Staff Reviewer

  delegate_staff_reviewer

  Reviews code the way a senior engineer would: correctness, security, maintainability.

  Called: When you ask for a review, or before a significant change lands.

• Code Simplifier

  delegate_code_simplifier

  Reduces complexity and duplication, improves readability.

  Called: When you ask to simplify or make code easier to read.

• Planner

  delegate_planner

  Produces a structured implementation plan and writes no code.

  Called: When you ask to plan, outline or design an approach first.

• Discuss

  delegate_discuss

  Explains concepts and trade-offs without touching files.

  Called: Conceptual or exploratory questions.

• Backend Architect

  delegate_backend_architect

  API routes, middleware, authentication, server-side error handling and API contracts.

  Called: Full-stack builds, alongside the Database Specialist.

• Database Specialist

  delegate_database_specialist

  Schema design, relationships, queries, migrations, indexing and seed data.

  Called: Full-stack builds and any data-model change.

  Uses a PostgreSQL-specific prompt on cloud projects.

Models

Tasks route to Anthropic, Google and OpenAI models depending on what each task needs. The auto mode picks the model per task, or you choose one yourself. Each agent's model can be set separately.