Skip to main content
Iris Code is one analysis engine with several front ends. Every rule, score and gate decision comes from the same core, so a finding in JetBrains is the same finding in VS Code, on the same line. What differs between hosts is how much interface each editor allows an extension to build. The table below is filled in only where a feature has been verified working in that host. Where a cell says no, it means no today rather than planned.

​
Support matrix

“Forks” means Cursor, Windsurf, VSCodium, Trae and Positron. They install the same extension package as VS Code and behave the same way. Everything in the CLI column of your mind is available everywhere: iris check, iris gate, iris secrets, hooks and CI run from a terminal regardless of which editor you use, and they are the same binary on every platform.

​
One licence, every editor

Signing in once covers every host and the CLI. There is no per-editor licence, no per-editor price, and using the same licence from three editors on one machine counts as one user, not three. VS Code and its forks store the key in the editor’s own secret storage. Everything else reads ~/.iris/credentials, written by iris auth login.

​
Other LSP editors

iris-lsp is a standalone language server that speaks stdio JSON-RPC and carries the whole analysis engine, which is what JetBrains support is built on. It works in Neovim, Helix and anything else that speaks LSP. Native binaries are published for six platforms with checksums, and need no Node installation. Other LSP editors has the download table, the Neovim and Helix configuration, and an honest account of which features do not exist outside a full extension.

​
Reporting a problem

Because the same symptom usually has a different cause per host, say which editor and which version you are using. Report it at iriscode.co/support or email hello@iriscode.co.