Skip to main content

Choose an agent with aliases

An alias is a short name for a coding agent and a model, such as #opus or #sol. Write it in a Linear issue or comment to choose who works on that task. Without one, your workspace's developer agent does the work.

Built-in aliases​

AliasModel
#opusClaude Opus 5.5
#fableClaude Fable 5.1

Use an alias on one task​

Put the alias anywhere in the issue description or in the comment that starts the work:

@thriveondev #opus /implement

The alias applies to the implement and fix-review runs of that task. The review uses your workspace's reviewer agent.

How the agent is chosen​

ThriveOnDev looks for an agent in this order:

  1. The first #word in the issue or comment that matches an alias.
  2. Your workspace's Developer setting.
  3. The platform default, #astra.
warning

Any #word that matches an alias selects that agent, even in a sentence like "fixes the #sol layout". Write aliases only when you mean them.

Set your workspace default​

Owners and admins choose the default under Settings → AI models → Developer. It applies to every task that does not name an alias, including tasks picked up through the Automatable label.

Make sure the alias can run​

An alias only works if the person who gave the task has AI access for that agent. A #sol task needs a Codex sign-in, and an #opus task needs a Claude key. If it is missing, the task stops with AI access not connected. See Add your AI access.