Asking copiot for diagnostic backup:
This directly corroborates the instability you described. A few additions to strengthen the report:
Ran terminal command: Get-Content "$env:APPDATA\Code\User\settings.json" -ErrorAction SilentlyContinue | Select-String -Pattern "update|autoUpdate|autoCheck|telemetry|pylance|mcp" | Select-Object -First 30
Ran terminal command: Get-ChildItem "$env:APPDATA\Code\logs" -Recurse -Filter "*.log" -ErrorAction SilentlyContinue | Sort-Object LastWriteTime -Descending | Select-Object -First 10 FullName, LastWriteTime
Ran terminal command: $logPath = "C:\Users\dkmol\AppData\Roaming\Code\logs\20260522T035909\window1\exthost\output_logging_20260522T035912\3-GitHub Copil"
$files = Get-ChildItem "C:\Users\dkmol\AppData\Roaming\Code\logs\20260522T035909\window1\exthost\output_logging_20260522T035912" -ErrorAction SilentlyContinue
$files | Select-Object Name, Length
Ran terminal command: Get-ChildItem "C:\Users\dkmol\AppData\Roaming\Code\logs\20260522T035909" -Recurse -Filter "*.log" | Where-Object {$_.Length -gt 0} | Sort-Object LastWriteTime -Descending | Select-Object FullName, Length, LastWriteTime | Select-Object -First 20
Ran terminal command: Get-Content "C:\Users\dkmol\AppData\Roaming\Code\logs\20260522T035909\mcpGateway.log" | Select-String -Pattern "terminated|disconnect|error|pylance|SSE|reconnect|failed|drop" -CaseSensitive:$false | Select-Object -First 50
Ran terminal command: Get-Content "C:\Users\dkmol\AppData\Roaming\Code\logs\20260522T035909\mcpGateway.log" | Select-String -Pattern "terminated|TypeError|disconnect|drop|reconnect|failed|No SSE" -CaseSensitive:$false | Select-Object -First 60 | ForEach-Object { $_.Line }
Ran terminal command: $content = Get-Content "C:\Users\dkmol\AppData\Roaming\Code\logs\20260522T035909\mcpGateway.log"
Write-Output "--- Total lines: $($content.Count) ---"
$content | Select-Object -First 30
Ran terminal command: Get-ChildItem "C:\Users\dkmol\AppData\Roaming\Code\logs" -Directory | Sort-Object Name -Descending | Select-Object -First 5 Name
Ran terminal command: $prevLogs = @("20260520T203226","20260520T175450","20260520T174545","20260520T173756")
foreach ($session in $prevLogs) {
$log = "C:\Users\dkmol\AppData\Roaming\Code\logs$session\mcpGateway.log"
if (Test-Path $log) {
Write-Output "=== $session ==="
Get-Content $log | Select-String -Pattern "terminated|TypeError|SSE.*disconnect|drop|error|No SSE" -CaseSensitive:$false | Select-Object -First 10 | ForEach-Object { $_.Line }
}
}
Ran terminal command: $prevLogs = @("20260520T203226","20260520T175450","20260520T174545","20260520T173756")
foreach ($session in $prevLogs) {
$log = "C:\Users\dkmol\AppData\Roaming\Code\logs$session\mcpGateway.log"
if (Test-Path $log) {
Write-Output "=== $session ==="
Get-Content $log | Select-String -Pattern "terminated|TypeError|SSE.*disconnect|error]" -CaseSensitive:$false | Select-Object -First 8 | ForEach-Object { $_.Line }
}
}
Ran terminal command: $log = "C:\Users\dkmol\AppData\Roaming\Code\logs\20260520T203226\mcpGateway.log"
$content = Get-Content $log
Write-Output "Lines: $($content.Count)"
Look for any warnings or errors
$content | Select-String -Pattern "[warn]|[error]|failed|hang|timeout|No SSE" | Select-Object -First 20 | ForEach-Object { $_.Line }
Ran terminal command: $log = "C:\Users\dkmol\AppData\Roaming\Code\logs\20260520T203226\mcpGateway.log"
Get-Content $log | Select-String -Pattern "[warn]|[error]|SSE client detached|No SSE clients" |
Group-Object {$.Line -replace '\d{2}:\d{2}:\d{2}.\d{3}',''} |
ForEach-Object { "$($.Count)x $($_.Name)" } | Select-Object -First 20
This is damning. Let me get the full picture:
Ran terminal command: $log = "C:\Users\dkmol\AppData\Roaming\Code\logs\20260520T203226\mcpGateway.log"
$content = Get-Content $log
$total_detach = ($content | Select-String "SSE client detached").Count
$total_drop = ($content | Select-String "No SSE clients to broadcast").Count
$total_attach = ($content | Select-String "SSE client attached").Count
$sessions = ($content | Select-String "Creating new session").Count
Write-Output "Sessions created: $sessions"
Write-Output "SSE client attached: $total_attach"
Write-Output "SSE client detached: $total_detach"
Write-Output "Messages dropped (no SSE client): $total_drop"
Write-Output ""
Write-Output "--- Detach/attach ratio ---"
if ($total_attach -gt 0) { [math]::Round($total_detach / $total_attach, 1) }
Ran terminal command: # Show a window of rapid attach/detach cycling - the "thrash" pattern
$log = "C:\Users\dkmol\AppData\Roaming\Code\logs\20260520T203226\mcpGateway.log"
$content = Get-Content $log
Find lines with SSE client attached/detached near each other - take a 30-line window
$idx = ($content | Select-String "SSE client attached" | Select-Object -First 1).LineNumber
$content[($idx-2)..($idx+14)]
Ran terminal command: $log = "C:\Users\dkmol\AppData\Roaming\Code\logs\20260520T203226\mcpGateway.log"
$content = Get-Content $log
Show a burst of attach/detach to illustrate thrashing
$lines = $content | Select-String "SSE client (attached|detached)" | Select-Object -First 20
$lines | ForEach-Object { $_.Line }
I now have comprehensive log evidence. Here's what to add to your bug report:
📋 Additions to Strengthen the Bug Report
Evidence Section — Log Proof (add verbatim)
File: %APPDATA%\Code\logs\20260520T203226\mcpGateway.log
Quantified SSE churn (May 20 session alone):
| Metric |
Count |
| MCP sessions created |
20 |
| SSE client attached |
1,566 |
| SSE client detached (total: 0) |
1,566 |
| Messages dropped (no SSE client) |
40 |
The 1-second reconnect thrash pattern is logged explicitly:
20:39:58.397 SSE client detached (total: 0)
20:39:59.417 SSE client attached (total: 1) ← 1 second later, auto-reconnect
20:45:02.882 SSE client detached (total: 0)
20:45:03.892 SSE client attached (total: 1) ← 1 second later again
20:50:08.075 SSE client detached (total: 0)
20:50:09.093 SSE client attached (total: 1) ← same pattern, every time
This repeated 1,566 times in one session. Any in-flight tool call during that 1-second gap hangs permanently — the response arrives on a dead SSE channel that no longer exists.
Current session today also shows the race condition at startup:
04:13:32.062 Session initialized
04:13:32.062 --> notifications/tools/list_changed
04:13:32.062 No SSE clients to broadcast to, dropping message ← SSE not ready yet
04:13:32.069 SSE client attached (total: 1) ← arrived 7ms too late
Settings Discrepancy (add to report)
Your workspace .vscode/settings.json shows the pylance_mcp_server was already disabled as a workaround:
{
"github.copilot-chat.mcp.servers": {
"pylance_mcp_server": { "enabled": false }
}
}Your user-level settings show manual update controls but not extensions.autoCheckUpdates: false — meaning Pylance could still silently update and re-enable MCP behavior without consent. Add this to your user settings to close the gap:
"extensions.autoCheckUpdates": false
Design Issue — Your Core Argument (strengthened)
The logs prove the 1-second reconnect is VS Code's own internal retry loop — not a network issue, not user error. The MCP gateway reconnects automatically but there is no mechanism to:
- Pause a pending tool call during reconnect
- Notify the user a tool invocation is hung
- Cancel or timeout a waiting request
- Opt out of MCP being used for a given agent session
1,566 disconnects in a single evening session is not a footnote. It is a broken contract with a paying developer.
Root Cause: Pylance MCP Server Disconnecting
The logs show a clear pattern — the pylance_mcp_server MCP connection is repeatedly dropping with SSE stream disconnected: TypeError: terminated errors:
• This happened 4+ times in quick succession before this session even started
• When this session began, it reconnected (took 20ms), but the instability persists
When any of the pylance_mcp_server-* tools are invoked mid-stream-drop, the request hangs waiting for a response that never arrives.
How to fix:
- Restart VS Code — this is the most reliable fix; it resets the MCP server and SSE connection cleanly
- If that doesn't help: open VS Code settings and search for pylance_mcp_server and temporarily disable it, then restart
- Check Extensions → Pylance is up to date
The model request pipeline itself is healthy (token utilization at ~21%, normal LLM round-trip times). The hanging is entirely caused by the MCP server instability.
"update.mode": "none",
"extensions.autoUpdate": false,
"extensions.autoCheckUpdates": false,
"telemetry.telemetryLevel": "off",
"github.copilot.enable": {
"*": false
}
The option to choose to defer to MCP, the option to choose visibility and logging of a task's effort to validate progress, the lack of abiity to pause or stop or suspend, not only is troubling, it inhibits the human and AI collaboration. The hanging is infuriating when using the tool to build something that is too complex for the AI model to reason across the full scope of files. So, micro managing the effort - especialy with the MCP - has to be controllable. The fact the update gave me no choice - no abiity to opt in or out of a new feature - or shift in how the Ux workflow is assigned, depreciates the value of the copilot while it increases my distrust of anywork effort assigned without my oversight and guidance. This is more than a Bug. it is a design implication that has huge ramifications for anyone doing serious development - not just fast proto-typing - and it is a footnote in the release notes.
Type: Bug
Terrible. I lost all my ability to manage the interface with the Agents. No opt in. No Opt out. this recent update makes it impossible to have any interaction with the reasoning and analysis of the copilot. I have been a paying client. I want the control. Not AI. this is a terrible direction for the product and use of AI. Others will fill the void. Transparency is what is needed. Not hiding behind hand waving and obcuring the AI decisions that manifest the drift and missunderstandings it makes. I will drop this tool from use. I have researched settings and you have ripped the head off i see.
VS Code version: Code 1.121.0 (f6cfa2e, 2026-05-19T11:51:53+02:00)
OS version: Windows_NT x64 10.0.26200
Modes:
System Info
| Item |
Value |
| CPUs |
12th Gen Intel(R) Core(TM) i7-12650H (16 x 2688) |
| GPU Status |
2d_canvas: enabled
GPU0: VENDOR= 0x8086, DEVICE=0x46a3 [Intel(R) UHD Graphics], DRIVER_VENDOR=Intel, DRIVER_VERSION=31.0.101.4502 ACTIVE
GPU1: VENDOR= 0x10de, DEVICE=0x25a0 [NVIDIA GeForce RTX 3050 Ti Laptop GPU], DRIVER_VERSION=32.0.15.8183
GPU2: VENDOR= 0x1414, DEVICE=0x008c [Microsoft Basic Render Driver], DRIVER_VERSION=10.0.26100.8328
Machine model name:
Machine model version:
direct_rendering_display_compositor: disabled_off_ok
gpu_compositing: enabled
multiple_raster_threads: enabled_on
opengl: enabled_on
rasterization: enabled
raw_draw: disabled_off_ok
skia_graphite: disabled_off
trees_in_viz: disabled_off
video_decode: enabled
video_encode: enabled
webgl: enabled
webgl2: enabled
webgpu: enabled
webnn: disabled_off |
| Load (avg) |
undefined |
| Memory (System) |
15.68GB (2.65GB free) |
| Process Argv |
--crash-reporter-id 86431130-2d72-4b65-b758-329106e00554 |
| Screen Reader |
no |
| VM |
0% |
Extensions (16)
| Extension |
Author (truncated) |
Version |
| dart-code |
Dar |
3.134.0 |
| flutter |
Dar |
3.134.0 |
| githistory |
don |
0.6.20 |
| vscode-github-actions |
git |
0.31.5 |
| rainbow-csv |
mec |
3.24.1 |
| vscode-containers |
ms- |
2.4.4 |
| csdevkit |
ms- |
3.20.197 |
| csharp |
ms- |
2.140.8 |
| vscode-dotnet-runtime |
ms- |
3.0.2 |
| debugpy |
ms- |
2026.6.0 |
| python |
ms- |
2026.4.0 |
| vscode-pylance |
ms- |
2026.2.1 |
| vscode-python-envs |
ms- |
1.30.0 |
| cpptools |
ms- |
1.32.2 |
| rust-analyzer |
rus |
0.3.2896 |
| pdf |
tom |
1.2.2 |
A/B Experiments
vsliv368cf:30146710
vswsl492cf:30256860
pythonvspyt551:31249599
binariesv615:30325510
nativeloc1:31344060
dwcopilot:31170013
dwoutputs:31242946
copilot_t_ci:31333650
e5gg6876:31282496
pythonrdcb7:31342333
6518g693:31463988
aj953862:31281341
6abeh943:31336334
envsdeactivate2:31505458
cloudbuttont:31379625
42190218_ostrepl:31403339
ddidtcf:31399634
ec5jj548:31422691
cp_cls_t_966_ss:31454198
inlinechat_v2_hd992725:31505030
4je02754:31466945
8hhj4413:31478653
ge8j1254_inline_auto_hint_haiku:31490510
38bie571_auto:31478678
cp_cls_t_1081:31454832
conptydll_true:31498968
ia-use-proxy-models-svc:31452481
e9c30283:31461165
test_treatment2:31471001
46204921:31447328
rl_a_098a3278:31513473
idci7584:31464702
e3e4d672:31494082
ei9d7968:31496641
nes-extended-on:31455476
chat:31457767
8hig5102:31480529
89g7j272:31507493
7e187181:31503455
i2gc6536:31499202
52612955:31516516
ghj88844:31499326
ddid_t:31478206
hmra_i5g22:31518061
getcmakediagnosticson:31489824
ja75b849:31515466
7df3h592:31512476
pro_large_t:31499376
cp_cls_t_1082:31516087
logging_enabled_new:31498466
j0d79568:31499440
jb_cp_cls_c_632:31517842
852d2892:31506239
56dj4588:31512888
cg448276_tst_on:31514358
32d76977:31512328
ha629193:31508444
539gd155_c:31506875
jh5f2457_c:31515489
prpt_lrg:31515847
Asking copiot for diagnostic backup:
This directly corroborates the instability you described. A few additions to strengthen the report:
Ran terminal command: Get-Content "$env:APPDATA\Code\User\settings.json" -ErrorAction SilentlyContinue | Select-String -Pattern "update|autoUpdate|autoCheck|telemetry|pylance|mcp" | Select-Object -First 30
Ran terminal command: Get-ChildItem "$env:APPDATA\Code\logs" -Recurse -Filter "*.log" -ErrorAction SilentlyContinue | Sort-Object LastWriteTime -Descending | Select-Object -First 10 FullName, LastWriteTime
Ran terminal command: $logPath = "C:\Users\dkmol\AppData\Roaming\Code\logs\20260522T035909\window1\exthost\output_logging_20260522T035912\3-GitHub Copil"
$files = Get-ChildItem "C:\Users\dkmol\AppData\Roaming\Code\logs\20260522T035909\window1\exthost\output_logging_20260522T035912" -ErrorAction SilentlyContinue
$files | Select-Object Name, Length
Ran terminal command: Get-ChildItem "C:\Users\dkmol\AppData\Roaming\Code\logs\20260522T035909" -Recurse -Filter "*.log" | Where-Object {$_.Length -gt 0} | Sort-Object LastWriteTime -Descending | Select-Object FullName, Length, LastWriteTime | Select-Object -First 20
Ran terminal command: Get-Content "C:\Users\dkmol\AppData\Roaming\Code\logs\20260522T035909\mcpGateway.log" | Select-String -Pattern "terminated|disconnect|error|pylance|SSE|reconnect|failed|drop" -CaseSensitive:$false | Select-Object -First 50
Ran terminal command: Get-Content "C:\Users\dkmol\AppData\Roaming\Code\logs\20260522T035909\mcpGateway.log" | Select-String -Pattern "terminated|TypeError|disconnect|drop|reconnect|failed|No SSE" -CaseSensitive:$false | Select-Object -First 60 | ForEach-Object { $_.Line }
Ran terminal command: $content = Get-Content "C:\Users\dkmol\AppData\Roaming\Code\logs\20260522T035909\mcpGateway.log"
Write-Output "--- Total lines: $($content.Count) ---"
$content | Select-Object -First 30
Ran terminal command: Get-ChildItem "C:\Users\dkmol\AppData\Roaming\Code\logs" -Directory | Sort-Object Name -Descending | Select-Object -First 5 Name
Ran terminal command: $prevLogs = @("20260520T203226","20260520T175450","20260520T174545","20260520T173756")
foreach ($session in $prevLogs) {
$log = "C:\Users\dkmol\AppData\Roaming\Code\logs$session\mcpGateway.log"
if (Test-Path $log) {
Write-Output "=== $session ==="
Get-Content $log | Select-String -Pattern "terminated|TypeError|SSE.*disconnect|drop|error|No SSE" -CaseSensitive:$false | Select-Object -First 10 | ForEach-Object { $_.Line }
}
}
Ran terminal command: $prevLogs = @("20260520T203226","20260520T175450","20260520T174545","20260520T173756")
foreach ($session in $prevLogs) {
$log = "C:\Users\dkmol\AppData\Roaming\Code\logs$session\mcpGateway.log"
if (Test-Path $log) {
Write-Output "=== $session ==="
Get-Content $log | Select-String -Pattern "terminated|TypeError|SSE.*disconnect|error]" -CaseSensitive:$false | Select-Object -First 8 | ForEach-Object { $_.Line }
}
}
Ran terminal command: $log = "C:\Users\dkmol\AppData\Roaming\Code\logs\20260520T203226\mcpGateway.log"
$content = Get-Content $log
Write-Output "Lines: $($content.Count)"
Look for any warnings or errors
$content | Select-String -Pattern "[warn]|[error]|failed|hang|timeout|No SSE" | Select-Object -First 20 | ForEach-Object { $_.Line }
Ran terminal command: $log = "C:\Users\dkmol\AppData\Roaming\Code\logs\20260520T203226\mcpGateway.log"
Get-Content $log | Select-String -Pattern "[warn]|[error]|SSE client detached|No SSE clients" |
Group-Object {$.Line -replace '\d{2}:\d{2}:\d{2}.\d{3}',''} |
ForEach-Object { "$($.Count)x $($_.Name)" } | Select-Object -First 20
This is damning. Let me get the full picture:
Ran terminal command: $log = "C:\Users\dkmol\AppData\Roaming\Code\logs\20260520T203226\mcpGateway.log"
$content = Get-Content $log
$total_detach = ($content | Select-String "SSE client detached").Count
$total_drop = ($content | Select-String "No SSE clients to broadcast").Count
$total_attach = ($content | Select-String "SSE client attached").Count
$sessions = ($content | Select-String "Creating new session").Count
Write-Output "Sessions created: $sessions"
Write-Output "SSE client attached: $total_attach"
Write-Output "SSE client detached: $total_detach"
Write-Output "Messages dropped (no SSE client): $total_drop"
Write-Output ""
Write-Output "--- Detach/attach ratio ---"
if ($total_attach -gt 0) { [math]::Round($total_detach / $total_attach, 1) }
Ran terminal command: # Show a window of rapid attach/detach cycling - the "thrash" pattern
$log = "C:\Users\dkmol\AppData\Roaming\Code\logs\20260520T203226\mcpGateway.log"
$content = Get-Content $log
Find lines with SSE client attached/detached near each other - take a 30-line window
$idx = ($content | Select-String "SSE client attached" | Select-Object -First 1).LineNumber
$content[($idx-2)..($idx+14)]
Ran terminal command: $log = "C:\Users\dkmol\AppData\Roaming\Code\logs\20260520T203226\mcpGateway.log"
$content = Get-Content $log
Show a burst of attach/detach to illustrate thrashing
$lines = $content | Select-String "SSE client (attached|detached)" | Select-Object -First 20
$lines | ForEach-Object { $_.Line }
I now have comprehensive log evidence. Here's what to add to your bug report:
📋 Additions to Strengthen the Bug Report
Evidence Section — Log Proof (add verbatim)
File:
%APPDATA%\Code\logs\20260520T203226\mcpGateway.logQuantified SSE churn (May 20 session alone):
The 1-second reconnect thrash pattern is logged explicitly:
This repeated 1,566 times in one session. Any in-flight tool call during that 1-second gap hangs permanently — the response arrives on a dead SSE channel that no longer exists.
Current session today also shows the race condition at startup:
Settings Discrepancy (add to report)
Your workspace
.vscode/settings.jsonshows the pylance_mcp_server was already disabled as a workaround:{ "github.copilot-chat.mcp.servers": { "pylance_mcp_server": { "enabled": false } } }Your user-level settings show manual update controls but not
extensions.autoCheckUpdates: false— meaning Pylance could still silently update and re-enable MCP behavior without consent. Add this to your user settings to close the gap:Design Issue — Your Core Argument (strengthened)
The logs prove the 1-second reconnect is VS Code's own internal retry loop — not a network issue, not user error. The MCP gateway reconnects automatically but there is no mechanism to:
1,566 disconnects in a single evening session is not a footnote. It is a broken contract with a paying developer.
Root Cause: Pylance MCP Server Disconnecting
The logs show a clear pattern — the pylance_mcp_server MCP connection is repeatedly dropping with SSE stream disconnected: TypeError: terminated errors:
• This happened 4+ times in quick succession before this session even started
• When this session began, it reconnected (took 20ms), but the instability persists
When any of the pylance_mcp_server-* tools are invoked mid-stream-drop, the request hangs waiting for a response that never arrives.
How to fix:
The model request pipeline itself is healthy (token utilization at ~21%, normal LLM round-trip times). The hanging is entirely caused by the MCP server instability.
"update.mode": "none",
"extensions.autoUpdate": false,
"extensions.autoCheckUpdates": false,
"telemetry.telemetryLevel": "off",
"github.copilot.enable": {
"*": false
}
The option to choose to defer to MCP, the option to choose visibility and logging of a task's effort to validate progress, the lack of abiity to pause or stop or suspend, not only is troubling, it inhibits the human and AI collaboration. The hanging is infuriating when using the tool to build something that is too complex for the AI model to reason across the full scope of files. So, micro managing the effort - especialy with the MCP - has to be controllable. The fact the update gave me no choice - no abiity to opt in or out of a new feature - or shift in how the Ux workflow is assigned, depreciates the value of the copilot while it increases my distrust of anywork effort assigned without my oversight and guidance. This is more than a Bug. it is a design implication that has huge ramifications for anyone doing serious development - not just fast proto-typing - and it is a footnote in the release notes.
Type: Bug
Terrible. I lost all my ability to manage the interface with the Agents. No opt in. No Opt out. this recent update makes it impossible to have any interaction with the reasoning and analysis of the copilot. I have been a paying client. I want the control. Not AI. this is a terrible direction for the product and use of AI. Others will fill the void. Transparency is what is needed. Not hiding behind hand waving and obcuring the AI decisions that manifest the drift and missunderstandings it makes. I will drop this tool from use. I have researched settings and you have ripped the head off i see.
VS Code version: Code 1.121.0 (f6cfa2e, 2026-05-19T11:51:53+02:00)
OS version: Windows_NT x64 10.0.26200
Modes:
System Info
GPU0: VENDOR= 0x8086, DEVICE=0x46a3 [Intel(R) UHD Graphics], DRIVER_VENDOR=Intel, DRIVER_VERSION=31.0.101.4502 ACTIVE
GPU1: VENDOR= 0x10de, DEVICE=0x25a0 [NVIDIA GeForce RTX 3050 Ti Laptop GPU], DRIVER_VERSION=32.0.15.8183
GPU2: VENDOR= 0x1414, DEVICE=0x008c [Microsoft Basic Render Driver], DRIVER_VERSION=10.0.26100.8328
Machine model name:
Machine model version:
direct_rendering_display_compositor: disabled_off_ok
gpu_compositing: enabled
multiple_raster_threads: enabled_on
opengl: enabled_on
rasterization: enabled
raw_draw: disabled_off_ok
skia_graphite: disabled_off
trees_in_viz: disabled_off
video_decode: enabled
video_encode: enabled
webgl: enabled
webgl2: enabled
webgpu: enabled
webnn: disabled_off
Extensions (16)
A/B Experiments