Install
1
Install from the Marketplace
Settings > Plugins > Marketplace, search for Iris Code, install.
2
Restart the IDE fully
Close and reopen the IDE, rather than only reloading the plugin. The note below explains why.
3
Open the tool window
View > Tool Windows > Iris Code, or Tools > Iris Code: Open Panel.
Sign in
Use Tools > Iris Code: Sign In, or runiris auth login in a terminal. Both write the same ~/.iris/credentials file, so one sign-in covers the plugin, the CLI (the iris terminal commands), your hooks and CI.
What you get
The tool window is the same panel as the VS Code sidebar, rendered by the same code: Home, Review, Improve, Explore and Configure, with File, Folder, Workspace, Findings and TODOs review scopes, gate preview, trends, and every table. Panel navigation explains where each tool lives. The tables open as editor tabs. Diagnostics (underlines in the code), hover details, code lens hints and quick fixes come through LSP4IJ. The panel works with the IDE itself:- clicking a file opens it at the right line
- “Update dependency” runs in a real terminal
- duplicate pairs open in the IDE’s own diff viewer
- installing a hook asks before changing your repository
Ctrl+Shift+A), including Iris Code: Refactor Plan. They are all named Iris Code: ..., so typing “iris” finds every one of them.
Refactor plan in the File, Folder or Workspace tab opens the Refactor Playbook panel. There you can plan a refactor, apply approved mechanical fixes with Undo, get instructions for a coding agent, and check the result against the saved starting point (the baseline).
Planning one file is Free; new folder and workspace plans use project access. The Hooks section also offers the always-Free package guard and the included finish verification.
What it does not have
- No detached panel. The tool window can be widened or floated using the IDE’s own controls.
- No guided onboarding tour. These docs cover the same ground.
- No project-view badge for file-naming violations. The violations still appear in the Problems panel and the naming table.
- No push-blocked counter panel.
Reporting a problem
When an Iris Code action fails, such as a workspace or folder scan, the IDE notification offers two buttons:- Show details shows the error with the time, the action and the stack trace. The full record is also written to the IDE log (Help > Show Log in Explorer, or Show Log in Finder on macOS).
- Report problem opens a report form on iriscode.co with a short summary already filled in: the Iris Code and IDE versions, your operating system, the action and the error message.
~ and <workspace>. The summary travels in the part of the link that browsers do not send to a server, so nothing reaches Iris Code until you review it, add what you were doing and press Send report.