Module 1 · ModesVerified 2 Nov 2026

Ask, Plan, Agent & Autopilot

Copilot works very differently depending on the mode. Choosing well is the single biggest habit change you can make.

A workflow that works

Most good sessions move left to right.

Explore the four modes

Pick a mode to see what it can do

Edits files, runs commands, fixes its own errors. You approve the risky steps.

Edits files

Yes — across many files

Runs terminal commands

Yes, with approval

Asks you

Yes — approvals and questions

Permission level

Manual permissions (the default)

Best for

Well-scoped implementation, bug fixes with a failing test, migrations where you want to watch each step.

Watch out

Review diffs and use checkpoints to roll back. Keep tasks small so you can review them.

Example prompt

Implement the plan above. Run the tests after each step and stop if anything fails twice.

Which mode should I use?

Tap a task

Choose a task above and the recommended mode appears here.

Copilot modes compared
Mode	Changes files	Runs commands	Asks you	Use for
Ask	No — read-only	No	Not needed	Understanding unfamiliar code, explaining an error, learning a concept, comparing options.
Plan	No — writes a plan only	No	Yes — clarifying questions	Features that touch several files, risky refactors, anything where you would normally sketch the approach first.
Agent (interactive)	Yes — across many files	Yes, with approval	Yes — approvals and questions	Well-scoped implementation, bug fixes with a failing test, migrations where you want to watch each step.
Autopilot	Yes — unattended	Yes, auto-approved	No — answers its own questions	Repetitive, well-specified work with strong tests: bulk renames, adding types, generating test suites.

Autopilot and permissions

Autopilot behaves like auto-approving everything. Pair it with the terminal sandbox and a clean git branch. See the permissions module.