You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Recent updates have caused even simple queries (eg what model are you?) to go into an infinite loop when using github-copilot/claude-sonnet-4.5 model. It answers, compacts, creates state for the next session, and keeps looping infinitely doing that.
Yeah, Visual Studio 2026 has a problem for sure. I get errors like the one described here. Agent stop working - then needs to be poked. And hard exceptions with exceeded context length. VSCode, ironically, work flawlessly and is free to use .. but I do love the Visual Studio 2026 IDE - just sad that AI integration is SO FAR BEHIND VSCode.
Activity
georgeharker commentedon Feb 13, 2026
Can confirm this is a bug which did not occur in v1.1.59
and was introduced in v1.1.60
I'm guessing this is a compaction check issue
neriousy commentedon Feb 13, 2026
can't reproduce
georgeharker commentedon Feb 13, 2026
Intriguing. It has also stopped for me this morning on @latest was 100% reproducible yesterday. I wonder if this was an issue on GitHub's end
gimlichael commentedon Feb 14, 2026
It happens in Visual Studio 2026 here; several times - model is not important.
When I ask why, it just says it will avoid that.
I fear tokens are just being wasted here.
chenyinchang commentedon Mar 13, 2026
Same problem. I think that the reason why from context length limit
gimlichael commentedon Mar 15, 2026
Yeah, Visual Studio 2026 has a problem for sure. I get errors like the one described here. Agent stop working - then needs to be poked. And hard exceptions with exceeded context length. VSCode, ironically, work flawlessly and is free to use .. but I do love the Visual Studio 2026 IDE - just sad that AI integration is SO FAR BEHIND VSCode.
github-actions commentedon Jul 3, 2026
To stay organized issues are automatically closed after 60 days of no activity. If the issue is still relevant please open a new one.