Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bug: LSP Crashing in Agent Mode, Problems Paused - Extend to All Extensions #6311

Open
beingminimal opened this issue Mar 10, 2025 · 0 comments
Assignees
Labels
bug Issue identified by VS Code Team member as probable bug completions

Comments

@beingminimal
Copy link

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:

  1. Install LSP: Install and enable an LSP (e.g., Deno).
  2. Open File: Open a file of the LSP's language (e.g., .ts, .js).
  3. Activate Agent: Trigger Agent Mode involving that file.
  4. 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.

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.

@beingminimal beingminimal added bug Issue identified by VS Code Team member as probable bug completions triage-needed Issues needing to be assigned to the prospective feature owner labels Mar 10, 2025
@vs-code-engineering vs-code-engineering bot removed the triage-needed Issues needing to be assigned to the prospective feature owner label Mar 10, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Issue identified by VS Code Team member as probable bug completions
Projects
None yet
Development

No branches or pull requests

2 participants