Skip to main content
Routing is set in three places, from broadest to narrowest. Each one falls back to the one above it, so you only set what you actually want to differ. At request time Notis takes the narrowest choice that exists: conversation, then channel or automation, then the account default (Auto unless you have changed it elsewhere). Agents routing in the account menu is only for connecting Codex and Claude. It does not pick an account-wide target — that default is Auto.

​
One channel

Open the Channels page, then the defaults for the channel you want — WhatsApp, Telegram, Slack, email, the desktop app, and so on. The Agent section lists Auto, then Notis, Codex Cloud, Claude Cloud, Codex Local, and Claude Local. Leave it on Auto unless you want that channel pinned. Save, and every message arriving on that channel routes there. This is the useful one for splitting work by context: WhatsApp on Auto for everyday chat, the desktop app on Codex Local because that is where your repositories are.

​
One automation

Open the automation and set its Agent in the editor.
  • An automation that must touch your local machine — a nightly repository job, something reading local files — should pin a Local target. If the machine is offline, the run fails loudly instead of answering from a host without your files.
  • An automation that just needs an answer — a daily digest, a summary — should stay on Auto so a sleeping laptop does not skip your morning brief.
An automation with no routing set inherits Auto (or whatever narrower scope sits above it).

​
One conversation

In the Notis overlay and in the chat sidepanel, the composer has an agent picker alongside the intelligence and speed pickers. Open it with ⌥ A, or click it, then choose with the arrow keys or the number next to each target. Two things to know:
  • It only affects that conversation. Nothing is saved to the channel or your account.
  • Unconnected targets are dimmed. Clicking one takes you to Agents routing to connect it, rather than selecting a target that cannot run.
The button next to the composer names the current target whenever it is not plain Auto/Notis inheritance, so you can always see where the next message is going. A dashed outline means the target is inherited from your channel; a solid one means you picked it for this conversation.

​
A worked example

A setup that keeps local work local without making everything brittle:
  • Everywhere else: Auto. Everyday chat always answers, and prefers your machine when it is awake.
  • Desktop app channel: Codex Local. Coding work runs on your machine, or fails rather than being answered by an agent with no access to your code.
  • Nightly repository automation: Codex Local. It runs where the repository is, or it tells you it did not run.