Environments and releases
The Releases tab, release views and the artifact
Every release with its notes, digest and where it runs; compare any two or a release with the draft; download a release as JSON; and the read-only view of what Staging or Production runs, with its deployment history.
Reference3 min readUpdated 1 November 2026
An agent's Releases tab lists every release; clicking a Staging or Production pill in the environment bar shows what that environment runs, read only. Both are about releases, the promoted snapshots. Edit history is different: it lists the saved changes to the draft.
The Releases tab
| Column | What it shows |
|---|---|
| Version | v1, v2 and so on, newest first. The first row is the Draft: "Not released yet", "3 changes since v2" or "Same as v2" |
| Notes | The release notes typed when it was made, or No notes |
| Released by, Created | Who promoted from Development, and when |
| Digest | The first 12 characters of a SHA-256 of the snapshot. Two releases with the same digest hold the same configuration |
| Running in | Chips for the environments running it, or Nowhere |
| Actions | Compare with the draft, Download, and Promote to <next> when it can move on (off, with the reason, when it can't) |
The list holds the newest 200 releases.
Compare
Compare at the top opens a bar with two pickers: Draft (Development) and every release. It lists each field that differs, before and after, with the instructions as a line diff (long unchanged runs folded as "12 unchanged lines"), or says "v3 and Draft are the same." The compare button on a release row compares it with the draft. The same comparison appears in the promote dialog as What changes in <environment>.
Download the artifact
Download saves the release as a JSON file, <agent-name>-v3.json, with format: "sentientone.agent-release/v1", the agent's id and name, the version, digest, notes, when it was created and the snapshot itself, every release field. Keep it with your own change records or compare releases outside the app. It can't be uploaded back: releases are only ever made by promoting.
{ "format": "sentientone.agent-release/v1", "agent": { "id": "…", "name": "Northwind help desk" }, "version": 3, "digest": "9f2c1a7b4e0d", "notes": "Shorter answers; the new returns policy", "createdAt": "2026-11-01T09:15:00.000Z", "snapshot": { "system_prompt": "You are the support agent for …", "provider": "anthropic", "model": "claude-haiku-4-5", "temperature": 0.4, "max_tokens": 1024, "top_p": 1, "frequency_penalty": 0, "presence_penalty": 0, "output_type": "text", "tools": [], "guardrails": [], "rag_enabled": true, "chat_workflow_id": null, "rate_limit_rpm": 60 }}What an environment runs
Click Staging or Production in the environment bar. A banner says what it runs and since when, such as "Production runs v3, promoted 2 days ago by Maya.", and that releases can't be edited. Its buttons: Open Development (back to the editable tabs), Roll back and Download artifact. Below, the release's configuration in sections (Instructions; Model and parameters; Tools; Guardrails; Knowledge on or off; Chat workflow; Rate limit) and the environment's Deployment history: every promotion and rollback there, such as "v3 promoted (was v2)", "Rolled back to v2 from v3" and "v1, what it ran when environments were turned on", with who and when.
An environment with no release of the agent reads Not released to Staging yet, with Open Development and Promote to Staging.
Release notes
Typed in the promote dialog when a new release is made, up to 2,000 characters, and shown in the Releases tab, the release view and the rollback dialog. They can't be edited afterwards.
Can I edit a release?
No. Change the agent in Development and promote a new one, or roll the environment back to an earlier release.
Where is Versions now?
It's Edit history: the saved edits to the draft, with Restore this edit. Releases have their own tab.
Why do two releases have the same digest?
Their configuration is identical: the draft was promoted, changed and changed back. Either can run anywhere.
Still stuck?
Email us with what you tried and any request id. A person replies.