Skip to content

Variable Page in XTM One

This page explains what the Variables page shows and how it works in XTM One.

Unlike most other resources, variables do not use a list page plus detail page pattern. They use one management page with create and edit dialogs.

What you see in the sidebar

In the left navigation, this area appears as Variables.

The page title is also Variables.

Variables main page

The variables page is a management board for reusable values.

Use this page to:

  • search variables by name, description, or known value pattern when they want to reuse an existing variable instead of recreating one
  • filter by tags to narrow the page to one project, environment, team, or workflow
  • create a variable when a value should be reused across prompts, skills, personas, or tools
  • edit an existing variable when the value changes over time but the same reference should stay valid
  • copy a variable reference so it can be inserted accurately elsewhere in the platform
  • delete a variable when it is no longer needed and should stop resolving in future uses

The header includes:

  • page title Variables
  • short description explaining that variables resolve at runtime in personas, prompts, skills, and tools
  • New Variable

The filter row includes:

  • search field
  • tag filter
  • result count

Variable cards

Each variable is shown as a card rather than as a row in a table.

The card shows:

  • name
  • description
  • whether the variable is Secret
  • company-managed or shared state when relevant
  • a value preview
  • updated time
  • tags

That design helps you decide quickly:

  • whether this is the right variable
  • whether it is sensitive
  • whether it still looks current enough to trust

For non-secret variables, the value preview is visible directly on the card.

For secret variables, the value preview is masked and the user can toggle reveal or hide on the card itself.

Each card also includes a small copy action for the variable reference.

Editing behavior

Clicking a variable card opens the edit dialog.

This means the variable UX is fast and lightweight:

  • no separate detail page
  • no separate tabs
  • edit in place through a modal dialog

New variable dialog

The create dialog contains:

  • name
  • value
  • Secret switch
  • description
  • tags
  • Cancel
  • Save

The key decision in this dialog is whether the variable should be marked Secret. That changes how it is displayed and handled later in the UI.

The page description also reminds users that variables are usually inserted from variable pickers in text editors elsewhere in the platform.

Edit variable dialog

The edit dialog uses the same fields, plus extra actions:

  • Copy reference
  • delete

That makes the edit dialog both a maintenance screen and a reuse screen. You do not open it only to change the value. You also open it to copy the correct reference format.

If the variable is secret, the value field does not automatically reveal the current stored value. Instead, the placeholder tells the user to enter a new value when they want to update it.

This behavior reinforces that secret handling is different from plain text variables.

Copying a variable reference

The UI lets users copy the reference format directly instead of typing it manually.

The copied format uses the variable ID, for example:

  • {{var_id.<id>}}

That makes the variable reusable in:

  • personas
  • prompts
  • skills
  • tools

Secret versus non-secret UX

The variables page makes the difference visible immediately:

  • non-secret variables use the standard braces icon and show their value preview
  • secret variables use a lock icon, show a Secret badge, and hide their value by default

This is one of the clearest resource pages in the product because the state is visible without opening the dialog.

Empty states

If no variables exist yet, the page shows an empty state inviting the user to create variables for dynamic values in personas, prompts, skills, and tools.

If variables exist but filters remove them all, the page shows No variables matching your filters.

Good habits on this page

  • Use Secret for credentials or sensitive values.
  • Copy the reference instead of typing it from memory.
  • Add clear descriptions so other users know where the variable should be used.
  • Use tags when the same workspace contains many operational variables.