Why mode matters
If you use the wrong Copilot mode, the interaction feels clumsy. The tool is strongest when the question fits the mode.
- Chat: ask broader questions, explain code, compare approaches.
- Inline: change the file you already have open.
- Agent: handle guided multi-step work and cross-file tasks.
- Review: inspect, test, and keep ownership with the developer.
Mode comparison
When to use each mode
- Chat when you want explanation, brainstorming, or design discussion.
- Inline when you want a local edit inside one file.
- Agent when you want guided work across multiple steps.
- Review when you want to inspect what changed before you accept it.
Practical examples
// Chat prompt
Explain why this repository uses dependency injection here.
Compare this service to a simpler implementation.// Inline prompt
Refactor this method to reduce duplication and keep behavior the same.How I used the modes in .NET delivery work
- Chat when I need to understand unfamiliar code before touching it.
- Inline when I want a small refactor or a quick test added in the file I already have open.
- Agent when the change spans multiple files or takes a few steps to finish.
- Review when I want to inspect the diff and keep the final merge decision with me.
What not to do
- Do not use agent mode to avoid understanding your code.
- Do not accept inline edits without reading the diff.
- Do not use chat as a substitute for design ownership.
Closing takeaway
Copilot becomes useful when you match the task to the mode. That keeps the workflow fast without removing the developer’s judgment.