Basilisk: A strict Python type checker for any editor

Python’s dynamic nature makes it powerful, but its optional type system often leads to overlooked issues—especially when AI generates code. When one developer found Pylance’s gradual typing inadequate for their AI agent project, they took matters into their own hands and created Basilisk, a strict type checker designed to work seamlessly in any editor.

The limits of Pylance’s gradual typing

Python’s type system is robust, yet tools like Pylance default to permissive settings that allow untyped code to slip through unchecked. Functions without annotations, implicit Any types, and a patchwork of opt-in strictness rules create an environment where type hints are treated as optional suggestions rather than enforceable contracts. For a tool generating Python code, this approach is fundamentally flawed—your types shouldn’t be "vibes."

Beyond its lax enforcement, Pylance’s proprietary nature ties users to Microsoft’s official VS Code build, excluding those who prefer alternatives like Cursor, Windsurf, or Zed. Even within VS Code, configuring the type checker to analyze all files proved inconsistent, often limiting error detection to the active file despite extensive settings tweaks.

Building an open alternative: Basilisk

Frustrated by these constraints, the developer behind the Nimble Agent project created Basilisk, an open-source Python language server, type checker, debugger, and profiler built in Rust. Unlike Pylance, Basilisk ships as a single binary with no dependencies on Node, Python, or Microsoft tools—making it portable across any editor that supports the Language Server Protocol (LSP).

The core philosophy is simple: strict by default. There’s no toggle for permissive mode, no --basic flag, and no global override to disable checks. This mirrors the philosophy of Rust’s borrow checker or TypeScript’s strict: true—where strictness isn’t optional but expected. Basilisk enforces 151 diagnostics out of the box, ensuring type safety without compromise.

A complete Python dev experience in one tool

While strict type checking is Basilisk’s foundation, its ambition extends far beyond diagnostics. The tool consolidates a full Python development workflow into a single Rust binary:

• Type checking and inference – Enforces strict typing with full PEP 484 conformance
• Debugging – Embeds debugpy with zero configuration required
• Profiling – Integrates py-spy for real-time performance insights
• Test exploration – Supports pytest and unittest with coverage overlays
• Refactoring tools – Provides extract, inline, move-to-file, rename, and signature changes
• Autofixes and formatting – Leverages Ruff for efficient code improvements

Because Basilisk operates through LSP, it delivers the same experience in any editor—VS Code, Cursor, Windsurf (via Open VSX), Zed, or Neovim. Install once, and the full toolkit follows you, regardless of your preferred development environment.

Why strict typing matters for AI-generated code

AI agents like Nimble Agent generate Python code dynamically, making type safety critical. Loose type checkers risk propagating undefined behavior, leading to runtime errors and maintenance nightmares. Basilisk eliminates this risk by treating type annotations as mandatory, ensuring generated code adheres to contracts from the outset.

The project started as a personal necessity but evolved into a broader solution for Python developers seeking consistency. With its Rust-based architecture, incremental checking, and editor-agnostic design, Basilisk represents a new standard for Python tooling—one where strictness isn’t a feature toggle but a baseline requirement.

The future of Python tooling

Open-source tools like Basilisk highlight a growing demand for stricter, more reliable Python development environments. As AI-assisted coding becomes ubiquitous, the need for robust type enforcement grows alongside it. Whether you’re a solo developer or part of a large team, tools that prioritize correctness over convenience are becoming indispensable.

For those tired of type hints being treated as optional, Basilisk offers a compelling alternative—one where your code’s integrity isn’t left to chance.