Configure an agent

An agent configuration gives Gideon a role, operating instructions, and a set of capabilities. Use a specialist when a recurring kind of work deserves its own defaults.

Create the role

Open Agents and create an agent. Give it a name and a one-line description. Write a system prompt that states its responsibilities, boundaries, and how to report results. Keep Voice—tone and personality—separate from operating instructions.

Choose capabilities

Review the tools and skills attached to the agent. Set its approval mode deliberately. A specialized name does not make broad access necessary. Hosted model selection is managed; self-hosted agents can use the model controls available there.

Add routing hints

Specialty describes when the agent is the right fit. Routing hints are example requests that should suggest it. With specialist suggestions enabled in Chat settings, Gideon offers a routing chip rather than silently retargeting the chat. Leave specialty empty if you do not want suggestions.

Set context

Use Default directory for a workspace the runtime can access. An optional memory store can give the agent a named context. Check the resulting session’s workspace before assigning file changes.

Inspect and revise

Agent details show instructions, skills, tools, triggers, routing notes, and lifecycle hooks. Try the agent on a bounded real task before relying on automation. Change its instructions when the outcome reveals a specific problem.

For external agent CLIs and their restrictions, read runners and defaults.