Question

A developer working in a large monorepo asks why GitHub Copilot sometimes suggests a function signature that doesn't match a utility defined in a completely separate module that is not currently open in the editor. As the Copilot administrator explaining how completion prompts are built, which statement best describes the underlying cause?

Accepted Answer

Copilot builds the prompt primarily from the current file and a limited set of related context such as open tabs, so a closed, unrelated module is unlikely to be included in the prompt sent to the model.

Answer

Copilot indexes and reads the entire repository from disk for every completion request, so the closed module must have been corrupted or excluded by a content-exclusion rule.

Answer

Copilot stores all previously accepted suggestions in a persistent per-user database and reuses them, so the mismatch is caused by a stale cached suggestion.

Answer

Copilot sends the developer's full local file system tree to the model on each keystroke, so the model always has every module available and the mismatch indicates a proxy filtering error.