Environment Variables

Environment variables are key-value pairs scoped to a project and environment. At runtime, agents resolve {{env.KEY}} placeholders in tool configs and parameters to the matching value. Use them for non-sensitive settings like URLs, feature flags, and timeouts.

• Navigation: Admin > Team > Env Variables
• Required role: Owner, Admin, or Operator

Example:

tools:
  - name: crm-lookup
    config:
      base_url: '{{env.CRM_API_URL}}'
      timeout: '{{env.CRM_TIMEOUT_MS}}'

Environment Variables vs Secrets

• Variables: Non-sensitive config, visible to Operators, can be marked secret, scoped per project environment, syntax {{env.KEY}}.
• Secrets: Sensitive credentials, hidden after creation, always secret, scoped per workspace/project, syntax {{secret.KEY}}.

Use variables for environment-specific non-sensitive values; use secrets for API keys, passwords, tokens.

Config Variables

• {{config.KEY}} = plaintext, resolved at compile time
• One value per project (not environment-scoped)
• Best for project-wide constants

Environment Tabs & Toolbar

• Tabs: Global, Dev, Staging, Production (each shows variable count).
• Toolbar actions: Filter keys, Refresh, Diff, Namespaces, All Variables, Export, Import, Add Variable

Global variables are available in all environments. Environment-specific variables with the same key take priority over global variables.

Adding a variable

1. Go to Settings > Team > Env Variables.
2. Select the target project from the dropdown.
3. Select the target environment tab (Global, Dev, Staging, Production).
4. Click Add Variable.
5. In the dialog, enter:

• Key - unique identifier (use UPPER_SNAKE_CASE, for example: MY_API_KEY).
• Value - variable value.
• Description - optional usage note.
• Mark as secret - check if sensitive (hidden after creation).

1. Click Create.

When creating a variable on the Global tab, it will be available in all environments unless overridden by an environment-specific variable with the same key.

Editing & Deleting Variables

• Edit: Click Edit to update a variable’s value or description. Changes apply immediately.
• Delete: Click the delete icon and confirm.

Deleting a variable referenced in an agent definition causes runtime errors. Check references before deleting.

Export Variables

Export variables from the current environment tab for backup or reuse.

1. Select the environment tab.
2. Click Export.
3. Choose format: JSON (array) or .env (file format).
4. Copy to Clipboard or Download.
   Includes all variables in the selected environment.

Import Variables

Import variables into the current environment from a JSON array.

1. Select the environment tab.
2. Click Import.
3. Paste JSON in format:
   [
     {"key": "API_KEY", "value": "sk-xxx", "isSecret": true},
     {"key": "DB_URL", "value": "postgres://..."}
   ]
   
4. Check Overwrite existing variables to replace matching keys.
5. Click Import.

Creates new variables and updates existing ones if overwrite is enabled. Variables not in the file remain unchanged.

Workspace-Wide Variables

Environment variables are project-scoped. To replicate across projects:

• Use Export/Import with the same JSON file.
• Use workspace-level secrets for values shared across all projects.