Manage agent definitions with /config-agents in Grok Build

/config-agents (alias /agents) opens the manager for agent definitions and personas. Official: Subagents, Modes and Commands.

Open the manager

1. Start or resume a Build session (grok or grok -c).
2. Run:

/config-agents

Or:

/agents

Use /personas when you only need the persona overlay list — see Manage personas in Grok Build.

Where agent types live

Built-in types stay available without custom files:

Type	Role
general-purpose	Default full-capability child
explore	Read, list, and search only — no shell, no edits
plan	Drafts an implementation plan — no shell, no edits

Add or override types as files under:

• Project: .grok/agents/
• User: ~/.grok/agents/

Personas (tone, focus, contracts) live under .grok/personas/*.toml, ~/.grok/personas/*.toml, or [subagents.personas] in user config. They do not add tools to explore or plan.

Turn subagents on or off

Mechanism	Example
Env	GROK_SUBAGENTS=1 (or 0 to disable)
User config	[subagents] enabled = true
Per-type	[subagents.toggle] map of type → bool
Per-type model	[subagents.models] map of type → model id

Leave [subagents] enabled unset to keep the docs default-on behavior. After edits, confirm discovery:

grok inspect

Child sessions and permission inheritance: Use Grok Build subagents. Parent ask / auto / always-approve still applies: Configure Grok Build permissions.

Pitfalls

• /config-agents manages definitions; it does not itself spawn a child turn. Spawn from the parent session or task tool after the type exists.
• Project .grok/config.toml only contributes MCP, plugins, and permission rules — put [subagents] and personas in user config or agent/persona files.
• Putting a persona on explore or plan never unlocks shell or edits.