Routing

Routing configs set defaults for new cloud tasks and let integration messages select an agent with a keyword. Local tasks use the connected computer’s model picker. Each config is a row in Settings → Routing:

Field	Meaning
Trigger	The keyword that selects this config, written as `/keyword` (e.g. `ultra`)
Harness	Which coding agent + model runs the task (e.g. Codex GPT 5.5)
Effort	A reasoning level supported by the selected model
Instructions	Optional custom instructions appended to the task

Every cloud workspace has an undeletable default config — the fallback when no trigger matches. Check that row for the workspace’s current agent, model, and effort.

/plan and /goal are harness commands, not routing configs. A trigger can precede them: @twill /ultra /plan ….

Using triggers

Start a task message with the trigger:

@twill /ultra fix the race condition in the export worker

The trigger is stripped before the agent sees the message. How a trigger fires depends on the surface:

Surface	How to fire a config
Web app	Pick the harness and effort directly in the composer
Slack, Notion, Asana	`/trigger` at the start of the message
GitHub	`/trigger` in the text, or an issue label matching the trigger
Linear	An issue label matching the trigger

Routing applies to a task’s first message only. Follow-ups keep the task’s existing harness.

Get started

Local and cloud

Tasks

Customization

Integrations

Apps and developer tools

Workspace and account

Using triggers

​Using triggers

Using triggers