Skip to main content
Agents on HasteKit are versioned automatically. Every time you click Save, the current configuration becomes a new immutable snapshot. Old snapshots are kept forever and can be re-pointed to by an alias at any time.
Versions tab

​
How versions work

  • Version 0 = $LATEST — the mutable working copy. Every save on the Model / System Prompt / Tools / Skills / Memory / Handoffs / Output Schema / Connectors / Knowledge / Codebases / History tabs updates $LATEST.
  • Click “Create New Version” on the Versions tab to freeze the current $LATEST into a numbered snapshot (1, 2, 3, …). Future edits go back to $LATEST.
  • Numbered versions are immutable — once published they never change.

​
What versions enable

  • Stable references — clients call my_agent@5 or my_agent@production instead of “whatever’s in $LATEST right now.”
  • Safe rollouts — point a production alias at the new version; if it misbehaves, repoint the alias back. Clients don’t redeploy.
  • A/B testing — split traffic across two versions using a weighted alias.
  • Audit and rollback — every change is a discrete artifact you can review or re-activate.

​
What’s captured in a version

Everything on the agent except the General info (name, max iteration, runtime). Specifically: model and parameters, system prompt, output schema, history config, knowledge bases, codebases, memory service, tools, MCP servers, OpenAPI servers, connector actions, skills, and handoffs. Each version is fully self-contained — restoring an old version restores the exact tool catalog and prompts that were active at the time.