> ## Documentation Index
> Fetch the complete documentation index at: https://help.notis.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Overview

> Choose which agent runs your work — Auto, Notis, Codex, or Claude Code — and whether it runs on your computer or in your Notis cloud.

When you give Notis a real piece of work — refactor a repo, dig through a project, run a long research task — Notis hands it to an agent. Agent routing is where you say *which* agent that is, and *where* it runs.

There are six choices:

| Target           | What runs                | Where it runs                                   |
| ---------------- | ------------------------ | ----------------------------------------------- |
| **Auto**         | Notis picks              | Local before cloud, then hosted Notis           |
| **Notis**        | The hosted Notis agent   | Notis servers                                   |
| **Codex Cloud**  | Your Codex account       | Your Notis cloud computer                       |
| **Claude Cloud** | Your Claude Code account | Your Notis cloud computer                       |
| **Codex Local**  | Your Codex CLI           | Your own machine, through the Notis desktop app |
| **Claude Local** | Your Claude Code CLI     | Your own machine, through the Notis desktop app |

## Auto versus a named target

**Auto** is the default. Notis ranks every coding-agent target your account can actually reach — your machine first, then your cloud computer, preferring whichever subscription still has usage left — and walks that chain. If nothing is connected, Auto lands on hosted Notis. Auto never fails: there is always somewhere to run.

A **named target** is a promise. If you pick Codex Local and your laptop is asleep, the request fails and says so. It does not quietly answer from a machine that has never seen your repository. That is deliberate: the old behaviour silently walked Desktop → Cloud → Notis, which could move a local coding task onto a host with none of your files.

There are no fallback checkboxes. Choosing Auto *is* the fallback ladder; choosing a named target is the hard pin.

## Local versus cloud

**Local** targets run the coding agent you already installed and signed in to, on your own computer. Notis sends it the task and reads back the result — your Codex or Claude login stays in that CLI's own credential store and never leaves the machine. The agent gets whatever your local CLI allows: your repositories, your files, your tools. It needs the [Notis desktop app](/your-computer/overview) running.

**Cloud** targets run the same first-party CLI inside your [Cloud Computer](/tools/cloud-computer) — an isolated container that belongs to your account. It stays available when your laptop is asleep, and the agent is boxed inside the container rather than sitting on your machine. Cloud targets need a plan that includes the Cloud Computer.

Either way, the model bill goes to your own Codex or Claude subscription. Notis never asks for an API key and never accepts one.

**Notis** is the hosted agent: no coding-agent account required. It is also where Auto ends when nothing else is ready.

## Where routing is decided

Notis resolves routing for each turn in this order, first match wins:

1. **This conversation** — the agent picker in the Notis overlay or chat sidepanel.
2. **This channel or automation** — the default you set on a channel, or on a single automation.
3. **Account default** — usually Auto after migration; Agents routing no longer sets this from the UI.

So a channel pinned to Codex Local with Auto everywhere else is a normal setup, and picking Claude Cloud once from the overlay does not change anything permanently.

## Related

* [Connect your agents](/agent-routing/connect-agents) — sign each target in.
* [Route channels, automations, and conversations](/agent-routing/route-channels-and-automations) — set routing per scope.
* [Your Computer](/your-computer/overview) — what the desktop app makes reachable.
* [Cloud Computer](/tools/cloud-computer) — the isolated container the cloud targets use.