GitHub Copilot: Extended Range Next Edit Suggestions in Visual Studio
GitHub CopilotGitHub Copilot's next edit suggestions (NES) in Visual Studio can now predict and propose follow-up edits anywhere in the active file, not just near the cursor. Previously, NES was limited to the immediate area around the current edit, which often missed related changes further down the file. The feature, called long-distance or extended-range NES, ships off by default and can be turned on from the editor's inline suggestion settings.
Sources & Mentions
1 external resource covering this update
Predicting Edits Beyond the Cursor
Next edit suggestions have always tried to anticipate a developer's next change, but the feature was historically confined to a small window around the cursor. That worked well for tightly clustered edits, but many real changes ripple outward: renaming a variable, updating a function signature, or adjusting a related conditional several lines, or screens, away.
How Extended Range Works
With this update, Copilot can scan the entire active file for edits that logically follow from a change just made, rather than only the immediate vicinity. If a developer updates a type definition near the top of a file, Copilot can now surface a related suggestion further down where that type is used, instead of requiring the developer to notice and make that edit manually.
Turning It On
The capability ships as an opt-in setting rather than a default behavior. Developers can enable it under Tools > Options > Text Editor > Inline Suggestions by selecting "Enable extended range suggestions." GitHub has kept it off by default for now, suggesting the team is still gathering feedback before making it the standard experience.
Why It Matters
For developers who rely heavily on NES during refactors, this closes one of the more common frustrations with the feature: doing a multi-location edit and having Copilot only catch the change closest to where they clicked. Extending the suggestion range across the whole file makes NES more useful for exactly the kind of cross-cutting edits developers already do by hand.