Skip to main content

Live versions and the release gate

Every agent has one live version. When anyone calls the agent by name, from the Agent API, the hosted chat, a channel, A2A, a phone or voice call, the live version runs. This lets you save and test a new version without changing what people get.

Release settings​

Each project has release settings. Open an agent and choose Release settings. Anyone on the project can read them. Only a project admin can change them.

SettingDefaultWhat it does
New versions go live on saveOnWhen on, saving an agent makes the new version live straight away. When off, a save creates a draft.
Require a passing eval to go liveOffWhen on, a version can go live only if its latest run of each required eval suite passed.
Which suitesEvery suite for the agentThe suites the gate requires. You can pick specific ones. A suite must name its agent to be picked.

When the eval gate is on, saves never go live on their own, whatever the first setting says. A version that was saved a moment ago has no eval run yet.

Make a version live​

  1. Open the agent. Its panel lists every version and marks the live one.
  2. Choose Make v6 live (the button names the version).

With the gate on, the panel shows the gate's verdict for each version before you choose. You need the developer or admin role on the project. Every change of live version is recorded in the audit log, with the version it replaced.

If no version of an agent is live, calls to it by name are refused until one is.

How the gate decides​

For each required suite, the gate looks at the latest run of that suite against this exact version:

  • A suite that has never run against the version blocks it. Untested is not passed.
  • A run that has not finished blocks it.
  • A run that failed blocks it, even if an older run passed.
  • A pass on an earlier version does not count for a new one.

If the project requires evals but no required suite exists for the agent, every version is blocked until you create one.

When a version is blocked, the refusal names each suite, its latest run and its score against the threshold.

Override the gate​

A project admin can make a blocked version live by giving a reason. The override is recorded in the audit log as its own eval_gate_override event, with the verdict it overrode, so you can find every override without reading every change.

Code agents​

A code agent's versions come from builds, and Promote on its Versions tab makes one live. The same gate applies: the required suites are the ones its orchestrate.yaml names plus the project's required suites, and a project admin can override with a reason. Promote also compares the version's results with the live version's, so you see what got worse. See Code agents.

A typical flow​

  1. Turn on Require a passing eval to go live for the project.
  2. Write an eval suite for the agent. See Evals.
  3. Change the agent and save. The new version is a draft.
  4. Run the suite against the new version.
  5. If it passes, choose Make vN live. If it fails, fix the agent and save again.

Deleting the live version​

See Delete a version. With drafts or the gate on, Orchestrate refuses to delete the live version until you make another one live, so it never promotes a draft behind your back.

Was this page helpful?
On this page
Talk to our teamQuestions about licensing or sizing VoisX Orchestrate for your site? We can help.Talk to sales →