UAT: LSP runtime ignores transport and initialization options from registry #7956

New issue

Open

opened 2026-04-12 08:33:11 +00:00 by HAL9000 · 3 comments

HAL9000 commented

2026-04-12 08:33:11 +00:00

Owner

Summary

What was tested: Code analysis of LspLifecycleManager.start_server and LspClient.initialize handling of registry configuration fields
Expected behavior: docs/specification.md §LSP Integration → LSP Registry table (lines 20696-20717) requires the runtime to honour transport, initialization, and workspace_settings when starting servers
Actual behavior: start_server always constructs StdioTransport and never inspects config.transport; it also calls client.initialize(workspace_path) without forwarding config.initialization, and there is no workspace/didChangeConfiguration call anywhere to apply config.workspace_settings, leaving those spec-required hooks inert
Impact: TCP-hosted servers, custom initializationOptions, and workspace configuration cannot be used even though the registry schema exposes them
Type/Bug

Evidence

Spec: docs/specification.md lines 20696-20717 (transport, initialization, workspace_settings fields)
Implementation: src/cleveragents/lsp/lifecycle.py lines 102-123 always use StdioTransport; src/cleveragents/lsp/lifecycle.py line 112 passes only workspace_path to client.initialize; no code path sends workspace/didChangeConfiguration after initialization

Suggested Fix

Support both stdio and TCP transports, pass config.initialization into client.initialize, and send workspace/didChangeConfiguration with config.workspace_settings after the handshake

Automated by CleverAgents Bot
Supervisor: UAT Testing Pool | Agent: uat-test-pool-supervisor

## Summary - **What was tested**: Code analysis of `LspLifecycleManager.start_server` and `LspClient.initialize` handling of registry configuration fields - **Expected behavior**: docs/specification.md §LSP Integration → LSP Registry table (lines 20696-20717) requires the runtime to honour `transport`, `initialization`, and `workspace_settings` when starting servers - **Actual behavior**: `start_server` always constructs `StdioTransport` and never inspects `config.transport`; it also calls `client.initialize(workspace_path)` without forwarding `config.initialization`, and there is no `workspace/didChangeConfiguration` call anywhere to apply `config.workspace_settings`, leaving those spec-required hooks inert - **Impact**: TCP-hosted servers, custom initializationOptions, and workspace configuration cannot be used even though the registry schema exposes them - **Type/Bug** ## Evidence - Spec: docs/specification.md lines 20696-20717 (transport, initialization, workspace_settings fields) - Implementation: src/cleveragents/lsp/lifecycle.py lines 102-123 always use `StdioTransport`; src/cleveragents/lsp/lifecycle.py line 112 passes only `workspace_path` to `client.initialize`; no code path sends `workspace/didChangeConfiguration` after initialization ## Suggested Fix - Support both stdio and TCP transports, pass `config.initialization` into `client.initialize`, and send `workspace/didChangeConfiguration` with `config.workspace_settings` after the handshake --- **Automated by CleverAgents Bot** Supervisor: UAT Testing Pool | Agent: uat-test-pool-supervisor

HAL9000 added the

State

Unverified

label

2026-04-12 18:32:29 +00:00

freemo added the

labels

2026-04-12 18:35:07 +00:00

HAL9000 referenced this issue

2026-04-12 19:32:29 +00:00

[AUTO-GROOMER] Backlog Grooming Report (Cycle 1) #8009

HAL9000 added

and removed

labels

2026-04-14 05:57:38 +00:00

HAL9000 commented

2026-04-14 05:57:38 +00:00

Author

Owner

✅ Verified — UAT bug: LSP runtime ignores transport/initialization options. MoSCoW: Should-have. Priority: Medium.

Automated by CleverAgents Bot
Supervisor: Project Owner | Agent: project-owner-pool-supervisor

✅ **Verified** — UAT bug: LSP runtime ignores transport/initialization options. MoSCoW: Should-have. Priority: Medium. --- **Automated by CleverAgents Bot** Supervisor: Project Owner | Agent: project-owner-pool-supervisor

HAL9000 commented

2026-04-14 06:10:58 +00:00

Author

Owner

✅ Verified — UAT bug: LSP runtime ignores transport/initialization options. MoSCoW: Should-have. Priority: Medium.

Automated by CleverAgents Bot
Supervisor: Project Owner | Agent: project-owner-pool-supervisor