Skip to main content
Project environment values are available to:
  • Terminals opened for the project or one of its worktrees
  • Startup, setup, named run, and archive commands
  • Agent processes working in the project

​
Add shared variables

Put non-secret team values in .radius/settings.toml:
These values are inherited by every worktree created from the project.

​
Store local variables and secrets

Use .radius/settings.local.toml for machine-specific values. Values under environment.secrets are hidden in the settings page after they are saved.
environment.secrets is valid only in .radius/settings.local.toml. Radius reports a diagnostic if a shared settings file contains secrets.

​
Remove an inherited variable

Use environment.unset in the local file to remove a shared variable on your machine:

​
Radius-provided variables

Radius also supplies repository and workspace context: Terminals created for CLI automation also receive RADIUS_WINDOW_ID, RADIUS_GROUP_ID, and RADIUS_TAB_ID. See Startup scripts.

​
Copy ignored files into worktrees

Use files.include for local configuration that a worktree needs but Git does not track:
When Radius creates a worktree, it copies matching files from the source project while preserving their relative paths. Only files that Git considers ignored are copied. Radius skips directories, symbolic links, paths outside the project, and .radius/settings.local.toml.
Add copied files to .gitignore before listing them under files.include. A tracked file already arrives through Git and does not need this setting.

​
Override the copied-file list

files.include is a single list rather than a merged collection. Defining it in .radius/settings.local.toml replaces the shared list for your machine.
For every environment and file key, see the settings file reference.