v0.13.0
Released November 18, 2026. Supported until May 18, 2027.
v0.13.0 ships 19 behavior changes, 2 security updates, 13 new features, 28 bug fixes, and 1 deprecation. Behavior between the management plane and the data plane changed in this release. The most severe security issue cleared is medium.
A fully detailed version of these release notes (including artifact versions) is included in the Admin Console.
The full release notes are opened from the Admin Console, as described in Check the management plane version.
Upgrade and rollback
- The release carries no breaking change. 23 changes name operator steps of their own, given with each change in the full release notes in the Admin Console.
- The upgrade rolls through without dropping traffic.
- Rollback to v0.12.1 is conditional. See the note below.
Finish the management plane rollout before upgrading data planes. While 0.12 and 0.13 management plane replicas run side by side, an OAuth MCP profile with an access policy can serve with only its project's required scopes. After rolling the management plane alone back to 0.12, edits to such a profile do not reach a 0.13 data plane, which keeps the last policy it rendered; delete the profile to take it off. After rolling both planes back below 0.13, every such profile serves as in 0.12 with no access policy. After a rollback of the management plane to a release before 0.13.0, the data plane stops enforcing require_binding. Token calls that name a project are admitted again without a binding. A 0.12 management plane also does not refuse a write that removes the last verifier of a project that only a binding verifies. Before the rollback, give each such project a gateway auth policy of its own, or set its accepted credentials to API_KEY.
Behavior changes
Budgets
On data planes running 0.13.0 or later, exhausted-budget blocks and fallback switches are skipped for passthrough requests only when both Count passthrough in budgets and Passthrough can use managed models are No. Available once the data plane is on 0.13.0 or later.
Gateway
Tare keeps strict mode off for OAuth MCP profiles when upgrading from 0.12 without an explicit setting.
Under strict mode, an OAuth MCP profile is not served if its project has a gateway auth policy but no gateway, or a gateway without a jwt policy.
New OAuth MCP profiles admit no callers until an access policy is set.
An edited MCP profile stays pending until every serving data plane accepts the edit. Available once the data plane is on 0.13.0 or later.
An MCP profile's access policy applies to every MCP method. Available once the data plane is on 0.13.0 or later.
A personal OAuth MCP profile with its own issuer and key set keeps serving under strict mode on self-hosted installs, to any token its own issuer signs.
During a management plane rollback, an OAuth MCP profile keeps its last access policy render if an older management plane sends it without one. Available once the data plane is on 0.13.0 or later.
Data plane spans no longer include the tars.signature attribute.
Request logs and MCP request logs have a new trace_id field: the id of the trace recorded for the request, so the entry can be looked up in your tracing backend. Available once the data plane is on 0.13.0 or later.
For a project that accepts IdP tokens through a claim-to-project binding alone, with no gateway auth policy of its own, a token that matches bindings for two projects reaches the project named in x-tars-project. Available once the data plane is on 0.13.0 or later.
For a project that accepts IdP tokens through a claim-to-project binding alone, disabling a policy of the project for an issuer does not stop that issuer's tokens while a binding on another project's enabled policy for the issuer names the project. Available once the data plane is on 0.13.0 or later.
For a project that accepts IdP tokens through a claim-to-project binding alone, a call that names the project gets 503 keys_unavailable when the binding's policy has no usable key set, and 503 bindings_unavailable when the data plane did not receive the policy's bindings. Available once the data plane is on 0.13.0 or later.
When a data plane's proxy configuration exceeds its size limit, the management plane first removes the organization's application mappings and IdP registrations from the gateway auth block.
The data plane proxy now writes one JSON access-log line per request.
Observability
Traces are stored in the management plane's observability store and queried with TraceQL on port 3200 of the dpo-oap Service.
Management plane API
TRUSTED_PROXY_HOPS (default 0) sets how many proxies add to X-Forwarded-For.
Failed SSO, SAML, social and CLI logins now create failed LOGIN audit records.
Super Admin and the admin management key now include applications.read and applications.edit.
Security updates
Data plane
The data plane now refuses all revoked, disabled or deleted API keys, regardless of revocation-list length.
Auth
/oauth/revoke now revokes an MCP client's refresh token and all tokens rotated from it.
New features
Gateway
MCP spans carry the backend that served the call in the mcp.backend.name attribute, so traces can be filtered by MCP backend. Available once the data plane is on 0.13.0 or later.
OAuth MCP profiles can allow callers by client id or scope, and deny listed client ids first. Available once the data plane is on 0.13.0 or later.
Data plane
MCP calls made with an API key now carry the caller's customer, user, API key and data plane on their spans, as model calls do, and MCP request logs record the API key id. Available once the data plane is on 0.13.0 or later.
Management plane API
Data plane traces can be read through the API: GET /v1/traces lists them with filters, and GET /v1/traces/{trace_id} returns one trace with its spans.
Admins can disable managed-model use for an organization's passthrough requests. Available once the data plane is on 0.13.0 or later.
Gateway auth policies now support require_binding. Available once the data plane is on 0.13.0 or later.
A project can accept IdP tokens on a gateway without a gateway auth policy of its own when a claim-to-project binding on an enabled jwt policy of that gateway names it. Available once the data plane is on 0.13.0 or later.
Request Logs identifies the budget and fallback policy that acted on a request. Available once the data plane is on 0.13.0 or later.
Detaching a project from a project gateway, or deleting or archiving the project, returns failed_precondition while a claim-to-project binding on one of its jwt gateway auth policies is all that verifies the IdP tokens of another project on that project gateway.
Request logs now include caller_path, which is empty unless a preview feature is enabled.
GetSCIMReconcileReport lists people SCIM has not confirmed for a given number of days.
tare CLI
Run tetrate agentrouter doctor --only hostnames before changing data plane hostname configuration to compare declared hostnames, inference routes and project configuration, and identify hostnames the data plane cannot route.
Consoles
Each project in the Admin Console has a Catalog → MCP OAuth Clients page listing the project's own MCP OAuth clients, with search, a status filter, and add, edit and delete, like the organization page.
Bug fixes
Auth
SSO provider reads return the callback an OIDC sign-in sends as oidc.redirect_uri, and the SSO provider status returns the same value as oidc_callback_url, also before a provider exists.
Roles and permissions
Organization roles with projects.read now list all organization projects in the Admin Console project pickers and RBAC Access and Roles pages.
Data plane
A traffic-splitting policy in which every model but one has weight 0 now sends its requests to that one model, instead of answering 500.
Data planes now retain model routes during concurrent route updates and restore missing routes on the next update.
MCP OAuth token updates now complete as skipped without a failed event or repeated retries, because the data plane receives these tokens through the MCP profile and does not apply the event.
A data plane installed from rendered manifests (the install command's --print-resources output, helm template, Argo CD or Flux) now starts its Controller in the data plane's namespace, so models are served instead of every request returning 404.
When a data plane requests a configuration that does not exist, the management plane returns an empty result.
Consoles
Admins can now open Home in the Developer Console when they can see projects where they are not users.
Users whose organization role lists the organization's projects can now open those project pages in the Admin Console.
Goose and VS Code icons now display correctly in the MCP catalog's client connect panel.
In the Developer Console, Add Server accepts non-OAuth MCP servers that require a token without a successful Test connection.
In the Developer Console, Test connection runs from the data plane that serves the profile's project and lists tools for servers it can reach. Available once the data plane is on 0.13.0 or later.
Request logs no longer flag a request as using a fallback model when the model name contains a short size or variant token such as 4o or 7b (for example gpt-4o-2024-08-06).
Admin Console Request Logs retain entries during brief management plane restarts when the data plane's export queue has room.
Gateway
On data planes at 0.10.0 or later, requests route on declared hostnames even when an unused endpoint is also present. Available once the data plane is on 0.10.0 or later.
Adding a project to a data plane with an existing endpoint routes it through that endpoint instead of creating another.
Declared hostnames remain routable when a project's endpoint URL contains capital letters.
Requests on existing connections now use updated project hostname access rules as soon as the data plane receives them.
After a model route is removed, the data plane stops routing the hostname within about five minutes, without waiting for another configuration change.
Management plane API
Creating an existing encryption key through the management API now returns HTTP 409 Conflict.
An RBAC call with a missing or malformed role, binding, group or Team id now returns HTTP 400 invalid_argument instead of HTTP 500 internal.
Saving different fields of the same guardrail or guardrail rule at the same time, from the API or the Admin Console, now keeps both changes instead of one save undoing the other.
Audit records for telemetry configuration changes now include the signed-in user's id and email, including project telemetry changes in the Developer Console.
Request Logs now marks input blocked by a guardrail as not served (not_served). Available once the data plane is on 0.13.0 or later.
A Connect request whose JSON cannot be decoded, in a POST body or in the message query parameter of a GET, now returns HTTP 400 with code invalid_argument instead of HTTP 500, so SDKs stop retrying it.
A telemetry export config read right after an update or delete now returns the change, a second update no longer reverts the first, a config can be created again right after it was deleted, and trace exports follow the change within 10 seconds instead of up to 5 minutes.
tare CLI
The install guide and the quickstart now use the tetrate CLI that the install script installs: they check the install with tetrate --version and sign in and create keys with tetrate agentrouter api commands.
SDK
The quickstart bundled in the Go SDK tarball now runs with go run ./examples/quickstart from the extracted SDK root, as the install guide describes.
Deprecations
Management plane API
The GET /v1/request-logs/policy-counts route of CountRequestsByPolicy is deprecated.