Runtime & Versioning
Select, validate, and upgrade the Agent Executor version that runs your agent.
Runtime & Versioning controls the Agent Executor version that runs your agent. Executor releases add capabilities, address issues, and can deprecate earlier behavior. Pinning a version keeps runtime behavior predictable while you validate upgrades.
Set the version on the Agent Behaviour page: open Agent Config → Agent Behaviour and use the Runtime & Versioning dropdown at the foot of Advanced Controls. The Agent Config sidebar has no separate Runtime & Versioning item.
Executor Version
Use the Runtime & Versioning dropdown, called Executor Version in the My Agents menu, to select the runtime for this agent. On the Agent Behaviour page its hint reads "Runtime version for this agent. Different versions may change behavior and available features." Open the dropdown to see the list. The selected version is ticked, and versions that are no longer supported are greyed out and marked Deprecated.

Executor Version
Mandatory
The latest version available to your tenant, such as 1.4
Switching versions can change agent behavior and available features.
The dropdown lists versions available to your tenant. New agents use the latest available version by default. Existing agents remain on their current version until you migrate them.
You can also change it from the agent list: in My Agents, select ••• on the agent's row, then Executor Version. The current version is ticked, and 1.0 is marked Deprecated.

Migrate to v1.4
Agent Executor v1.4 is the current documented upgrade target. Migrate when you need its runtime capabilities or support for the current release.
In Executor Version, select
1.4.Select Save.
Test representative conversations, skills, and integrations.
Check expected outputs and execution behavior before you rely on the upgraded agent in production.
See September 12 release notes for the v1.4 announcement.
When the executor version matters
Most agent configuration works across versions. Some capabilities require a newer executor version. For example, PII tokenization can be unavailable when an agent uses an older unsupported version.
If a builder section is unavailable, check the executor version. Upgrade and validate the agent when the feature requires a newer runtime.
Draft versions and executor versions
Executor Version selects the platform runtime. Draft Version saves a snapshot of the agent configuration.
Executor Version
One runtime per agent
Control runtime behavior and feature availability
Draft Version
Many snapshots per agent
Compare or restore agent configuration
The settings are independent. Saving a draft doesn't change the executor version. Changing the executor version doesn't save a draft.
Which agent version runs
An agent has a draft (version 0), the numbered versions you save, and one live version: the version that was last published and approved. See Publish an agent.
When someone starts a conversation, the platform picks the version like this:
The request names a version
That version. Through the API this is the version field; 0 is the draft.
The request names no version
The live version. If nothing has been published yet, the draft.
The person was given one saved version of the agent (a Viewer)
That version. A request for the draft or for no version resolves to it, and any other version is refused.
The conversation already started
The version it started on. A follow-up message can't switch it.
Saving a newer version doesn't change what an existing integration runs if it names a version. To move it forward, change the number it sends.
A flow or another agent that you add as a skill has its own version choice. A flow runs Current Published or a pinned Version N, and an agent runs Draft or a saved version. See Add a flow as a skill.
In the agent playground, the chat widget has a version picker, but only in developer mode, and developer mode is available only in local, development, and release-candidate environments, not in production. In a running conversation the picker is read-only: Start a new chat to switch versions.
Why this matters
Version pinning makes agent behavior reproducible. Your agent remains on its tested runtime until you choose an upgrade. Use the latest supported version for new agents, then validate it before production use.
Last updated
Was this helpful?

