Using an agent

Keep separate setups of an agent, run it as a conversation or as single runs, see which version a setup runs, and manage what it remembers for you.

Each agent in My agents can have several setups. A setup keeps its own inputs, preferences, schedules, history and memory. Use separate setups for separate jobs, for example one per client.

Setups

Open an agent from My agents. The SETUP bar at the top of the Agent page shows the setup you are on. Pick another setup from it to switch. The bar says "Everything below is saved for this setup only."

Make a new setup

Click New setup on the setup bar, or on the agent's card in My agents. The new setup opens ("Making a new setup…"). A setup made now runs the version the Builder has published now.

Rename or delete a setup

Click Rename setup (the pencil) next to the setup's name, type the new name, and click Save or Cancel.
Click Delete setup (the bin), then Delete to confirm. Everything saved for the setup goes with it, and this can't be undone. The page then opens another setup of the agent, or My agents when it was the last one.

Conversation or Single run

On the Run tab, choose how to run at the right of the tabs.

Conversation

Conversation shows the action's runs as a chat: what each run was given, then what it gave back, under the time it finished. Each run reads the conversation so far (the latest exchanges in full and a summary of older ones) and adds its own exchange, so you can follow up on an earlier answer.

Before the first run, the inputs come one card at a time ("Let's set up your first run"). Click Next to go on, Back to go back, and Skip for an input you may leave empty. The last card's button runs the action.
After that, only the inputs asked each run come up in the bar under the conversation. The rest sit under Other inputs; click one to change it. When there is nothing to fill in, click Run: it uses your saved inputs.
While a run works, the bar shows its progress and Stop. A run you stop shows "You stopped this run." in the conversation, not as a failure.

Runs that a schedule, a webhook, an app event or a room started don't show in the conversation and don't read or add to it. Find them in History (a room's turns are also in the room).

Single run

Single run shows the inputs beside the result: What you give it, then What you get back. A single run stands alone: it doesn't read the conversation and adds nothing to it. It still appears in the conversation, marked "Single run", and in History.

When the Builder publishes a new version

A setup of a Store agent keeps running the version it was made from, so its results don't change under you. When the Builder releases a newer version, the Run tab says A newer version is out, with the version this setup runs and the new one. Click New setup to make a setup on the new version. Your other setups keep working as they are.

If the Builder changed the price, royalty or fees, the Run tab says The Builder changed the terms: this setup keeps what it was made with, and a new setup uses the new terms. When you make that new setup, the New setup dialog shows the new terms. Click Accept and make the setup, or pay the price difference first. See Agent Store.

Your memory in an agent

When an agent learns from your runs, each setup has its own memory, private to you. Open Settings and find Memory. A number on the Settings tab means things it learned are waiting for you.

When it learns something: shown when the Builder lets you choose. Ask me first waits for you to keep or discard each thing; Save automatically saves it right away.
Things waiting for you are listed as "new thing learned · keep or discard". Click Keep or Discard on each one.
The setup's memories, each marked "Learned from a run", "Added by you" or "From the Builder". Click Forget (the bin) to delete one of yours. Items from the Builder can't be changed. Click Show all to see every memory.
Documents: reference files the agent should always know, such as a style guide. Click Upload to add one, and the cross to remove one of yours.
Memory used shows how much of this setup's memory space is in use. A note appears when your memory across all your agents is nearly full.
Timeline lists every change you made to memory. Click Undo to reverse a change, and Redo to apply it again. Undo is for your own changes only: changes a run makes aren't listed. Changes are kept for 7 days (at most the last 25 changes), then removed. They count toward this setup's storage.

If Memory says "This agent doesn't keep memories. Each run starts fresh.", the Builder set the agent to remember nothing.

When the memory is full, new things aren't saved and you get a notice; runs keep working. See Memory.

Apps an agent uses

Apps and permissions in Settings lists the apps the agent uses. The agent uses your own account for each app. Connect each app marked Not connected before you run it.

If an administrator turns off one of the agent's app actions, its Builder is told. An app event that an administrator paused can't be switched back on from When it runs; the Builder needs to replace it in a new version.

Limits

Setups per agent: each setup counts as one conversation; you can have up to 10 conversations per agent.
Memory per setup: up to 50 MB.
Memory across all your workflows and agents: up to 200 MB.
Undoable memory changes: the last 25 changes, for 7 days.
Storage per setup (shared by what you upload and your Timeline): up to 50 MB.

Common problems

I can't make a new setup

The agent already has the most setups allowed. Delete one you no longer need with Delete setup, then click New setup.

My runs aren't remembered

Memory says the agent doesn't keep memories, or the memory is full. Free up space with Forget, or remove documents you no longer need.

A follow-up doesn't know the earlier answer

Only Conversation runs read the conversation. A Single run, and a run a schedule, webhook, app event or room started, stands alone.

Results changed after an update

A setup of a Store agent made from an older version keeps that version. A setup you make after the Builder publishes runs the new version. To stay on one version, keep using the setup you have.