Council agents

Council agents are designed for multi-perspective reasoning. The coordinator gathers perspectives from specialized members and synthesizes a single answer.

Use the Council when the task benefits from disagreement, trade-off analysis, or second-order thinking. For straightforward implementation, a primary agent or project/developer is usually faster.

Inventory

Agent	Default selector	Perspective
`council/coordinator`	`@handler/coordinator`	Orchestrates the Council and synthesizes the result.
`council/architect`	`@provider/gpt`	System design and structural reasoning.
`council/guardian`	`@provider/claude_opus`	Risk, safety, and critical review.
`council/pragmatist`	`@provider/glm`	Practical delivery trade-offs.
`council/sage`	`@provider/gemini_pro`	Broad synthesis and reflective analysis.
`council/visionary`	`@provider/kimi`	Alternative directions and future-facing ideas.

Model honesty

Council prompts receive the actual selected model names after configuration, fallback, and availability selection are resolved. This keeps each member’s self-identification aligned with the model currently behind that role instead of relying on hardcoded vendor claims.

Configuring Council models

The default Council member selectors reference provider pool names. Defining those pools is the easiest way to shape Council routing:

{
  "models": {
    "providers": {
      "gpt": ["<provider/model-architect>"],
      "claude_opus": ["<provider/model-guardian>"],
      "gemini_pro": ["<provider/model-sage>"],
      "kimi": ["<provider/model-visionary>"],
      "glm": ["<provider/model-pragmatist>"]
    }
  }
}

Use Model routing for the full selector syntax and fallback behavior.

On this page