Installation

Basilisk is a single Rust binary with no runtime dependencies — no Node.js, no Python interpreter, no package manager required after installation. For every supported editor, the binary comes with the extension; you never install it separately.

Pick your setup:

If you use… Install guide The binary is…
VS Code, Cursor, Windsurf VS Code & Cursor bundled inside the extension
Zed Zed downloaded with the extension on first run
Neovim Neovim downloaded by the plugin on first use
The command line / CI CLI & Package Managers installed via PyPI (uv tool install), Homebrew, Scoop, or a release binary

Editor support (LSP)

Basilisk implements the Language Server Protocol, so any LSP-capable editor can use it:

  • VS Code — official extension, binary bundled → guide
  • Cursor, Windsurf & other VS Code forks — via Open VSXguide
  • Zed — native extension, binary auto-downloaded → guide
  • Neovim — official basilisk.nvim plugin, binary auto-downloaded → guide
  • Helix — native LSP support (point it at a CLI install)
  • Emacs — via eglot or lsp-mode (point it at a CLI install)
  • JetBrains (IntelliJ / PyCharm) — coming soon

Integration status by editor

Where the full Basilisk workflow stands in each editor today — ✅ shipped, 🌗 partial, ⛔️ not yet:

IDE Est. users Deployed LSP Format Profiling Memory Debugging Testing MCP
VS Code 50M MAU ⛔️
IntelliJ / PyCharm 11.4M ⛔️ ⛔️ 🌗 ⛔️ ⛔️ ⛔️ ⛔️ ⛔️
OpenVSX (Cursor, Windsurf etc) 1M+ DAU ⛔️
Emacs ~1M ⛔️ ⛔️ 🌗 ⛔️ ⛔️ ⛔️ ⛔️ ⛔️
Vim ~1/3 of CLI users ⛔️ ⛔️ 🌗 ⛔️ ⛔️ ⛔️ ⛔️ ⛔️
Sublime Text ~1.5% mkt share ⛔️ ⛔️ 🌗 ⛔️ ⛔️ ⛔️ ⛔️ ⛔️
Zed 100Ks/day ⛔️ 🌗 ⛔️
Neovim ~180K 🌗 ⛔️ 🌗 🌗 ⛔️

User estimates link to their sources and are the platforms' own published figures, not our measurements.

Next steps

Once installed, head to the Quick Start to run your first type check, or the Configuration reference to tune Basilisk in pyproject.toml.