Agent lifecycle

An agent moves from an initial Main version through drafts and published versions, and can finally be archived.

Create, edit, and publish#

Creating an agent also creates its Main branch and initial immutable version. Editing creates or updates the current user's draft on the selected branch. Publishing turns the validated draft into another immutable version and advances that branch.

Only publishing Main updates the agent's active version. Previous versions remain in history so the configuration used at a point in time is not rewritten.

Duplicate an agent#

From the agent-list row menu, select Duplicate agent. The dashboard reads the source agent's active configuration, creates a new agent named <source name> (copy), and opens the new agent. The result gets its own agent ID, Main branch, and initial immutable version.

Duplicate copies only the active configuration and derives the new name. It does not copy the source agent ID, tags, archive state, branches, drafts, version history, or conversation history. A non-Main branch tip or an unpublished draft is not used.

Verify the result by checking the (copy) name, confirming that the URL contains a new agent ID, and comparing the important Agent Studio fields with the source active configuration. Then start a fresh Test Chat. If duplication reports a server error or stays on the list, search for the (copy) name before retrying so you do not create an extra duplicate after an uncertain response.

Copy agent JSON config#

From the same row menu, select Copy agent JSON config. The dashboard reads the active configuration and writes only that configuration as formatted JSON to the clipboard. It does not include the agent identity, tags, branches, drafts, version history, or conversation history.

On success, the dashboard shows Config for “<agent name>” copied. Paste into a trusted local editor and verify the expected top-level configuration fields. If loading the active configuration fails, the list shows the server error; reload and retry after the server condition is fixed.

Clipboard writing requires a secure HTTPS origin and site permission. If the browser blocks it, the dashboard shows Your browser blocked clipboard access. Allow clipboard access for this site, then try Copy agent JSON config again. Open the site from its secure HTTPS origin, grant clipboard permission for the site, and retry the same row action. There is no alternate dashboard JSON export control.

Archive behavior#

Archiving marks the agent as archived instead of deleting its row, versions, or conversation history. Archived agents are hidden from the normal agent list unless the archived filter is enabled.

An archived agent cannot be restored through the current UI or API. Treat archive as a one-way lifecycle action. There is no current delete-agent operation, and creating another agent does not revive the archived identity.

Before archiving#

1. Confirm that the selected agent is no longer needed.
2. Preserve any configuration details you need from its immutable history.
3. Check dependent operational flows before selecting Archive agent.
4. Enable the archived filter afterward to verify that the row is marked Archived.

Archive is different from discarding a draft. To release or resolve editable work, use draft and publish. For permanent workspace knowledge deletion, follow manage and delete, which has separate recursive behavior.