Check and restore versions
New conversations use the latest published version of the context. Check which one is live, or bring back an earlier one.
Check what is live
Every publish creates a version that records its label, its publisher, and its Git commit when there is one.
In a git-managed project:
Which context version is live, and does it include our merged change?Commands: cassis status, or get_project_status over MCP: the merged commit should appear as latest_git_commit_sha. If publication failed, see Troubleshoot Git and publishing.
In an app-managed project:
Open Versions: the top entry is the published version, with its label and publisher.
To check a fix, ask its question in a new conversation: an existing conversation keeps the version it started on.
Restore an earlier version
Say active_customers changed answers its owner did not expect, and you want the version published just before it. Restoring rolls back the context, not warehouse data.
In a git-managed project:
Revert the commit that added active_customers on a new branch, run the checks and evals, and open a pull request.Commands: git revert <commit> on a new branch, then the checks and pull request of the Git workflow. The earlier context goes live once that merge publishes.
In an app-managed project:
In Versions, choose the version and select Restore. It replaces the unpublished context, pending edits included, and leaves the published version alone. Review Unpublished changes, run the eval cases, and publish: only then do new conversations get the earlier context.