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
New Zed 1.1.5 code lens items don't do anything on click yet #286
This is a feature request. The new Zed 1.15 code lens items are starting to show up for me. But I don't yet understand how/if I can make clicking them trigger actions.
Here's an RSpec example:
Hopefully we can set these up to do the "right" thing by default, or at least make it more discoverable how to wire them up via tasks, etc.
changed the title [-]New Zed 1.1.5 code lens items don't do anything[/-][+]New Zed 1.1.5 code lens items don't do anything on click yet[/+]on May 6, 2026
Hi, yeah, unfortunately, Ruby LSP code lenses do not work due to technical limitations in Extensions API. Code lenses from extension LSPs can render, but code lenses whose commands are custom client-side commands do not work today. Ruby LSP uses client-side commands.
Zed handles client commands through the in-process LspAdapter::client_command hook, used by built-in adapters like Rust and Go to map commands such as rust-analyzer.runSingle or gopls.run_tests into local editor actions/tasks. The extension LSP adapter does not implement this hook, and the Extensions API does not expose any way for extensions to register client command handlers. Fixing this likely requires adding extension API support for declaring/handling client commands, or a generic command mapping path for extension-based LSP adapters.
Activity
[-]New Zed 1.1.5 code lens items don't do anything[/-][+]New Zed 1.1.5 code lens items don't do anything on click yet[/+]vitallium commentedon May 6, 2026
Hi, yeah, unfortunately, Ruby LSP code lenses do not work due to technical limitations in Extensions API. Code lenses from extension LSPs can render, but code lenses whose commands are custom client-side commands do not work today. Ruby LSP uses client-side commands.
Zed handles client commands through the in-process
LspAdapter::client_commandhook, used by built-in adapters like Rust and Go to map commands such asrust-analyzer.runSingleorgopls.run_testsinto local editor actions/tasks. The extension LSP adapter does not implement this hook, and the Extensions API does not expose any way for extensions to register client command handlers. Fixing this likely requires adding extension API support for declaring/handling client commands, or a generic command mapping path for extension-based LSP adapters.nertzy commentedon May 6, 2026
Makes sense and I was expecting something like this to be the case. Thanks for the context.