Question

A developer notices that when they add a helper function at the very top of a large file, GitHub Copilot's inline completions further down the file don't seem to consistently use it, even though the function is clearly visible in the same file. They ask you why Copilot doesn't always incorporate every piece of code in the open file into its suggestions. Which explanation best describes how Copilot's prompt-building process handles this situation?

Accepted Answer

Copilot assembles a prompt within a limited token budget, selecting and prioritizing context by estimated relevance to the cursor rather than including the entire file verbatim, so distant code may be truncated or deprioritized.

Answer

Copilot always sends the complete contents of every open file to the model, so any inconsistency must be caused by a network error dropping part of the request.

Answer

Copilot permanently memorizes functions it has seen earlier in the session and reuses them from that memory, so the helper should have been remembered regardless of position.

Answer

Copilot only reads the 15 lines immediately above and below the cursor and ignores all other content in the file entirely.