A developer keeps breaking flow to switch from the editor to a browser and search the project's framework documentation for the right API call. They want to keep that lookup inside their current file without leaving the editor. Which Copilot surface most directly reduces this context switching?
- AOpen the GitHub web interface in a browser tab and read the repository wiki there, so the answer sits beside the code that the developer is currently editing in the IDE.
- BAsk Copilot Chat about the API inside the editor, since it answers from the editor and keeps the developer in their current file rather than sending them to a browser. Correct
- CRun GitHub Copilot CLI in a separate terminal pane to ask about the API, then copy the explanation back into the file the developer is working in.
- DWait for inline ghost-text completions to surface the API call while typing, on the basis that completions remove any need to ask a question about the framework at all.
Why A is wrong: A browser wiki keeps a reference handy but is still a separate window, so it does not remove the editor-to-browser switch that the developer is trying to avoid.
Why B is correct: Copilot Chat runs inside the IDE and answers questions about code in context, so the developer gets the lookup without leaving the editor, directly cutting context switching.
Why C is wrong: GitHub Copilot CLI helps with shell tasks but lives in the terminal, so copying answers back into the editor reintroduces the switching the developer wants to stop.
Why D is wrong: Inline completions suggest code as you type but cannot answer a what-does-this-do question, so they do not provide the explanation the developer is looking for.