Skip to main content
You can create agents for recurring tasks in addition to using the built-in assistant. Each agent has its own instructions, skills, files, integrations, and routines. A few examples:
  • A Stock Health Advisor that reviews inventory every morning and flags stockout and overstock risks.
  • A Weekly Channel Reviewer that writes a channel performance summary every Monday.
  • A Support Digest agent that reads yesterday’s tickets and summarizes the themes.

​
Create an agent

In the Agents section, click Create agent. Two ways to start:

Create with agent

Describe the task in a conversation. The agent asks for the information it needs, drafts its configuration, and lets you review it.

Configure manually

Skip the interview and fill in the configuration yourself.
Both options create the agent immediately. Select its name to rename it or change its icon.

​
Sessions and configuration

An agent’s page has two tabs. Sessions contains every conversation and scheduled run for the agent. Open a session to read it. You can also:
  • Select Ask agent to start a conversation.
  • Select Run now to run the agent from its instructions without entering a message.
Use Configuration to manage how the agent works.

​
Configuration

​
General

Manage the agent’s name, icon, default model, visibility, and owner.
  • Default model: The model the agent uses unless someone chooses another model in a conversation.
  • Visibility: Who can access the agent: only you, specific teams, or everyone in your organization. See Sharing agents and sessions before sharing an agent that uses private resources or connected accounts.
  • Owner: The person who can change the agent’s configuration and share it. To hand the agent to another member of your organization, select the Owner row and pick the new owner. Dema previews what moves with the agent, which connections the new owner needs to reconnect, and whether you lose access. See Transfer ownership.
Use Version history in the agent’s actions menu to browse past versions and restore one. Each version snapshots the agent’s files, so restoring an earlier version brings back the files that were attached at that time.

​
Instructions

Instructions describe the agent’s role, process, and expected output. Create with agent drafts them for you, and you can edit them after saving. A useful structure is Role for its purpose, Playbook for the steps it follows, and Output format for the result it should produce. Type / to reference a skill or app, or @ to reference an integration. This is the same as in the message box, so the agent recognizes the resource when it runs.
These instructions apply only to this agent. Put shared rules for language and formatting under Agents → Settings → Instructions. See the Overview.

​
Files

The agent’s shared files and memory. See Files and memory.

​
Skills

Add reusable workflows from your library or write a skill for this agent. See Skills.

​
Apps

View apps the agent created and apps linked from your library. See Apps.

​
Integrations

Connect services such as Slack, Shopify, or Gmail. Reuse an existing connection or authorize a new one, then set the allowed actions for each tool. Two ways to take an integration away:
  • Unlink removes it from this agent only.
  • Disconnect deletes the connection everywhere it’s used.

​
Tool permissions

When an agent asks to use a tool, you can approve it once, always approve it, or block it. Saved choices appear under Always approved, Manual approval, and Blocked at the bottom of the configuration page. You can reset any choice to its default.

​
Routines

A routine runs an agent automatically on a daily or weekly schedule. In the agent’s Configuration tab, find Routines and select Add routine. An agent can have more than one routine. Each routine can use a different schedule and optional instruction, and each run appears as a new session in the agent’s Sessions tab.
Create the routine from an app’s Updates tab when every run should update that app.