Skip to content

[FEATURE]: Deactivate unused LSP servers during a session #12976

Closed

Description

@rombert

Feature hasn't been suggested before.

  • I have verified this feature I'm about to request hasn't been suggested before.

Describe the enhancement you want to request

I am sometimes working in a monorepo-like setup, where I have 3-400 hundred projects checked out. I have wide-reaching tasks that require investigatin/changes in maybe 10-20 projects per session.

For each changed project, a JDT LSP server is instantiated. Those do add in up terms of memory available on my laptop and eventually lead to performance problems.

My workaround is to exit opencode and immediately resume the session - this way the LSP servers are stopped and respawned when needed.

It would be great if opencode would handle this gracefully by deactivating LSP servers for projects that were not recently used in the current session.

Activity

  1. added
    discussionUsed for feature requests, proposals, ideas, etc. Open discussion
    on Feb 10, 2026
  2. added
    perfIndicates a performance issue or need for optimization
    on Feb 10, 2026
  3. github-actions commented on Feb 10, 2026

    @github-actions
    Contributor

    This issue might be a duplicate of existing issues. Please check:

    These issues all relate to LSP memory management and process accumulation in monorepos. Your feature request (#12976) is well-documented and addresses a specific need for deactivating unused LSP servers during a session, which would complement the above discussions on LSP resource management.

  4. rombert commented on Feb 10, 2026

    @rombert
    Author

    This is related to #11368 but not the same. In my case there is no 'root' pom.xml, the projects are independent. But if JDT can handle mutiple unrelated projects with a single instance then that's good.

  5. github-actions commented on Apr 12, 2026

    @github-actions
    Contributor

    To stay organized issues are automatically closed after 90 days of no activity. If the issue is still relevant please open a new one.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

discussionUsed for feature requests, proposals, ideas, etc. Open discussionperfIndicates a performance issue or need for optimization

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions