# Agent version history (/docs/api-reference/agent-versions)

> What agent version history is, how manual, auto-saved, and backup versions differ, and what happens when you restore one.

Version history keeps a snapshot of your agent's configuration every time you
save one, so you can go back to an earlier setup if a change doesn't work out.
The endpoints below list, save, compare, rename, delete, and restore versions.
See the [Agents](/docs/api-reference/agents/listAgentVersions) group for the
full request and response reference.

  
    Every time you save your agent, a version can be kept alongside it: a frozen
    copy of the configuration at that moment. You can look back at any saved
    version, compare it with what's running now, or bring it back.
  

  
    There are three kinds. A **named version** is one you saved yourself, usually
    right before trying something risky. An **auto-saved version** is captured
    automatically a few minutes after you stop editing, so there's always a recent
    point to fall back to even if you forget to save one. A **backup** is created
    automatically right before a restore, so restoring never throws away your
    current setup.
  

  
    Yes. A version is auto-saved a few minutes after you stop making changes, once
    the editing settles down. You don't need to save one yourself unless you want
    to name and keep a specific point.
  

  
    Yes. Restoring saves your current setup as a backup version first, so you can
    always undo a restore by restoring that backup.
  

  
    Restoring brings back the agent's configuration. If the version references a
    knowledge file or integration that was deleted since it was saved, that
    reference can't be reattached; the response reports it so you know what to
    reconnect by hand.