How It Works
The agent loads the named profile’s prompt and tools, then answers the user in that mode.Features
- Built-in Profiles - Pre-configured agents for common tasks
- Agent Modes - Primary, subagent, and all-context modes
- Custom Profiles - Register your own agent profiles
- Profile Discovery - List and filter available profiles
Built-in Profiles
| Profile | Mode | Description |
|---|---|---|
general | Primary | General-purpose coding assistant |
coder | All | Focused code implementation |
planner | Subagent | Task planning and decomposition |
reviewer | Subagent | Code review and quality |
explorer | Subagent | Codebase exploration |
debugger | Subagent | Debugging and troubleshooting |
Quick Start
Agent Modes
| Mode | Description |
|---|---|
PRIMARY | Main agent that can spawn subagents |
SUBAGENT | Spawned by another agent for specific tasks |
ALL | Can be used in any context |
API Reference
AgentProfile
Functions
Examples
Using Built-in Profiles
Custom Profile
Filter by Mode
Best Practices
Start with built-in profiles
Start with built-in profiles
Use
general, coder, or reviewer before authoring custom profiles — they already bundle sensible tools and temperature defaults.Match mode to role
Match mode to role
Reserve
SUBAGENT profiles for delegated tasks; use PRIMARY or ALL for agents that own the conversation.Keep custom profiles focused
Keep custom profiles focused
One clear purpose per profile (e.g. security audit, planning) keeps tool lists small and prompts easier to maintain.
Hide experimental profiles
Hide experimental profiles
Set
hidden=True on profiles still in development so they stay out of list_profiles() until ready.Related
Handoffs
Delegate work to subagents that can reuse profile presets.
Agent-Centric API
Consolidated feature flags and config objects on
Agent(...).
