Choose the right agent
Match the role to code changes, coordination, planning, or investigation.
Choose the role that produces the outcome you need. Agent pages bring together the conversations and work relevant to that role.
Read the visual explanation
Engineering works on code, Chief coordinates tasks, Product writes specifications, Oncall investigates bugs, Security reviews findings, and Code Intelligence analyzes code.
| Role | Use it for | Follow the work in |
|---|---|---|
| Engineering | Code changes, tests, maintenance, and implementation | Sessions |
| Chief | Coordinating tasks and delegating work across roles | Tasks |
| Product | Defining and revising the desired behavior | Specifications |
| Oncall | Investigating bugs and recording evidence | Bug reports |
| Security | Investigating security concerns and remediation | Security reports |
| Code Intelligence | Analyzing code, findings, and recommendations | Analysis reports |
Give the role a useful objective
Name the outcome and supply the source context. Engineering needs the behavior to change and relevant repositories. Product needs the problem, users, constraints, and decisions to resolve. An investigator needs symptoms, reproduction context, and evidence.
For example, ask Product to define filter behavior before asking Engineering to implement a search feature whose requirements are unsettled. Ask Oncall to reproduce an intermittent error before prescribing a speculative fix.
Follow delegation
A role may delegate work when its workflow supports it. Open linked child work to inspect the actual execution and results. The parent conversation provides coordination context, while the child can have its own questions and status.
See delegation and handoff. A role label does not expand repository access, model access, or workspace permissions.
Some navigation surfaces vary by release. The configured-agent sidebar is hidden, and paused product surfaces should not be treated as available just because an older link exists. Read feature availability.