Prompts
Versioning and lifecycle
Every change to a prompt creates a new version. The lifecycle controls when changes reach production. Diff view shows what changed; rollback restores any prior version.
What you'll learn
- The four version statuses and what each one permits
- How to create a new version of an existing prompt
- How to compare two versions with diff view
- How to roll back when a release regresses
Status lifecycle
- 1
Draft
Editable, isolated, not attachable to production agents. Every new version starts here. - 2
Active
Production-ready. Attachable. Becomes the default version that agents following the prompt without pinning will use. - 3
Deprecated
Existing attachments keep working. New attachments are blocked. Use this to signal a planned migration without breaking running agents. - 4
Archived
Immutable, read-only. Cannot be reactivated, edited, or attached. Available for audit and as a rollback source.
Create a new version
- 1
Open the prompt
Click the prompt in the library. The Versions tab shows every version with status, author, and timestamp. - 2
Click New Version
A new Draft is created, pre-populated with the content of the latest Active version. Version numbers follow semver — patch by default, bump major or minor on intentional behavior changes. - 3
Edit and preview
Iterate as you did when authoring. Use the diff view to see your changes against the previous version side-by-side. - 4
Activate
Click Activate when ready. The new version becomes Active. Agents following the prompt move over on their next run. The previous Active version moves to Deprecated automatically — unless you opt to keep both Active for a parallel rollout.
Diff view
Open any two versions side-by-side from the Versions tab. Additions, deletions, and re-ordered blocks are highlighted. Use the diff view in code review — paste a link in a pull request or change ticket so reviewers can verify the intent of a prompt change before activation.
Rollback
- 1
Identify the regression
Use Monitor and Eval to confirm the current Active version is performing worse than a prior one. - 2
Open the good version
Find the version you want to roll back to. It can be Active, Deprecated, or Archived. - 3
Click Roll back
A new Draft is created from that version's content. Review the diff against the current Active to make sure nothing else regresses. - 4
Activate the rollback
Promote the Draft to Active. The bad version moves to Deprecated. Attached agents pick up the rollback on their next run.
Frequently asked questions
- Can I pin an agent to a specific version?
- Yes. In the agent builder's Skill Selection step, choose Pin Version when attaching the prompt. The agent will stay on that version even when a newer one is activated. Useful for stability-critical agents that need an explicit migration step.
- What happens to agents attached to a Deprecated version?
- They keep running with no behavior change. Deprecated is a signal, not a block. The agent's detail page surfaces a warning and a one-click migrate-to-latest option.
- Can I un-archive a version?
- No. Archived is terminal — content is read-only and not attachable. To get the same content back, open the archived version, click Roll back, and activate the resulting Draft as a new version.
- How are version numbers assigned?
- Dezifi follows semver. Patch bumps for typo fixes and clarifications. Minor bumps for additive changes. Major bumps for breaking changes to behavior. You can override the suggested number when activating.