Agents

Overview

An agent is a reusable workflow the super agent builds from a successful chat session. Instead of re-prompting the same task every time, you save it as an agent that anyone on your team can run with different inputs.

Agents listing page with agent cards showing names, descriptions, and version counts

Creating an agent

Run a successful session

Use the chat to accomplish a task — generate a report, build an HTML page, analyze data, or anything else.

Click Create Agent

When you’re happy with the result, click the Create Agent button in the chat input bar. The super agent analyzes the session and extracts the workflow.

Chat thread with a completed response and the Create Agent button visible in the input bar

Configure the agent

A dialog appears where you can set the output format and provide optional instructions for how the agent should behave:

Create agent dialog showing Dashboard selected as output format with Recommended badge, plus Markdown and Html options

Output format — choose from:
- Dashboard (recommended) — the agent renders a visual dashboard with KPI cards, charts, and tables inline in every session. A sample dashboard is generated during creation and reused as the layout template for future runs.
- Markdown — traditional text-based output saved as an artifact
- Html — interactive HTML page preview in the artifact panel
Instructions — optional guidance for how the agent should execute (e.g., “focus on revenue growth metrics”)

Click Start building to create the agent.

Save and share

The agent appears in your workspace’s Agents section, ready for anyone to run.

Running an agent

Open the Agents page from the sidebar and click an agent to run it. Each agent has:

Input form — structured fields (text, dropdowns, file uploads) that parameterize the run
Run button — execute the agent with the provided inputs
Session history — view previous runs and their outputs

Input forms

The super agent automatically generates input fields based on the original prompt. For example, if the original session was:

Generate a weekly report for the marketing team covering social media metrics from last week

The agent might have input fields like:

Field	Type	Default
Team name	Text	”marketing”
Report type	Text	”weekly”
Topic	Text	”social media metrics”
Time period	Text	”last week”

Each run fills in these fields and the super agent executes the same workflow with the new parameters. After creating an agent, you can refine it by sending follow-up messages in the chat:

Update the report to also include email campaign performance and format the output as a PDF

Each follow-up creates a new version of the agent. The previous version is preserved.

Version control

Every modification to an agent creates a new version automatically. Each version captures the full agent configuration — input fields, output format, execution instructions, and attached files — so you always have a snapshot of what worked. You can:

View version history — see all versions with timestamps and who made the change
Read release notes — the super agent summarizes what changed in each version so you can review before adopting
Publish a version — mark a version as ready to distribute to your team or the community
Restore a previous version — roll back if a refinement didn’t work out; restoring creates a new version so nothing is lost
Download any version — export a specific version as a ZIP bundle for backup or transfer
Pull source updates — when an upstream source agent publishes a new version, you can pull the latest changes into your copy

Version control is automatic. You never lose a working version when you iterate on an agent.

Version History dialog listing v3, v2, and v1 with published badges, dates, and release notes

Exporting and importing

Agents can be exported as ZIP bundles and imported into other accounts or organizations. Imported agents preserve version history metadata. In organization contexts, you can share an imported agent with your team during the import process.

Agent detail page

Each agent has a detail page showing:

Overview tab

Title and description
Created date and version count
Quick-run form

Files tab

The Files tab is a file manager for reference files attached to the agent. These are supplementary resources — templates, datasets, images, configuration files — that the agent can read during every run.

How files get attached

There are two ways files end up in an agent’s Files tab:

Automatic — when the super agent builds the agent, it can stage reference files during creation. For example, if the agent generates a report template or pulls in a dataset, those files are automatically attached to the agent.
Manual upload — open the Files tab and drag-and-drop files or click to browse. You can upload multiple files at once (up to 10 MB each, 50 files per agent).

How the agent uses files

When the agent runs, all attached files are mounted into the sandbox at predictable paths. The agent receives a manifest (app-files.json) that maps each file’s display name to its sandbox path, so it can read the files directly during execution. This is useful for workflows that need fixed reference material — for example:

A report generator that uses a branded HTML template
A data analyzer that reads a CSV dataset
A content writer that follows a style guide document

Managing files

Preview — click any file to open a preview overlay (images render inline; other types show content or download)
Delete — click the trash icon next to any file to remove it permanently
Upload more — the drag-and-drop area is always available at the bottom of the tab

Agent files are separate from the global Files page. They are scoped to a specific agent and mounted into the sandbox every time that agent runs.

Config tab

The config.yaml that defines the agent’s input form, output format, and memory settings
The skill.md that contains the agent’s execution instructions

Sessions tab

History of all runs with inputs and outputs
Status (success, error) and timestamps
Links to the full chat thread for each run
Dashboards — if the agent produced a visual dashboard during the run, it appears in the expanded session card alongside the summary and artifacts

When an agent is created with the Dashboard output format, each run renders an interactive dashboard with KPI cards, charts, tables, and alerts. The dashboard layout is consistent across runs — only the data changes.

Stock analysis dashboard with current price, 52-week range, market cap, revenue, and price history chart rendered in an agent session

Personal agents live in your account by default. To make an agent available to your organization, use Convert to Team on the agent detail page. This moves the agent into the team workspace where all members can access it. Team members can:

Run the agent with their own inputs
View session history — see results from all team runs, including who triggered each one
Follow up to refine the agent and create new versions
Manage schedules — set up recurring runs on intervals or cron expressions

Organization agents show a team badge and are visible in the shared Agents listing. Access is role-based: all members can run agents, but only the creator can change the agent’s autonomy settings or delete it.

Write autonomy and approvals (Beta)

This feature is currently in beta testing. If you’d like early access, contact us at support@creao.ai.

When an agent connects to external services — email, social media, messaging, marketplaces — some actions can have real-world consequences. CREAO’s write autonomy system lets you control how these actions are handled.

Agent detail page with two pending approval cards showing Approve & Apply and Reject buttons, and the Autonomy section with Full auto mode toggle

How it works

Every tool call the agent makes to a connected service is classified as read, write, or destructive:

Read — fetching data, listing items, searching. These always run immediately.
Write — sending a message, creating a post, updating a profile. These require approval by default.
Destructive — deleting content, archiving channels, ending campaigns. These are blocked if validation fails.

Autonomy modes

Each agent has an autonomy setting you can toggle from the sidebar:

Approval required (default)
Full auto

When the agent wants to perform a write or destructive action, it pauses and shows an approval card in the chat. You can review the proposed action — including a preview of what will be sent — and either:

Approve & Apply — the action executes immediately
Reject — the action is cancelled and the agent is notified

If you send a follow-up message without approving, the pending approval is automatically superseded and the buttons are disabled.

Supported connectors

Write autonomy currently covers these connectors:

Connector	Write examples	Destructive examples
X (Twitter)	Post tweet, retweet, like	Delete tweet, unlike
Gmail	Send email, create draft	Delete email
Outlook	Send email, create contact	—
Slack	Send message, create channel	Delete message, archive channel
Discord	Send message	—
Telegram	Send message, forward message	Delete message
Reddit	Submit post, submit comment	—
YouTube	Upload video, create playlist	Delete playlist
Microsoft Teams	Send message, create channel	—
eBay	Create offer, publish listing	End campaign, delete campaign

Read-only tools (searching, listing, fetching) are never gated regardless of the autonomy setting.

Start with a working prototype in chat, save it as an agent, then iterate with follow-ups. Each refinement makes the agent more reliable and comprehensive.

Get Started

Features

Agent Brain

Pro

Community and Updates

Trust & Safety

Overview

Creating an agent