Agent types
| Type | Access |
|---|---|
| Private | Accessible only to the creator. Use for personal workflows and agents under active development. |
| Shared | Accessible to specific team members granted access by email. Collaborators can execute the agent but cannot modify its configuration. |
| Public | Accessible to all members of the organization. Discoverable in the agent library for standardized, reusable workflows. |
Agent definition
Every custom agent specifies four attributes:- Role: The professional function the agent adopts, such as
"Senior Python Developer"or"Security Auditor". This shapes how the agent frames its analysis. - Goal: The primary objective, defined with specific, measurable outcomes, such as
"Identify SQL injection vulnerabilities across all database query constructions". - Backstory: Professional context that informs decision-making. Include relevant methodology, standards, or principles the agent applies.
- System Prompt: High-level instructions that control execution behavior: output format, edge case handling, and quality standards.
Task configuration
Each agent contains between one and five tasks. A task defines a discrete action and consists of three components:- Description: A clear statement of what the task accomplishes, focused on outcomes. The system automatically enhances descriptions with step-by-step reasoning to improve execution quality.
- Tools: An array of tool IDs the agent can use. Each task requires at least one tool, selected from the library of 70+ options.
- Expected Output: A JSON object specifying the format and structure of the result.
Execution


