Skip to main content

What are Agents?

Agents are intelligent orchestrators that coordinate multiple actions to complete complex tasks. Unlike traditional scripts, agents are declarative - you define what they should do through instructions, not imperative code.

Agent Parameters

Configure agent behavior with decorator parameters:

Parameter Details

string
required
Unique identifier for the agent. Use <verb>_agent naming pattern.
string
required
Human-readable name displayed in the dashboard and logs.
string
Description of what the agent does. Shown in dashboard and API docs.
string
required
System prompt that defines agent behavior. This is how you tell the agent what to do, which actions to call, and how to handle scenarios. This is the core of your agent - think of it as the agentโ€™s job description.
list[string]
required
List of action IDs this agent can use. Agent can only call actions specified here.
string
default:"gpt-4o-mini"
LLM model to use for AI-powered agents. Supported models:
  • gpt-4o-mini (default, fast and cheap)
  • gpt-4o (most capable)
  • gpt-4-turbo
  • claude-3-5-sonnet-20241022
  • claude-3-opus-20240229
int
default:"40"
Maximum number of actions the agent can call in a single run. Prevents infinite loops.

Building Agents

Minimal Agent

The simplest agent with just instructions:

Agent with Actions

An agent that uses actions to get work done:

Using Memory

Actions store data in memory, and your agent instructions can reference that data:
Learn more about Memory โ†’

Using Integrations

Agents can use actions that leverage built-in integrations:
View all integrations โ†’

Testing Agents

Test your agent locally before deploying:
This runs your agent in local mode with test data. Youโ€™ll see:
  • Agent execution flow
  • Actions being called
  • Memory operations
  • Integration calls (mocked locally)
  • Strategy execution
Expected output:

Deployment

Deploy your agent:
After deployment, invoke via:

Best Practices

Each agent should have a clear, single purpose.โœ… Good: Separate agents for different workflows
โŒ Bad: One agent doing everything
Agent IDs should follow <verb>_agent pattern and be clear.โœ… Good
  • support_agent
  • research_agent
  • booking_agent
โŒ Bad
  • agent1
  • my-agent
  • test
Your instructions are the core of your agent - make them detailed and specific.
Prevent runaway execution by setting reasonable limits.
Tell your agent how to use memory in the instructions.
Only list actions the agent actually needs.

Limitations

Current limitations:
  • Max execution time: 15 minutes per run
  • Max steps: Configurable, default 40
  • Declarative only: Agents use instructions, not imperative code
  • State in memory: All state must be stored in memory
  • No async actions: Parallel execution coming soon

Next Steps

Actions

Learn how to build powerful actions

Memory

Master memory operations

Strategies

Add manual approval and wait conditions

Deployment

Deploy and invoke your agents