Preview and publish
Keep edits in a draft, preview and test them, publish a version to production, and roll back if needed.
An agent has one version in production and, at most, one draft. Your app only talks to the production version. When you save a change on the Assistant, Theme, Knowledge or Immersive mode pages, it goes to the draft. Nothing reaches your users until you publish.
Draft and production
| Draft | Production | |
|---|---|---|
| Who gets it | Nobody. Only you, in tests and the preview. | Every new session and new message. |
| Editable | Yes, by owners, admins and developers. | No. A version never changes once published. |
| How many | At most one per agent. | One live version, plus the history of earlier ones. |
Creating an agent publishes version 1 straight away, so a new agent works before you ever visit Deploy. Later edits go to the draft.
A turn that is already running finishes on the version it started with. The next turn uses the new one.
These settings are not versioned and apply at once: allowed domains, development mode, keys, the finish webhook and the list of required tests. The Deploy & access page says so above them.
Preview the draft
Press Preview in the bar above any agent page. A drawer opens with a sample of the assistant using the draft's settings: its name, modes, main language and direction, model and version ("Draft v3" or "Live v2"). With Immersive on, you see the immersive experience on a sample invoice. Otherwise you see a chat sample.
The preview is a sample. The conversation and record are fixed text: no model is called, nothing is billed and nothing is sent. To see how the draft really answers, run tests on it. See Evaluations.
Test the draft
Tests can run on the draft before you publish. A draft run keeps a copy of the draft as it is when the run starts, so later edits do not change a run in progress.
Press Check all in the bar to run every required test on the draft. The button shows Not run, Running, Passed or Failed, and its menu lists each required suite with its result and See the failing cases.
You choose which tests are required, and the minimum pass rate, on the Deploy page under Tests required before publishing.
Publish
Only an Owner or Admin can publish. A developer edits the draft and can run tests on it, but cannot ship it.
Press Publish in the bar above the agent. It is a split button: the main part opens the publish dialog. You can also open Deploy in the sidebar and press Review and publish.
Read What changes. Each changed setting appears as Added, Removed or Changed, with Before and After. Prompt, model, tone, knowledge, rate limits and theme are each listed.
Add a Note (optional) such as "What this release is for". Up to 500 characters.
Check Required tests. If a required suite has not passed on this exact draft, press Run required tests. Baseera shows an estimate of the cost on your provider key and asks you to confirm with Start the tests. Publish unlocks when every required suite reaches the minimum pass rate.
Press Publish version N. You see "Published as version N."
The dialog lists exactly the draft you reviewed. If someone edits the draft in the meantime, publishing is refused with "The draft changed after you opened this. Close it and review the draft again." so nobody ships changes they did not see.
Publish past failing tests
An Owner can choose Publish version N anyway and write a reason of 10 to 1,000 characters. The reason is saved in the History, together with how each required suite did. Admins cannot do this.
Read the status
The status in the bar shows one of four states:
- Live: a version is live, and there are no required tests or none has run on it yet.
- Draft: the draft has unpublished changes (shown in full as "Draft with unpublished changes" in the status menu).
- Live, passing: every required suite passed on the live version.
- Needs attention: a required suite failed on the draft, or fell below the pass rate on the live version.
Roll back
Rollback makes an earlier version the production version again. Nothing is deleted, and your draft is kept.
Press the arrow on the Publish button, or the version button in the sidebar's agent card, to open the versions menu. The same list is on the Deploy page under Versions.
Open a version to see Changes in vN, then choose Roll back to vN.
Add an optional note and press Roll back to version N.
Only owners and admins can roll back. Version numbers keep counting up, so publishing after a rollback never reuses a number. The History on Deploy lists every publish, rollback and override with who, when and the note.
What can go wrong
| Message | Cause and fix |
|---|---|
| "Only an owner or admin can deploy." | Your role cannot publish. Ask an owner or admin to review the draft. |
| "Nothing to deploy: there are no unpublished changes." | The draft equals production. |
| "A required test failed. Fix the draft, then run Check all." | Open See the failing cases, fix, and run again. |
| "A required test suite has not reached its pass rate on this draft." | Run the required tests again, or ask an owner to publish anyway. |
| "The draft can't be published as it is, for example because its provider key was removed." | Choose an active key on the Assistant page and save. |
| "That version can't be made production, for example because its provider key was removed." | A rollback target must have a working key. Choose another version. |
| "A run limit was reached (30 runs per agent per hour)." | Wait, then run again. |
| "Another test run is in progress for this agent." | Wait for it to finish. |
| "The draft has no active provider key, or a required suite has no cases." | Set a key, or add a test to the suite. |