LSP lifecycle: when should LSP servers be alive? Who's responsible for what? What does peak performance look like?

[Disasm]

tracey v1.2.0

Steps to reproduce:

• Start IDE (Cursor in my case) with tracey LSP enabled
• Open a Rust project that uses the time create
• Use "go to definition" for any of the imports from time
• Observe the list of running processes

The list of running processes contains
tracey daemon $HOME/.cargo/registry/src/index.crates.io-1949cf8c6b5b557f/time-macros-0.2.27 --config $HOME/.cargo/registry/src/index.crates.io-1949cf8c6b5b557f/time-macros-0.2.27/.config/tracey/config.styx or something similar.

[fasterthanlime]

Super sympathetic to this, however I have no idea how to fix it.

tracey doesn't decide when to launch itself. It could exit right after noticing this project has no tracey config — I have no idea how various code editors would react to that (they'd probably try to restart it? or show its status as "errored"?)

I'll have to read up on how LSP are supposed to handle this.

[Disasm]

I'm not familiar with LSPs, but I guess it would be better it LSP stays alive and reports nothing for workspaces without tracey configured. However, daemon doesn't need to be started unless tracey configuration exists.