Versions & candidates

Every agent keeps a history, so you can improve it without fear of losing what already works.

Draft vs. published

While you build, your agent is a private working draft — only you see it. When it's ready, you Publish it (the primary button at the top of the settings rail). Publishing makes the agent live and gives it a shareable link so other people can use it; the button then reads Published. You keep editing afterward — your in-progress edits don't touch the live version until you publish again, and re-publishing updates what users get.

Version history

The Versions surface keeps a timeline of your agent so you can move backward safely:

• Autosaves — the Builder snapshots your agent automatically as you work.
• Save version — capture a named checkpoint at any moment (for example, "before redesign").
• Restore — roll the agent back to any earlier version.
• Rename — give any version a clearer name.
• Pin — star important versions so they stand out.
• Open preview — view what a given version looked like, when a preview was built for it.

Candidates

Beyond the versions you save by hand, Donkit can generate a candidate — a proposed replacement configuration that is adopted only if it measurably beats the current one on your dataset. This is how the optimization loop improves an agent in a governed way: nothing goes live unless the numbers say it's better.

Automated candidate promotion runs through the Evaluate feature, which is plan-dependent and does not appear on every account.