Versioning and Rollback

almyty tracks versions of your agent pipelines, letting you save snapshots, compare changes, and roll back to a previous configuration.

In the UI

Saving a Version

1. Open the agent in the builder
2. Click the Versions tab in the agent detail header
3. Click Save Version
4. Enter a changelog describing what changed
5. Click Confirm — the snapshot is stored with an auto-incremented version number

Viewing Version History

1. Open the agent detail page
2. Click the Versions tab
3. The version list shows each snapshot with its version number, changelog, author, and timestamp

Rolling Back

1. Open the Versions tab
2. Find the version you want to restore
3. Click Rollback next to that version
4. Confirm the rollback — the agent’s pipeline is replaced with the snapshot
5. The rollback is recorded in the audit log as a separate event

Rolling back does not delete newer versions. You can roll forward to any later version at any time.

Via the API

Save a Version

curl -X POST /agents/{id}/versions \
  -H "Authorization: Bearer $TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "changelog": "Added error handling branch and retry logic"
  }'

Response:

{
  "success": true,
  "data": {
    "versionIndex": 3,
    "changelog": "Added error handling branch and retry logic",
    "createdAt": "2026-03-20T14:30:00Z",
    "pipeline": { "..." }
  }
}

List Versions

curl /agents/{id}/versions \
  -H "Authorization: Bearer $TOKEN"

Returns an array of version snapshots:

Roll Back

curl -X POST /agents/{id}/versions/{versionIndex}/rollback \
  -H "Authorization: Bearer $TOKEN"

Audit Log

Every agent change is recorded in the audit log:

curl /agents/{id}/audit-log \
  -H "Authorization: Bearer $TOKEN"

Each entry includes the timestamp, the user who performed the action, and relevant metadata.

Best Practices

1. Save versions before major changes — create a snapshot before restructuring the pipeline
2. Write meaningful changelogs — future you will thank present you
3. Test after rollback — verify the agent works correctly with the restored pipeline
4. Review the audit log — understand how an agent evolved over time