Skip to main content
Config Studio is a visual editor for .irisconfig.json, so you can configure Iris Code without knowing the key names. It lives at iriscode.co/account/config. Choose a preset, set your naming rules, and watch the JSON build up alongside your changes, then sync it to your editor. Presets, naming and the package guard are free; Pro adds custom thresholds, gate limits, scoring and severity overrides. In VS Code, run Iris Code: Open Config Studio from the Command Palette to open this page. The editor does not write a config until you review the sync diff and confirm it.

​
What it covers

Every setting that counts as a shared team standard, one section each, with a live preview of the file you will get: On the Free plan, Pro sections are shown but locked. A Free config uses its preset for everything except file naming and the package guard, so a value typed into a locked field would be ignored by your editor. The preview on the right is the exact .irisconfig.json that Copy, Download and sync hand over. On a narrow screen it sits below the editor.
Sync replaces the settings the studio controls and keeps the rest of your file.A few settings aren’t in the studio on purpose, because they describe one project or one machine rather than a shared standard: ignoreFiles, ignoreFunctions, testConvention, sidebarFontSize, teamProjectId, and the package guard’s allow list, which holds one repository’s reviewed exceptions. When your current file sets any of them, sync carries them over unchanged. They appear in the diff, and VS Code also lists them when the sync finishes.Everything else comes from the studio. A setting the studio controls but you left empty, such as a gate limit, is removed from the file.A diff is shown before anything is written. If your current file cannot be read as JSON, nothing can be carried over, and the editor asks before replacing it.

​
Syncing to VS Code

The sync flow is designed to never write silently - every sync opens a diff in VS Code first so you can review the exact changes before anything is committed to disk.
1

Open Account → Config in the browser

Navigate to iriscode.co/account/config while signed in to your Iris Code account.
2

Choose a preset or switch to Custom mode

Select one of the six presets on the Overview section, or Custom to start from an empty config. On Pro, change any setting in the sections that follow; the preset stays as the base for everything you leave alone.
3

Click 'Sync to VS Code'

Hit the Sync to VS Code button. Iris Code generates a short-lived one-time token and opens VS Code via a deep link.
4

VS Code opens a diff preview

VS Code opens and shows a diff preview of the exact changes that will be made to your .irisconfig.json.
5

Confirm or cancel

Confirm the write to apply the changes - or cancel to leave your config exactly as it was. Nothing is written silently.
The sync token is short-lived and single-use. If VS Code doesn’t open within a few seconds, check that the Iris Code extension is installed and that VS Code is running.

​
Other editors: sync with a code

The Sync to VS Code button opens a vscode:// deep link, which only VS Code itself claims. JetBrains IDEs have no such scheme, and VS Code forks register their own - so in Trae, Positron, or a JetBrains IDE that link would open VS Code, or nothing at all. For those editors, click Get a sync code instead. You get a one-time code to paste into your editor, and the rest of the flow is identical - same diff, same confirmation, same write targets.
Tools → Iris Code → Sync Config from Dashboard, then paste the code.Iris Code shows a real diff against your current config and writes only after you confirm. The write goes through the IDE, so it is undoable and analysis restarts automatically.
The code can only be redeemed once. If you cancel at the diff, generate a new code rather than reusing the old one.

​
Write targets

When you click Sync to VS Code, choose where the config is written:

Workspace

Writes .irisconfig.json to the project root. Available to all users - Free and Pro. Commit it and the whole team runs the same config automatically.

Global default

Pro only. Writes to your personal default config path so every new project on your machine starts with the same settings. Useful for personal standards you maintain across repositories.
For monorepos, sync a Workspace config to each package root that needs different thresholds. The extension resolves config by walking up the directory tree - the nearest .irisconfig.json wins.

​
Using a preset without Config Studio

You don’t need the dashboard to use a preset. Create a .irisconfig.json at your project root and add one line:
.irisconfig.json
All six preset IDs are: legacy, balanced, typescript, strict, security, ai-assisted. Commit the file and every developer on the team picks up the same thresholds automatically.

​
First-time setup from the CLI

iris init creates a commented Balanced .irisconfig.json and the default AGENTS.md rules file, then refreshes Iris Code blocks if either file already exists. It also installs the pre-push hook for an active Pro licence. On Free, it names that hook step as unavailable and continues with the safe setup steps. The command is safe to run again. It preserves an existing config and only refreshes the blocks Iris Code owns in existing rules files.

​
Free vs Pro

  • Pick any preset from the selector
  • Preview the resulting JSON in the live preview panel
  • Sync to the Workspace write target
  • Configure workspace-wide fileNaming and fileNamingScope, then add ordered path rules
  • Set the package guard policy, apart from prePush
The preset values are fixed and cannot be overridden locally - editing threshold fields in the generated file produces a yellow warning squiggle in the editor.