Google Analytics, Vercel Web Analytics, Leadsy and the TikTok Pixel stay off until you accept. The help chat starts once you have chosen. The scheduling button starts once you have chosen. Read our Privacy Policy.

Skip to content
StellarFirmStellarFirm
Mission manual
Esc

Type a word to search every page. Try , or .

Module 02 · The CEO

Routing

How StellarFirm decides which assistant gets a message: name an assistant to send it straight there, or let the CEO assistant match it.

View as Markdown
On this page

Routing is how a message you write ends up with the right assistant. You can steer it yourself by naming an assistant, or leave it to the CEO assistant.

Three ways a message is routed#

You writeWhat happens
A message that starts with an assistant's nameIt goes straight to that assistant. No guessing.
A message with no nameThe CEO assistant matches it to the right assistant from what it is about.
A message that is unclearThe CEO assistant takes the safe path and asks you.

Name an assistant#

Start your message with the assistant's name and it goes straight there.

PromptSend straight to the Coder

@coder fix the failing tests on [repository] and open a pull request for review.

Putting @, /, or persona: in front of the name all work, for example /coder ... or persona: coder .... The prompts in these docs often open with "Coder," in plain words, which the CEO assistant reads as addressing the Coder. The @ form is the surest way to skip routing completely.

Let the CEO assistant match it#

If you name nobody, the CEO assistant looks at what the message is about. Words like build, fix, tests, pull request, and CI point to the Coder. Other subjects point to other roles.

The message is aboutBelongs toStatus
Building, fixing, tests, pull requests, CICoderAvailable
What to build, priority, acceptance criteriaProduct ownerComing soon
Campaigns, launch posts, waitlistsMarketingComing soon
Invoices, expenses, budgetsAccountantComing soon
Contracts, terms, privacy wordingLegalComing soon

Only available assistants receive work. A role that is Coming soon is never chosen.

When the match is not clear#

If a message could belong to more than one role, or does not clearly belong to any, the CEO assistant does not guess. It takes the safe path: it asks you which assistant you mean, or what you want done.

You can avoid the question by writing a clearer goal. See write a good goal.

Several Coders#

You can run more than one Coder. When you do, the CEO assistant decides which Coder takes each message, so separate goals can move in parallel, each in its own workspace. You can also name a Coder at the start of a message.

Where routing runs#

Matching a message to an assistant takes one short check. You choose where that check runs for the whole company, in Settings under Models.

ChoiceWhat happens
Europe firstThe check runs in Europe. Only if Europe cannot answer in time does it run in the United States. This is the default.
Europe onlyThe check runs in Europe and nowhere else. If Europe cannot answer, the built-in rules decide and nothing is charged.
United StatesThe check runs in the United States.

Pictures, such as a screenshot of a portal, are only ever checked in Europe. A message is charged one routing fee however many tries the check takes, and nothing if every try fails. Only the CEO can change the choice; everyone else on the account sees it but cannot edit it.

Routing and approvals#

Routing decides who works. It never skips an approval. Whichever assistant gets a message, the same rules apply to risky steps. See approvals.

Prompts to try#

PromptLet the CEO route it

CEO, [describe the job in a sentence]. Pick the right assistant and tell me who you chose.

PromptAsk who owns it

CEO, who should handle [job], and what would they need from me?

Next#