Learn how Cotonity snapshots every published version, compare diffs between any two versions, roll back to a stable release in seconds, and maintain clear release notes.
How versioning works
Every time you publish an agent, Cotonity creates an immutable snapshot of the entire agent graph — all nodes, their configurations, their connections, and their prompt text — and assigns it an incrementing version number (v1, v2, v3, …). The snapshot includes the metadata for every integration and secret reference (but not the secret values themselves). Versions are stored indefinitely on all paid plans; the Free plan retains the last 10 versions. You can view all versions in the Versions tab of the agent's overview page, each with a timestamp, the user who published it, and a release note you can add at publish time.
Comparing versions
Click Compare in the Versions tab to open a visual diff between any two versions. The diff highlights nodes that were added (green), removed (red), or modified (yellow). For modified nodes, you can expand the diff to see the exact field-level changes — useful for auditing what changed in a prompt or a configuration value. The diff view also shows changes to agent-level settings such as trigger configuration, error handler setup, and alert thresholds. Use version comparisons during incident investigation to quickly identify whether a recent publish coincides with a spike in errors.
Rolling back to a previous version
To roll back, open the Versions tab, find the version you want to restore, and click Promote to Live. Cotonity will immediately switch production traffic to the selected version — all new runs will use it within seconds. Runs already in flight at the moment of rollback continue to completion using the version they started with. The rollback itself is recorded as a new event in the version history, so you have a complete audit trail. After rolling back, investigate the issue with the problematic version in sandbox mode before attempting to re-publish a fixed version.
Release notes and change documentation
Make it a habit to write a brief release note when you publish a new version — even just one sentence describing what changed and why. Release notes appear in the Versions tab next to each version and in the audit log, making it much easier for your team (or future you) to understand the history of the agent without diffing every version pair. If your organization uses a change management process, the audit log is exportable as a CSV for inclusion in change tickets or compliance reports. You can also tag versions with labels like 'stable', 'experimental', or 'hotfix' for quick filtering.