Environments & Variables

Environments are named sets of key-value variables scoped to a project. Switching the active environment changes the values injected into all probes and chains without modifying any probe configuration. This lets you reuse the same probes against different targets (e.g. dev, staging, prod).

[SCREENSHOT: Environment panel — environment selector dropdown at top, variable table below with key/value columns]

Creating an environment

[SCREENSHOT: New environment dialog — name field and confirm button]

Open the Environments panel inside a project and click New environment. Give it a name (e.g. dev, staging).

Adding variables

Add key-value pairs to the environment. Variable names are case-sensitive.

Key	Value
host	api.dev.example.com
token	dev-secret-token
email	test@example.com

[SCREENSHOT: Variable table with several rows, edit and delete icons per row]

Using variables in probes

Reference a variable anywhere a text field is supported using double curly braces:

https://{{host}}/api/users
Authorization: Bearer {{token}}

Supported fields per probe type:

Probe	Fields
HTTP	URL, body, headers, query parameters, cookies
SMTP	Host, each command’s data
IMAP	Host, each command’s data
LDAP	Host, DN, password, filter, attribute, value
SpamAssassin	Host, message body

Switching environments

[SCREENSHOT: Active environment chip in the project sidebar — “staging” chip with dropdown arrow]

The active environment is shown as a chip in the project sidebar. Click it to switch to a different environment. The selection is remembered across sessions (stored locally) and does not affect other users.

Variable priority

If a probe defines its own inline variables with the same name as an environment variable, the probe’s inline variable wins.

Environments in chains

Chains resolve variables server-side at execution time using the same environment. When you run a chain, the active environment’s variables are applied to all steps in addition to any variables produced by extractors.