IDE

IDE support for kis.ai is a language server for the platform’s YAML. Everything you declare — entities, workflows, routes, pipelines, agents, policies, service and block configuration — gets validated as you type, completed from the real schema, and cross-referenced.

Because so much of building on kis.ai is writing YAML, this is the difference between finding a schema error in your editor and finding it in a failed deploy.

What it gives you

Feature	What it does
Diagnostics	Real-time validation as you type
Completion	Context-aware autocomplete for fields and values
Hover	Documentation for the field under the cursor
Go to definition	Jump to a referenced resource
Document symbols	Outline view and symbol navigation

Completion is schema-driven rather than a word list, so it proposes the fields that are legal at that position in that kind — and it will not propose a field that does not exist, which is the failure mode of generic YAML tooling.

Supported kinds

Every kis.ai YAML kind, including:

Definitions — Entity, Workflow, Route, Pipeline, Agent, Policy

Configuration — ServiceConfig, DatabaseConfig, IAMConfig, JobConfig, NotifyConfig

Go-to-definition works across kinds. A route referencing an entity, or a workflow referencing a job, navigates to the declaration — which is how you keep your bearings once a product’s YAML outgrows a single file.

Installing

VS Code

ext install kisai.kis-spec

The extension detects its environment and connects accordingly:

• VS Code Desktop — spawns the language server locally over stdio
• VS Code Web — connects to a hosted language server over WebSocket

Web support means a browser-based editor gets the same validation as a local one, with no local toolchain to install.

Other editors

The server speaks the Language Server Protocol, so any LSP-capable editor can drive it. Point your editor’s LSP client at the binary and associate it with kis.ai YAML files.

Next

• Operations — running the server, versioning and troubleshooting