Open
Description
Problem
Q clients commonly provide features like Explain
, Optimize
, etc., which require very little UI (they send a canned query about code, and return chat responses). But even though the UI is simple, each Q LSP consumer must build this explicitly.

Proposal
Expose code actions for basic features such as Explain
, Optimize
, etc.
This needs more thought, but at least initially these actions could easily be provided:
Explain
: sends an "explain this code..." query and shows the response in a'window/showMessage'
event.Optimize
: sends an "optimize this code..." query and shows the response in a'window/showMessage'
event.- Use
window/showMessageRequest
to prompt user to select choices from a menu. ref - ...others?
This gives an "instant UI" for any LSP client that supports LSP code actions, without any explicit integration with Q LSP.