BUG: Autocompletions are not shown in VS 2026

[fitdev]

Copilot autocompletions are not being displayed despite successful API responses. I get NullReferenceException:

   at JeffPires.VisualChatGPTStudio.Copilot.Suggestions..cctor() in C:\Source\github\VisualChatGPTStudio\Copilot\Suggestions.cs:line 54
   --- End of inner exception stack trace ---
   at JeffPires.VisualChatGPTStudio.Copilot.Suggestions.ShowAutocompleteAsync(ITextView textView, String autocompleteText, Int32 position)
   at JeffPires.VisualChatGPTStudio.Copilot.InlinePredictionManager.<ShowAutocompleteAsync>d__7.MoveNext() in C:\Source\github\VisualChatGPTStudio\Copilot\InlinePredictionManager.cs:line 126

I am using VS Insiders

[fitdev]

A minor extra thing - it would be nice if Chat timeouts could be customized. Right now it automatically times out after like 2 minutes or so, which is not always desirable.

[jeffdapaz]

@fitdev, Lately I've been short on time, but as soon as I have some free time, I'll look into it.

[fitdev]

BTW I think this happens because you are using reflection to call VS's Intellicode internal APIs and they must have changed it in more recent previews.

And as another side note I noticed that when extension is enabled (and I tried using chat) both whole using chat and afterwards VS hangs for a second or so very often - likely due to forced GC or something.

[jeffdapaz]

Hi @fitdev,

Yeah, the inline Copilot suggestions rely on Visual Studio internal APIs via reflection, and recently microsoft did a extensive updates on these APIs . That’s why you getting a NullReferenceException in Suggestions.cs.

I actually spent a few hours trying to get it working again (even with AI help), but I couldn’t restore it reliably with the latest VS changes. Because of that, I’m keeping inline Copilot available for VS2022 stable, but it stays disabled on VS2026 for now until I find a solution.

About the brief “hangs” you mentioned: are your chats usually very large and/or do you keep many chat tabs open at the same time? I’m asking because I’m not seeing those freezes on my side, so I’m trying to figure out if it correlates with big chat history / lots of open tabs.

Also, I implemented it in the latest release (5.8.1) the editable timeout. There’s now a Timeout option in settings so you can configure how long the extension waits for API responses.

[fitdev]

About the brief “hangs” you mentioned: are your chats usually very large and/or do you keep many chat tabs open at the same time? I’m asking because I’m not seeing those freezes on my side, so I’m trying to figure out if it correlates with big chat history / lots of open tabs.

Not at all, for me it started basically as soon as I open a chat window and submit my first message.