Feature flags

Toggle and route runtime behaviour — like agent-version routing — with Flagsmith-backed flags.

Feature flags are runtime switches (backed by Flagsmith) that let you turn behaviour on or off and route traffic — for example mapping an agent-version-routing variant to a specific agent version — without redeploying.

The flags are platform-wide: one set applies to every workspace. So only platform administrators (super-admins signed in with multi-factor authentication) can see and use the Feature Flags page. Everyone else does not see it in the sidebar, and opening its address shows "Page not found". If you need a routing rule, copy a rule template from your agent's Release tab and ask a platform administrator.

Create a flag

  1. As a platform administrator, open Settings in the sidebar and choose Feature Flags under Release.
  2. In Connection, select the Project and Environment you want to manage.
  3. In Create Feature Flag, enter a Flag key (e.g. agent-version-routing), an optional Description, and toggle Default Enabled.
  4. Click Create Flag.

Manage and route

  1. In the Feature Flags table, toggle Enabled and edit the Value for the selected environment, then click Save on that row.
  2. Use Archive, Unarchive, or Delete to manage a flag's lifecycle.
  3. In Advanced Routing Controls, select a flag and click Load Advanced Data to add Multivariate Options (weighted variants) or Segment Overrides.
  4. In Routing Mapping, click Open Agent Routing to map variant keys to agent versions.

Test an evaluation

  1. In Test Flag Evaluation, pick the Environment, Feature Flag, and default variant.
  2. Fill the Simple context (targeting key, account, user, environment, channel, agent) — or switch to Advanced to edit raw context JSON.
  3. Click Run Test to see the OpenFeature result the runtime would return.

Tip: Test with a realistic context before enabling a flag in production — evaluation uses the same path the runtime does.