---
title: "Agent versioning"
url: "/agents/versioning"
description: "Edit a draft while production keeps serving the last published version, with history and one-click rollback."
productArea: agents
audience: ["business-user", "admin"]
plan: growth
tags: ["agents", "versioning"]
lastReviewed: 2026-07-28
---

# Agent versioning (/agents/versioning)





By default every edit to an agent goes live the moment you save. Versioning separates the two:
your agent becomes a **draft** you can edit freely, while production keeps serving the last
**published version** until you publish again.

Versioning is opt-in per agent. Until you publish a first version, edits go live instantly as
before.

## Turning it on [#turning-it-on]

Open the agent → **Settings** → **Versioning** → **Publish first version**.

## Publishing changes [#publishing-changes]

When the draft differs from what is published, a banner appears on the agent page.

| Action      | What it does                                                              |
| ----------- | ------------------------------------------------------------------------- |
| **Publish** | Freezes the current draft as the new production version, live immediately |
| **Discard** | Throws away draft changes and restores the published version              |
| **History** | Lists past versions and restores any of them                              |

Publishing is idempotent — if nothing changed, KlicForge tells you it is already up to date
rather than creating a duplicate.

### What Discard restores [#what-discard-restores]

**Restored:** agent settings, model, skill/tool/knowledge selection, prompt files, widget
configuration.

**Not restored:** edits to shared skills, knowledge documents, connections, evaluation suites
and scheduled tasks. These are shared resources that live outside the agent's own configuration.

## Rollback [#rollback]

**Settings → Versioning → Version history** lists every published version, newest first.
**Restore** points production back at that version. Your draft is untouched.

Rollback is never blocked by an [evaluation publish gate](/evaluations) — it is the emergency
path, and every target was live at some point already.

## What a version captures [#what-a-version-captures]

A published version is a snapshot of the agent's full configuration: prompt files, model and
fallbacks, temperature and session settings, attached skills and tools, the knowledge source
list, guardrails and widget configuration.

Two things are deliberately **not** frozen:

* **Name, slug and status.** Renaming an agent or switching it to `inactive` still works while
  versioning is on, so the on/off switch never gets stuck behind a publish.
* **Knowledge index content.** Only the *list* of attached knowledge sources is versioned, not
  the documents themselves. Re-uploading or re-embedding a source changes retrieval for every
  version, including old ones.

<Callout type="warn">
  That second point matters when comparing evaluation runs: a rerun of an old snapshot uses today's
  knowledge content, not the content as it was when the snapshot was taken.
</Callout>

## Testing before publishing [#testing-before-publishing]

The agent's test chat has a **draft / published** toggle, so you can talk to your unpublished
draft and the live version side by side before deciding.

## Plan limits [#plan-limits]

| Plan       | Versioning | Versions kept per agent |
| ---------- | ---------- | ----------------------- |
| Starter    | —          | —                       |
| Startup    | —          | —                       |
| Growth     | ✓          | 5                       |
| Business   | ✓          | 20                      |
| Enterprise | ✓          | Unlimited               |

"Versions kept" is a **rollback window** — how many recent versions stay restorable. Publishing
a sixth version on Growth does not fail; the oldest simply drops out of the window.

## If you downgrade [#if-you-downgrade]

Downgrading below Growth does not change what customers see — the agent keeps serving its
published version.

What stops is publishing. Edits still save to the draft but cannot be promoted. Two ways
forward:

1. **Upgrade** back to Growth or above and carry on publishing.
2. **Turn versioning off** — production goes back to serving the live configuration and every
   edit takes effect immediately. Any unpublished draft changes go live at that moment. Version
   history is kept.

Turning versioning off is available on every plan.

## Related pages [#related-pages]

* [Agents overview](/agents)
* [Evaluations](/evaluations)
* [Plans and usage](/organization)