Skip to main content
Config Studio is a visual editor at iriscode.co/account/config — pick a preset, tune thresholds and detection toggles, then sync the resulting .irisconfig.json directly to VS Code without touching a file manually. Free users can pick a preset and sync it in one click. Pro users get the full studio with custom thresholds, gate limits, severity overrides, and custom scoring weights.

​
What the studio contains

Config Studio surfaces every configuration option in one place, with a live JSON preview updating as you make changes:
  • Preset selector — choose from Balanced, Strict, Legacy, Security, TypeScript, or switch to Custom mode to edit every value individually.
  • Detection matrix — see at a glance which rule categories are on or off for the selected preset.
  • minHealthScore bar — the gate threshold used by the CLI and hooks is always visible at the top of the card.
  • Gate limits (Pro, Custom mode) — hard caps on secrets count, max file length, max complexity, and smells per file. Leave a field empty to impose no workspace-wide limit.
  • Custom scoring (Pro, Custom mode) — control exactly how many points each finding type deducts from the base 100 health score. See Scoring Weights.
  • Live JSON preview — the right panel updates as you change values, showing the exact .irisconfig.json that will be written.

​
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 account.
2

Choose a preset or switch to Custom mode

Select one of the five presets from the selector, or switch to Custom mode to tune individual thresholds, detections, and gate limits.
3

Click 'Sync to VS Code'

Hit the Sync to VS Code button. Iris 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 extension is installed and that VS Code is running.

​
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
{ "presetId": "balanced" }
All five preset IDs are: legacy, balanced, typescript, strict, security. Commit the file and every developer on the team picks up the same thresholds automatically.

​
Free vs Pro

  • Pick any preset from the selector
  • Preview the resulting JSON in the live preview panel
  • Sync to the Workspace write target
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.