# Task modes

Choose the mode that matches what you want Syntheo to do.

| Mode | Use it when | What to expect |
|---|---|---|
| **Submit** | You want the task completed | Syntheo inspects, makes needed changes, checks the result, and summarizes it |
| **Ask** | You want an explanation or comparison | Syntheo answers without making changes unless you clearly request them |
| **Architect** | You want a plan before implementation | Syntheo studies the project and produces a reviewable plan without implementing it |
| **Debug** | Something is wrong but the cause is unclear | Syntheo investigates the symptom before making a focused fix |

## Quick choices

### Use Submit when

- the outcome is clear;
- you are ready for files to change;
- you know how success should be checked.

### Use Ask when

- you are learning an unfamiliar project;
- you want a review or explanation;
- you want to compare options before deciding.

Add “do not edit” when staying read-only is important.

### Use Architect when

- the task affects several areas;
- requirements still need decisions;
- you want to approve the approach first;
- compatibility or migration risk matters.

After reviewing the plan, start a Submit task to implement it.

### Use Debug when

- you can describe a failure;
- you have an error, screenshot, or reproduction;
- you do not yet know the root cause.

Give Debug the expected result, actual result, and shortest reliable reproduction.

## Presets and modes are different

A **mode** says what kind of work to do. A **preset** chooses the model configuration used for that work.

Start with Standard. Use Hunter for difficult reasoning, Design for interface work, and Browser when the task needs web interaction.

## Next

Learn how to write the request in **[Prompts, context, and steering](prompts-and-context.md)**.

[← Everyday work](README.md) · [User guide](../README.md) · [Documentation use notice](../NOTICE.md)