katari-vscode

VSCode extension for the Katari language: syntax highlighting (TextMate grammar) + language client (LSP).

Features

.ktr syntax highlighting.
Hover types, go-to-definition, find-references, completion, and diagnostics — all served by the katari-lsp server.
Command-palette commands that drive the katari CLI.

Commands

All "Katari: …" entries in the command palette. The CLI-backed commands run in one shared Katari integrated terminal (so interactive flows — like apply prompts — work), against the nearest project: the extension walks up from the active editor's file (falling back to the workspace folders) to the closest katari.toml and passes it as -C <dir>.

Command	Runs
Katari: Check project	`katari check`
Katari: Build project	`katari build`
Katari: Apply (deploy) project	`katari apply`
Katari: Generate MCP tool bindings	`katari mcp pull --url … --out …` — prompts for the server URL and a `.ktr` output path (defaulting into `src/`), then opens the generated file
Katari: Restart language server	Stops `katari-lsp` and starts it again from the current settings (picks up a changed `katari.server.path`)

An MCP server that uses OAuth is authorized by answering the OAuth authorization escalation the runtime raises when a program first needs the credential — from the admin console or katari answer. There is no login command or stored env key to manage.

The CLI is resolved like the server, minus the bundled tier: an explicit katari.cli.path setting wins, else katari on PATH (no CLI is bundled in the VSIX — stack install katari in a from-source checkout, or a release binary).

The bundled language server

A published (release-page) install is platform-specific: each VSIX bundles the matching katari-lsp binary at bin/katari-lsp, so there is nothing to install separately. The extension resolves the server in three tiers (see src/extension.ts):

an explicit katari.server.path setting (your own build — the override);
the bundled bin/katari-lsp (a release install);
katari-lsp on PATH (a from-source checkout — see below).

CI builds the per-platform VSIXes in release-vsix.yml, pulling each binary from the katari-lsp-<version>-<platform>.tar.gz tarballs that release-katari.yml attaches to the GitHub Release.

Setup (from source)

Two ways to run the extension against a local checkout:

PATH (simplest for iterating on the LSP): install the server on PATH, then launch a dev host — no binary is bundled, so tier 3 applies.
```
stack install katari-lsp          # copies to ~/.local/bin
pnpm --filter katari-vscode run build
code --extensionDevelopmentPath=$PWD/typescript/vscode
```
Re-run stack install katari-lsp after changing the LSP (a bare stack build only updates .stack-work, not ~/.local/bin).

Bundled (to exercise the packaging path): copy the locally built binary into bin/ first, so tier 2 applies exactly like a release install.

stack build katari-lsp
pnpm --filter katari-vscode run server:copy   # → typescript/vscode/bin/katari-lsp
pnpm --filter katari-vscode run package:local # builds a universal .vsix with the binary

Then open any .ktr file (e.g. the e2e samples). If katari-lsp cannot be found, set an absolute path via the katari.server.path setting.

Manual smoke test checklist

Hover over a function name → shows type-info popup.
F12 on a name → jumps to its definition.
Shift+F12 → lists all references.
Ctrl+Space → completion popup with locals + top-level callables.
Introduce a typo → red squiggle appears.
Fix it → squiggle disappears.

Katari