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
In VS Code Agent Mode, LSP servers (e.g., Deno LSP) crash while agents are running. This coincides with the "Problems are paused" feature, indicated by a blue squiggly and the message: "Problems are paused because: [prompt]". This suggests a conflict between agent execution and LSP stability. VS Code already pauses problem reporting; to mitigate LSP crashes, this mechanism should be extended to pause all extensions for the affected file during agent activity.
Steps to Reproduce:
Install LSP: Install and enable an LSP (e.g., Deno).
Open File: Open a file of the LSP's language (e.g., .ts, .js).
Activate Agent: Trigger Agent Mode involving that file.
Observe LSP Crash: * Output Panel: Check LSP output for errors, restarts during agent run.
Problems Paused: Verify blue squiggly and "Problems are paused" message.
LSP Features: Confirm broken LSP features (completion, go-to-definition, diagnostics).
Expected Behavior:
LSP should function normally during agent execution. Problem reporting should remain active. Agent Mode should not disrupt core language support.
Actual Behavior:
LSP crashes/becomes unstable during agent run. Problem reporting is paused. This degrades development experience due to unreliable language features and missing error reporting.
Mitigation Suggestion: Extend "Problems Paused" to Pause All Extensions
VS Code already pauses problem reporting, a good first step. Extend this to temporarily pause all extensions (including LSP) for the file active in Agent Mode. This would likely prevent LSP crashes by avoiding resource conflicts. Upon agent completion, extensions should resume automatically. This leverages existing functionality for a more robust Agent Mode.
The text was updated successfully, but these errors were encountered:
Description:
In VS Code Agent Mode, LSP servers (e.g., Deno LSP) crash while agents are running. This coincides with the "Problems are paused" feature, indicated by a blue squiggly and the message: "Problems are paused because: [prompt]". This suggests a conflict between agent execution and LSP stability. VS Code already pauses problem reporting; to mitigate LSP crashes, this mechanism should be extended to pause all extensions for the affected file during agent activity.
Steps to Reproduce:
.ts
,.js
).Expected Behavior:
LSP should function normally during agent execution. Problem reporting should remain active. Agent Mode should not disrupt core language support.
Actual Behavior:
LSP crashes/becomes unstable during agent run. Problem reporting is paused. This degrades development experience due to unreliable language features and missing error reporting.
Environment:
Version: 1.99.0-insider (Universal)
Commit: 8ebc9a6f21bef915c1373b8d0f57a95b496216dd
Date: 2025-03-10T05:05:11.392Z
Electron: 34.2.0
ElectronBuildId: 11044223
Chromium: 132.0.6834.196
Node.js: 20.18.2
V8: 13.2.152.36-electron.0
OS: Darwin arm64 24.0.0
Mitigation Suggestion: Extend "Problems Paused" to Pause All Extensions
VS Code already pauses problem reporting, a good first step. Extend this to temporarily pause all extensions (including LSP) for the file active in Agent Mode. This would likely prevent LSP crashes by avoiding resource conflicts. Upon agent completion, extensions should resume automatically. This leverages existing functionality for a more robust Agent Mode.
The text was updated successfully, but these errors were encountered: