Relay Settings
Workspace-level defaults that apply across all runners — the default executor used when no label is set, and the path where runners clone repositories.
The Relay Settings page (/home/relay-settings) holds two workspace-level settings that apply to every runner paired to your account. Neither is required to get started, but both are worth configuring once your setup is stable.
Default executor
Where: Relay Settings → Workspace defaults → Default executor.
This dropdown sets the agent that runs jobs when no executor label is present on the Linear issue and no project-level label provides a fallback. The options are:
| Option | Behaviour |
|---|---|
| No default | Jobs with no executor label are held in a waiting_for_input state until you add one. |
| Codex CLI | All unlabelled jobs are routed to Codex. |
| Claude Code | All unlabelled jobs are routed to Claude Code. |
When to set a default
If your team predominantly uses one agent, setting a default avoids having to add an executor label to every issue. Jobs that need a different agent can always override the default with an explicit issue label — the label resolution priority is issue label → project label → this workspace default.
If you regularly use both agents for different types of work, leave this as No default and use project-level labels to route each Linear project to the right agent.
Effect on blocked jobs
Jobs that arrived before a default was set and are currently in waiting_for_input will not be automatically unblocked — you need to re-trigger them from the job detail page after saving the default.
Workspace path
Where: Relay Settings → Workspace path → Clone path.
This field sets the directory on the runner machine where Delego clones repositories when a job starts. It defaults to ~/delego-runner/workspace when left blank.
The value is baked into the pairing command the dashboard generates. When you pair a runner, the relay includes this path in the setup command so the runner process knows where to put its worktrees from the moment it first registers.
Changing the path
If you update the workspace path after runners are already paired, the new path takes effect for runners paired after the change. Existing paired runners will continue to use the path they were given at pairing time until they are re-paired.
To apply a new path to an existing runner:
- Save the new path in Relay Settings.
- Go to the Runners panel.
- Remove the runner you want to update.
- Pair it again — the generated command will now include the new path.
Choosing a path
A few things worth considering when picking a location:
- The directory should be on a disk with enough space for the repositories you expect to clone. Delego creates one worktree per job and cleans it up after the job completes, so peak usage is roughly the size of your largest repository multiplied by the number of runners running simultaneously.
- Avoid paths inside existing git repositories — worktrees must be created outside the repo they belong to.
- If you are running the runner as a background service, make sure the service user has write access to the path.