Before opening, please confirm:
Operating System
macOS 15.7.3
Kiro Version
1.24.0
Bug Description
When providing a custom LSP (running as a jar), Kiro CLI is not providing the clientInfo as specified by [1].
[1] https://microsoft.github.io/language-server-protocol/specifications/lsp/3.17/specification/#initialize
Steps to Reproduce
- Use some custom LSP provided as a Jar in the workspace LSP config. Our LSP will throw a NPE when
clientInfo is not provided, which discovers this issue.
- Run Kiro CLI with
/code init -f
- Observe via
/code logs that the NPE is thrown and clientInfo is not provided
Even when adding it to the initialization_options - like seen below - the LSP receives a null clientInfo
Example config:
"initialization_options": {
"clientInfo": {
"name": "Kiro CLI",
"version": "1.0.0"
}
}
When we modify the LSP to accept a null clientInfo, then we have no such issue and it works as expected.
Expected Behavior
Kiro CLI should pass clientInfo to the LSP by default according to best satisfy the current spec of the LSP and provide as much info as possible.
Manually providing clientInfo via initialization_options should also work.
Conversation ID
No response
Additional Context
No response
Before opening, please confirm:
Operating System
macOS 15.7.3
Kiro Version
1.24.0
Bug Description
When providing a custom LSP (running as a jar), Kiro CLI is not providing the
clientInfoas specified by [1].[1] https://microsoft.github.io/language-server-protocol/specifications/lsp/3.17/specification/#initialize
Steps to Reproduce
clientInfois not provided, which discovers this issue./code init -f/code logsthat the NPE is thrown andclientInfois not providedEven when adding it to the
initialization_options- like seen below - the LSP receives a nullclientInfoExample config:
When we modify the LSP to accept a null
clientInfo, then we have no such issue and it works as expected.Expected Behavior
Kiro CLI should pass
clientInfoto the LSP by default according to best satisfy the current spec of the LSP and provide as much info as possible.Manually providing
clientInfoviainitialization_optionsshould also work.Conversation ID
No response
Additional Context
No response