> For the complete documentation index, see [llms.txt](https://docs.uptiq.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.uptiq.ai/agent-builder/build/runtime-and-versioning.md).

# Runtime & Versioning

**Runtime & Versioning** is the page that controls which version of the platform's execution engine runs your agent. The executor changes over time — new versions add capabilities, fix issues, sometimes deprecate older behaviors — and this setting picks the version your agent is pinned to. Choosing an executor version is usually a one-time decision; the most common reason to revisit it is to gain access to a feature that depends on a newer runtime.

Manage Agent → Runtime & Versioning

Reach this page from **Manage Agent → Runtime & Versoning** in the left navigation. The left-nav label is spelled `Versoning`; the page title is spelled correctly `Versioning`. This is a labeling inconsistency in the current build (flagged in the companion anomalies report).

### Executor Version <a href="#executor-version" id="executor-version"></a>

The right pane has one field:

| Field            | Obligation | Default                                                          | Notes                                                                           |
| ---------------- | ---------- | ---------------------------------------------------------------- | ------------------------------------------------------------------------------- |
| Executor Version | Mandatory  | The latest version supported by your tenant (for example, `1.1`) | Switching versions can change agent behavior and the set of features available. |

The dropdown lists the executor versions available to your tenant. New agents are pinned to the latest version by default; existing agents stay on the version they were created with unless you change it deliberately.

### When the executor version matters <a href="#when-the-executor-version-matters" id="when-the-executor-version-matters"></a>

Most of the agent's configuration is portable across versions. A few features are version-gated, and the most visible one is **PII tokenization** — if your tenant has a masking provider connected, but the agent is pinned to an older executor that doesn't support PII tokenization, the PII tokenization section displays:

Switching to a newer executor version is the remediation. Other version-gated features may exist; if a section of the builder appears unavailable for reasons that aren't otherwise explained, the executor version is a place to check.

### Versioning the agent's draft <a href="#versioning-the-agents-draft" id="versioning-the-agents-draft"></a>

This page is **not** where you create version snapshots of your agent's configuration. That action lives in the header strip's **Draft Version** popover, described under The builder canvas.

To recap the distinction:

* **Executor Version** (this page) — the platform's runtime engine version. One choice per agent. Affects which features are available.
* **Draft Version** (header popover) — a snapshot of *this agent's configuration* at a moment in time. Many per agent. Used to roll back changes or compare configurations.

The two are independent. Saving a Draft Version doesn't change the Executor Version; changing the Executor Version doesn't save a Draft Version.

### Why this matters <a href="#why-this-matters" id="why-this-matters"></a>

Pinning your agent to a specific executor version makes the agent's behavior reproducible. If a platform upgrade introduces a behavior change you didn't expect, your agent isn't silently rolled forward — it stays on the version it was tested against until you choose to move it. That predictability matters most for agents already in production; for agents still under construction, pin to the latest version to access the most current feature set, and revisit the choice if you find yourself needing something a newer version offers.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.uptiq.ai/agent-builder/build/runtime-and-versioning.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.