Skip to main content
Every save that changes an agent’s configuration keeps its own version. Compare what changed against an earlier one, and revert when an edit makes things worse.
The version history dialog listing version chips and dates, with one version's Preview open showing how many lines reverting to it would change.

The version history dialog, with one version's prompt open for preview.

Open the history

1

Open it

Click the version chip beside the agent’s name, or open the actions menu and choose Version history.
2

Preview an older version

Click Preview on any version to read its prompt and see how many lines reverting would change.

Revert to an earlier version

Reverting does not delete anything. The old configuration is saved as a brand new version, so the history stays linear and nothing is lost.
1

Revert

Click the revert icon beside the version you want back.
2

Know what happens next

Every table column deployed from this agent picks up the reverted configuration the next time it runs.

Good to know

Only when the configuration actually changes. Saving with nothing changed, or only toggling a favourite, does not add one.
Yes, on their next run. A deployed column always reads whichever version is current, so a revert reaches every table using this agent.
Yes. A revert is just another version, so its own entry in the history can be reverted the same way.
Yes, the same as any other edit. The version chip beside the agent’s name moves forward as soon as you accept a revision.

Next steps

Train an agent

See where approved revisions come from.

Build an agent

Write the prompt this history is tracking.