Custom Agents
Create, import, and export custom agents with system prompts and triggers.
Beyond the 237+ built-in agents, you can create your own custom agents tailored to your specific workflows, conventions, and tools.
Creating a Custom Agent
- Go to Agents view (
Cmd + 2) > Custom tab - Click New Agent (or Import Agent)
- Fill in the Agent Wizard form:
| Field | Description | Required |
|---|---|---|
| Name | Agent identifier (used internally) | Yes |
| Display Name | Name shown in the UI | Yes |
| Description | What this agent does | Yes |
| Target | Output format or tool the agent is optimized for | No |
| Domain | Area of expertise (backend, frontend, etc.) | No |
| System Prompt | Instructions that guide the agent's behavior | Yes |
| Trigger Keywords | Words in your input that auto-select this agent | No |
- Click Save Agent
System Prompt Best Practices
The system prompt is the most important part of a custom agent. It tells the LLM exactly how to behave.
Good Example
You are an expert React developer specializing in:
- TypeScript with strict mode
- Tailwind CSS for styling
- React Query for data fetching
When generating code:
- Always use functional components
- Include proper TypeScript types
- Add meaningful comments for complex logic
Bad Example
You are a helpful assistant that can do anything.
The more specific your system prompt, the better the agent's output. Include your preferred patterns, libraries, and coding conventions.
Agent Attachments
Agents can include file attachments for additional context:
- Edit your agent > scroll to Attachments section
- Click Add File
- Select a file (txt, md, json supported)
| Limit | Value |
|---|---|
| Max files per agent | 5 |
| Max size per file | 1 MB |
| Warning threshold | 50 KB (may affect token budget) |
Great for: Style guides, API specs, code templates, example outputs.
Importing and Exporting Agents
Exporting
- Go to Agents view > Custom tab
- Click Export on the agent card
- Save the
.jsonfile
What's exported: Name, description, domain, system prompt, trigger keywords, attachments.
What's NOT exported: Internal system configurations.
Importing
- Go to Agents view > Custom tab
- Click Import Agent
- Select the
.jsonfile - Review and confirm
Sharing with Your Team
- Export your custom agents
- Share via Git, Slack, email, or any file sharing
- Team members import the file
- Everyone has consistent agents
Tips for Agent Power Users
1. Create Domain-Specific Agents
Don't use generic agents. Create specialized ones:
my-react-frontend-- Your React conventionsmy-node-backend-- Your API patternsmy-aws-infra-- Your cloud setup
2. Use Trigger Keywords Wisely
Add keywords that match how you naturally speak:
Trigger Keywords:
- react
- component
- hook
- useState
- useEffect
- frontend
3. Add Negative Triggers
Prevent wrong matches by excluding terms:
Negative Triggers:
- backend
- server
- api
- database
4. Include Examples in Attachments
Attach example outputs so the agent learns your preferred style.
5. Test Before Relying
- Create sample inputs
- Run through the agent
- Check output quality
- Adjust system prompt as needed
Troubleshooting
Agent not appearing in suggestions
- Check if the agent is enabled (toggle is on)
- Verify trigger keywords match your input
- Check for conflicting negative triggers
- Try locking the agent manually
Agent output is wrong style
- Review and refine the system prompt
- Add more specific instructions
- Include examples in attachments
- Check the selected optimization profile -- it affects output structure
Custom agent lost
- Check Agents view > Custom tab
- Custom agents are stored locally and encrypted
- If system keyring is inaccessible, agents may not load -- restart the app
Smart Detection picks the wrong agent
- Lock the correct agent manually
- Adjust trigger keywords on your preferred agent
- Increase the auto-apply confidence threshold in Settings
- Disable Smart Detection for agents and select manually