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
{{ message }}
Repository navigation
[FEATURE]: Deactivate unused LSP servers during a session #12976
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.
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.
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.
Activity
github-actions commentedon Feb 10, 2026
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.
rombert commentedon Feb 10, 2026
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.
github-actions commentedon Apr 12, 2026
To stay organized issues are automatically closed after 90 days of no activity. If the issue is still relevant please open a new one.