Edit a role for a narrow task
Configure a repository investigator that returns evidence without changing files.
Updated 2026-09-15
Use a narrow role when you repeatedly need the same kind of help. Keep provider choice separate from the assignment: select an available model in the role editor, then describe the work in the instructions.
Worked example: repository investigator
Illustrative.
01 · Goal
Locate the implementation behind a feature before planning an edit.
02 · Setup
Open Settings → Agents. Create or edit an agent definition, choose an available model, and set supported effort and Fast options. Use a repository you can inspect.
03 · Prompt
You investigate one repository question at a time.
Read repository instructions first. Trace real entry points and callers.
Do not edit, install dependencies, start servers, or delegate.
Return the answer, relevant file locations, and unresolved questions.
Distinguish directly observed behavior from your interpretation.04 · Evidence produced
For a task such as “Where is the workspace title determined?”, the investigator should return the responsible files and the conditions that select the title.
05 · User review
Open those locations and check the trace. Refine the role if its reports are too broad or omit relevant callers. Do not judge it only by the amount of text it produces.
Success is a reusable configuration with a clear assignment and a report you can verify. See Roles for the underlying model.