Question

A developer on your team is frustrated that GitHub Copilot's inline code completions sometimes suggest calls to functions that don't exist anywhere in their large monorepo, even though a correctly named helper function is defined in a file three directories away. They ask you why Copilot can't just reference every function in the entire repository when generating a suggestion. Which explanation best describes the underlying limitation of how Copilot builds its prompt for code completion?

Accepted Answer

Copilot assembles a limited-size context from the current file and related signals (such as open tabs and neighboring snippets) rather than indexing the whole repository, so functions outside that context can be hallucinated.

Answer

Copilot uploads the full repository to the model on every keystroke, but the model randomly ignores files to save processing time.

Answer

Copilot only ever sees the exact line the cursor is on, so it can never use any surrounding code or other files as context.

Answer

Copilot maintains a permanent server-side index of every function in the repository, so missing functions indicate the index is corrupted.