A developer typing in their editor with GitHub Copilot wants to understand what travels to the Copilot service when a ghost-text completion is requested. Which description of the data flow for an inline completion request is accurate?
- AThe editor uploads the developer's entire local repository to GitHub on every keystroke so the model can index the whole project before replying.
- BThe plugin compiles and executes the project locally, then transmits only the runtime output of the program to the Copilot proxy for completion.
- CThe request is answered entirely on the developer's machine by a bundled offline model, so no prompt data leaves the editor at any point.
- DThe editor builds a prompt from nearby code and open-file context, sends it through the Copilot proxy to the model, and returns a suggestion to the editor. Correct
Why A is wrong: Copilot does not upload the whole repository on each keystroke; it assembles a bounded prompt of surrounding context, so describing a full-repo upload per keystroke overstates what is transmitted.
Why B is wrong: Copilot does not compile or run the project; it works from source text context rather than runtime output, so this confuses execution with the contextual prompt that is actually sent.
Why C is wrong: Inline suggestions are produced by a cloud-hosted model reached through the Copilot service, not a bundled offline model, so claiming nothing leaves the editor is incorrect.
Why D is correct: An inline request packages surrounding code and open-file context into a prompt, routes it through the Copilot proxy to the model, and returns the generated suggestion, which is the documented completion flow.