> For the complete documentation index, see [llms.txt](https://docs.codemate.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.codemate.ai/cora/modes/auto.md).

# Auto

Orchestrator mode. Cora selects and sequences the appropriate modes based on what the prompt requires.

Auto is the default mode for open-ended or multi-step tasks. Rather than locking into a single mode, Cora evaluates the prompt and decides whether to plan first, write code, ask a clarifying question, or review what it just produced and can move between modes as the task unfolds.

<figure><img src="https://2395938751-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FZ8BnJrGJwy0hT6DEkmb4%2Fuploads%2FpDAplDA7fGF6kHNpUarY%2FAuto%2Bmode.gif?alt=media&amp;token=aa5e1d81-0794-412c-bc64-6dc06c8a69d3" alt=""><figcaption></figcaption></figure>

***

### When to use Auto

Auto is the right choice when you're not sure which mode a task requires, or when a task is likely to span more than one mode. Building a new feature from scratch, for example, naturally involves planning the approach, writing the code, and reviewing the result Auto handles the sequencing without you having to switch manually.

If you have a specific, well-scoped task :

&#x20;`explain this function` ,  `refactor this file`, `review this diff` , `Fix this bug`

using a targeted mode directly is faster and more predictable. Auto adds value when the task is larger or less defined.

***

### How Auto mode works

For a complex prompt, Auto typically follows this order:

1. If the task involves architectural decisions, it runs **Plan** first and surfaces the plan for your review.
2. Once you confirm, it switches to **Code** to execute.
3. After generating changes that touch security-sensitive areas, it runs a **Review** pass automatically.
4. At any point, it can pause in **Ask** mode if it needs clarification to proceed correctly.

The current mode is always visible in the panel. You can see when Cora switches and why.

> You can interrupt Auto at any mode transition. If the plan doesn't look right, push back before execution starts. If the code looks wrong mid-generation, stop and redirect don't let it finish and then ask it to redo.

***

### Auto vs. manual mode selection

Auto does not always sequence all four modes. For a small, unambiguous task like adding a field to an existing model, it will skip Plan and go straight to Code. The planning overhead is proportional to the complexity of the task.

If you want to force a planning step for a task Auto would otherwise execute directly, use Plan mode explicitly, review the output, then switch to Code.