Skip to main content
Project settings define how Radius prepares a repository, creates worktrees, starts commands, and configures the environment used by terminals and agents. Use the settings page for local choices and .radius/settings.toml for behavior that everyone working in the repository should share.

Environment and files

Configure variables, secrets, and ignored files copied into worktrees.

Git and worktrees

Choose the starting ref, remote, push behavior, and archive behavior.

Scripts and automation

Configure startup, setup, run, and archive commands.

Settings file reference

See every TOML field, default, and override rule.

​
Open project settings

1

Open the project menu

Open the menu for a project or worktree group in the Radius sidebar.
2

Choose Settings

Radius opens a project-scoped settings tab with Environment, Git, and Scripts sections.
3

Choose what to share

Changes made in the settings page are local to your machine. Use Open settings.toml to edit shared repository settings in your preferred editor.

​
Shared and local settings

.radius/settings.toml belongs in version control. Use it for team-wide variables, copied-file patterns, Git behavior, and scripts.
Settings resolve in this order:
  1. Radius defaults
  2. .radius/settings.toml
  3. .radius/settings.local.toml
Local values override shared values. Resetting local overrides returns the project to its shared configuration.
Worktrees inherit effective settings from their source project. Radius does not copy .radius/settings.local.toml into a new worktree.

​
What project settings control

  • Environment variables for terminals, lifecycle commands, and agent processes
  • Gitignored files copied into new worktrees
  • The Git ref and remote used for new worktrees and pushes
  • Whether local worktree branches are removed after archiving
  • Startup automation powered by the Radius CLI
  • Worktree setup, named run commands, and pre-archive cleanup
Continue with the settings file reference for the complete TOML format.