Operations
Transports
Section titled “Transports”The server supports two transports, chosen by the client:
| Transport | Used by | Notes |
|---|---|---|
| stdio | VS Code Desktop, most LSP clients | The server runs as a local child process |
| WebSocket | VS Code Web | The server is hosted; the browser connects to it |
For the hosted path, one server instance serves many editors. Size it like any other interactive service — the load is bursty, driven by typing, and latency is what users perceive.
Keeping schemas current
Section titled “Keeping schemas current”The value of the server is that it validates against the real schema. That means its schema set has to track the platform version your product targets.
A server older than the platform will flag valid new fields as errors; a server newer than the platform will accept fields the platform rejects. The second is worse, because the failure moves from your editor to your deploy.
Pin the extension or binary version alongside the platform version you build against, and upgrade them together.
Troubleshooting
Section titled “Troubleshooting”No diagnostics at all. The file is probably not being recognised as a kis.ai YAML kind.
Check the kind: field is present and spelled correctly — recognition keys off it.
Completion proposes nothing. Usually the same cause. It can also mean the document has a parse error earlier in the file: the server cannot offer position-aware completion inside YAML it cannot parse, so fix the first diagnostic and the rest usually follow.
Go-to-definition does not resolve. The referenced resource is not in the workspace the server indexed. Cross-file navigation is scoped to the open workspace, so a reference to a definition in another repository will not resolve.
Diagnostics disagree with CI. Almost always a version skew between the server’s schemas and the platform version CI validates against. Check both before debugging the YAML.