Skip to main content
An alias is a named pointer to one or two agent versions. Clients invoke the agent by alias — my_agent@production — and the alias decides which version actually runs. Repoint the alias and every client picks up the change on the next call.
Alias tab

​
Configuration

​
Single-version alias

Map a name to one immutable version. The most common pattern: To ship a new version: build and test it as v8, then re-point production from v7 to v8. To roll back: re-point production to v7. No client redeploy required.

​
Dual-version alias (canary / A-B)

Setting both Version 1 and Version 2 with a Weight between them splits invocations between the two versions according to the weight. Useful for:
  • Canary releases — production = 95% old / 5% new, ramped up if the new version performs well.
  • A/B experiments — compare two prompt or model configurations on real traffic.
Traces tag each run with which version actually executed, so you can compare success rate, latency, and cost between the two.

​
Same model for workflows

Workflows use the identical versioning + alias model — pr_triage@production works the same way.