Run your first diagnostics
After Pi trusts the project, call lsp_diagnostics with a workspace-relative file path:
lsp_diagnostics({"filePath":"src/index.ts"})The legacy filePath form checks one supported regular file. A clean file returns an empty diagnostic list. The built-in TypeScript route covers .ts, .tsx, .js, .jsx, .mjs, .cjs, .mts, and .cts.
If no server starts
Section titled “If no server starts”Run:
/lsp status/lsp policyThe typescript route is the only published automatic-install route; the main branch adds unreleased vue, vscode-json-language-server, and yaml-language-server routes. Global policy must leave the selected route enabled, allow automatic installation, and permit network: "auto"; the current platform must also match a verified row. The extension does not install candidate routes or manual routes.
If the result is untrusted_project, trust the project in Pi. If it is server_unavailable, check troubleshooting before changing configuration.
Next step
Section titled “Next step”Use batch diagnostics to scan selected directories, or see the tool reference for navigation and mutation tools.