Skip to main content

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

1

Run a successful session

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

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
3

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.
4

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:
FieldTypeDefault
Team nameText”marketing”
Report typeText”weekly”
TopicText”social media metrics”
Time periodText”last week”
Each run fills in these fields and the super agent executes the same workflow with the new parameters.

Follow-up and refinement

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. You can:
  • View version history — see all versions with timestamps
  • Compare versions — understand what changed between iterations
  • Restore a previous version — roll back if a refinement didn’t work out
Version control is automatic. You never lose a working version when you iterate on an agent.

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.
Agent detail page with Files tab selected showing three reference files and an upload area

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

Sharing with your team

Agents are available to everyone in the workspace. Team members can:
  • Run the agent with their own inputs
  • View session history to see past results
  • Follow up to create their own refined version
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.