Agent Overview
Understand what agents are, how to create them, and how the agent detail page is organized.
Tip: Your agent already knows all of this. Just ask it — "What tabs do you have?", "What's your status?", or "Walk me through your capabilities."
What Is an Agent?
An agent is an autonomous AI worker that runs in its own isolated environment — a real Linux desktop with a browser, terminal, file system, and network access. Each agent has its own identity, skills, credentials, email address, and task queue.
Agents aren't chatbots that answer questions. They're digital workers that do things: browse the web, fill forms, write and run code, process files, send emails, extract data — anything a skilled human can do at a computer.
Creating an Agent
- Navigate to Agents in your project sidebar
- Click New Agent in the top-right corner
- Enter a name and optional description
- Click Create
You'll be taken to the agent detail page — the command center for everything related to this agent.
The Agent Detail Page
The agent detail page is organized into tabs, each covering a different aspect of the agent's capabilities:
| Tab | What It Does |
|---|---|
| Agent | Primary workspace — chat with your agent and watch it work on the live sandbox preview |
| Context | Attach skills, write custom instructions, and configure which tools the agent can use |
| View received and sent emails, configure email settings and whitelisted addresses | |
| Channels | Connect external messaging platforms (Telegram) so you can chat with your agent outside the dashboard |
| Files | Upload and manage files — both persistent storage and live sandbox files |
| Datasets | View, edit, filter, and export structured data tables the agent has created |
| Credentials | Store encrypted secrets (passwords, API keys, tokens) the agent can use without seeing |
| Queue | Manage the agent's task queue — add items, reorder, and configure processing |
| Schedule | Create time-based triggers that run the agent with a specific prompt on a schedule |
| Runs | View execution history, token usage, costs, and run details |
Agent Lifecycle
Agents move through distinct states:
Created → Onboarding → Sleeping ⇄ Awake → Running → Sleeping
Onboarding
When you first create an agent, it starts in onboarding mode. The agent introduces itself and walks you through setup conversationally — asking about its purpose, communication style, schedule, and email preferences. During onboarding, only the settings_manager and send_email tools are available.
You can skip onboarding at any time by saying "skip" or "let's go".
Sleeping
The agent's sandbox is shut down. No compute resources are used. The agent can still receive emails (which are queued), respond to Telegram messages (which auto-wake the sandbox), and you can configure its settings. Scheduled runs will automatically wake the agent when triggered.
Awake
The sandbox is provisioned and running. You can see the live desktop preview and chat with the agent. The agent can interact with its desktop, browse the web, run terminal commands, and use all its tools.
Running
The agent is actively executing a task — either from a chat message, a queue item, or a scheduled run. You can watch it work in real time on the desktop preview.
AI Model Selection
Each agent is powered by a language model that you can choose and change at any time. Click the model selector in the chat input area to switch between available models:
- Claude (Anthropic) — Excellent at computer use, reasoning, and following complex instructions
- GPT (OpenAI) — Strong general-purpose capabilities
- Other models — Additional models as they become available
Different models have different strengths, token costs, and speed profiles. The model selector shows cost indicators to help you choose.
What's Next?
- Chat & Sandbox — Learn how to interact with your agent and use the live desktop preview
- Channels — Connect Telegram for external messaging
- Context & Configuration — Set up skills, instructions, and tools
- Schedule — Create time-based triggers for automated agent runs
- Runs & Scheduling — Track execution history and configure queue processing