XU XUv0.13.1
中文

Blog / Ecosystem Updates

2026-10-17 · Language Server & Tooling

Xu LSP & vscode-xu: Native Language Server Protocol and Editor Ecosystem

Until recently, editing Xu code relied primarily on TextMate grammar highlighting, while diagnostics required manual command-line invocation of xu check. As part of the 0.8.13 development cycle, Xu introduces its first official, natively self-hosted Language Server Protocol (LSP) daemon: xu-lsp (invoked seamlessly via xu lsp). In tandem, the official VS Code extension repository has been restructured and renamed to vscode-xu.

Pure self-hosted architecture, free from Oracle dependencies

Designed under Xu's sibling tool model, xu-lsp is written entirely in Xu itself. It directly leverages standard library modules including #encoding/json, #xu/format, and #os. Built as an independent binary at bin/xu-lsp, it is dispatched transparently by the compiler via xu lsp, completely eliminating runtime dependencies on the Rust primer (bootstrap oracle).

8 core LSP capabilities ready out of the box

Official extension renamed to vscode-xu

To align with established conventions across the modern programming language ecosystem (such as vscode-go, vscode-rust, and vscode-zig), the official editor extension repository has transitioned from vscode to vscode-xu. The compiler's automated installation scripts and companion repository discovery logic have been updated accordingly.

Editor setup example

// VS Code / Cursor: settings.json
{
  "xu.languageServerPath": "xu",
  "files.associations": {
    "*.xu": "xu"
  }
}

For editors such as Neovim (via nvim-lspconfig) or Helix, configuring the language server command as xu lsp brings the exact same modern IDE capabilities to your terminal workflow.

Getting started

Build the latest binary by running make xu-lsp or make tools in the compiler checkout. Install the freshly packaged vscode-xu extension, reload your editor window, and enjoy native IDE intelligence in Xu.

VS Code / Cursor Guide · Quickstart · vscode-xu repository