Roles
Give recurring agent assignments a clear purpose, model configuration, and scope.
Updated 2026-09-15
A role is a reusable agent configuration: what the agent is responsible for and how it should work. Use Settings → Agents to manage agent definitions used for delegation and routing. Provider authentication and permissions remain in Settings → Providers.
Write a role around a job, such as read-only investigation or focused implementation. Include the expected output and boundaries. Choose its model, effort, and supported Fast setting deliberately. A role name such as “reviewer” does not itself prevent file edits.
Worked example: a focused reviewer
Illustrative.
01 · Goal
Find correctness problems in one proposed change.
02 · Setup
Use a workspace with a small diff and a configured role whose provider is available. Give the reviewer no implementation ownership.
03 · Prompt
Review the current diff for correctness. Read the surrounding callers.
Do not edit files or start other agents. Report actionable findings with
file locations, a concrete failure scenario, and a suggested correction.
If you find no actionable issue, say so and list the limits of your review.04 · Evidence produced
Findings tied to the actual code, or an explicit statement of review coverage and limits.
05 · User review
Confirm each finding before assigning a fix. A clean review is not evidence that tests ran.