Environments
Every agent has two environments, test and live. Each serves its own published version, so your team can try a version while your users keep the current one.
Each surface of an agent (the widget, the public API and Slack) is deployed separately in each environment, with its own switch and its own pinned version. The Studio shows test as Test and live as Production. Publishing pins one version on every surface enabled in the chosen environment, in a single transaction. The two environments move independently: publishing to test does not change what live serves.
| Entry point | How the environment is chosen |
|---|---|
| Widget | By the deployment its rk_wgt_ token names. Each environment has its own token and its own allowed origins. |
| Public API | By the key: an rk_test_ key reaches test, an rk_live_ key reaches live. The API surface must be enabled in that environment. |
| Slack | Always live. A Slack deployment in test does not answer. |
| Playground | No environment. It runs the saved version you pick, and its runs are left out of production metrics. |
A run keeps the version it started with, even if you publish a new one a second later. Publishing changes what the next run gets, never what a run in progress is doing.
Publication gates (Enterprise)
With an Enterprise license that includes publication gates, a version reaches live only if it passes the agent's gated test suites. Before the version is pinned, every suite that carries a pass-rate threshold runs on it, and a verdict already reached for that version is reused. Below the threshold, or when a suite has not finished in time, the publication is refused, nothing changes and the refusal is recorded in the audit log. The suites, their thresholds and the last verdict are on the Publication gate card of the agent's Deploy tab. test is never gated, so a failing version can be examined there. See Enterprise modules.