Skip to main content
Some editors, including Cursor and Windsurf, are built from VS Code and can run its extensions. They use the same Iris Code extension package and support the same features as VS Code. This page explains where to install it and how to open it in each editor.

Install

Most forks cannot reach the Visual Studio Marketplace and use Open VSX instead. Search for Iris Code in the Extensions view; if it is not found, install the .vsix directly:
1

Download the package

Get the latest .vsix from iriscode.co/download or from Open VSX.
2

Install from disk

In the Extensions view, open the ... menu and choose Install from VSIX.

Sign in

Sign-in works in every fork. After you sign in, the browser hands you back to your editor through a link that starts with the editor’s own name (cursor://, windsurf://, trae:// and so on). Iris Code checks where that link leads rather than which editor name it starts with, so a fork does not need to be on any approved list for sign-in to finish. If sign-in does not return you to your editor, run iris auth login in a terminal instead. It writes ~/.iris/credentials, which every editor can read.

AI-assisted editors specifically

Cursor, Windsurf and Trae can generate a lot of code quickly, which is the situation Iris Code is designed for. Two features are worth turning on straight away:
  • Review My Changes scores only what changed, so a large generated diff is reviewed as a unit rather than being averaged into a whole-project score.
  • The pre-push git hook, a check that runs when you push, stops generated code below your standard from leaving the machine. That matters more when there is more code than anyone reads line by line.
Iris Code does not read your assistant’s suggestions and does not try to tell whether code was written by a person or an AI model. It analyses what is in the file.

Analytics

Each fork is recorded separately in usage analytics, as cursor, windsurf, trae and so on, so support and roadmap decisions reflect where Iris Code is actually used. The events are counts only, and never include source code, file paths or findings.