.irisconfig.json file holds your project’s Iris Code settings: what to check, and the limits (thresholds) code must meet. Commit it with your code so everyone gets the same results in the editor, on the command line and in automated checks such as CI.
For each file, Iris Code uses the nearest .irisconfig.json in its folder or the folders above it. That lets separate packages in a large repository have different settings.
To look up one setting by name, such as gateScope or minHealthScore, see All configuration keys, which lists every key with its values and default.
This page lists settings you can change, not the rules Iris Code checks. It mixes gate
limits, thresholds, scoring weights, severity overrides and rule ids, so counting the
entries here does not give the number of rules. For that, see the
accuracy benchmark, which publishes every measured rule
per language.
Priority order: nearest folder
.irisconfig.json → workspace root .irisconfig.json → personal default → VS Code settings → built-in defaultsComments, autocomplete and hover help
.irisconfig.json is JSONC, which is JSON that allows // comments. Every config Iris Code writes includes comments explaining each setting, so you can read the file without this page open.
Generated configs also open with a $schema line:
Config presets (Free + Pro)
A preset is a ready-made set of limits. Rather than choosing every threshold yourself, start from one: addpresetId, commit the file, and the whole team uses the same settings.
.irisconfig.json
strict, balanced, legacy, security, typescript, ai-assisted.
The ai-assisted preset sets stricter limits for teams reviewing a lot of AI-assisted code. It limits duplicate blocks and suppressions, but does not impose a naming convention.
Configs that Iris Code generates explain each active check and gate limit with a one-line comment. Settings that depend on your team, such as naming conventions, ignore lists and per-language settings, are included as commented-out examples until you choose them.
- Without sign-in
- Signed in
Iris Code uses the preset’s values exactly as shipped. Without signing in, changes you make to threshold fields in the file are ignored, and the editor marks them with a yellow warning squiggle. The preset built into Iris Code decides the values, not the file on disk.
Full custom configuration
For complete control, you can write out every setting. Every key is optional, so include only the ones you want to change..irisconfig.json
Thresholds
These keys set the size limits, such as how long a function may be, that produce warnings in the editor and sidebar.Detection toggles
Turn individual kinds of check on or off, without removing findings from the sidebar entirely.Display
Control what Iris Code shows in the editor.
Inline diagnostics are the squiggles under code and the entries in the Problems panel. Once
enableInlineDiagnostics is true, the inlineDiagnostics object turns individual categories on or off.
Gate thresholds
A gate is the pass or fail decision made when your code is checked by the CLI (theiris terminal commands) or the git pre-push hook. These keys set its limits. A file or workspace that goes over a limit fails the check.
Ignore rules
Scoring weights
healthScoreWeights, available when you are signed in, lets you override how many points each finding type subtracts from the base 100 health score. See Scoring Weights for the full reference and examples.
Per-language config
A repository that mixes languages rarely wants one set of limits for everything. For example, you may want to allow 500-line Python modules while keeping TypeScript files to 300 lines. Thelanguages block changes per-file settings separately for typescript, javascript, go, python, ruby, csharp, java, and rust files. Anything you do not set there uses the main settings.
.tsx files count as TypeScript and .jsx / .mjs / .cjs as JavaScript.
A ruby block also governs the extensionless Ruby files Iris Code reads, such as Gemfile and Rakefile; a csharp block governs both .cs sources and .csproj project files; and a java block governs both .java sources and the .properties files Iris Code reads for credentials.
fileNaming, its ordered overrides, and languages.*.fileNaming are Free. Path overrides are checked in order and the last match wins. When no path rule matches, the language’s own naming policy is used if it has one, for compatibility with older configs; otherwise the top-level convention applies. Top-level ignore patterns always apply.
When you are signed in, you can also set per-language thresholds, healthScoreWeights, severityOverrides and gate limits. These keep applying to the file checks you can run after your monthly project allowance is used up. Setting a threshold does not give you paid enforcement or start a scan.
Set top-level fileNamingScope to "new-files" (default) or "all". A matching path rule can override it with scope; a language’s naming policy can do the same when no path rule matches. See File naming conventions for the full order of rules, how the baseline is used, suggestions, ignore patterns and exemptions.
Some settings only make sense for the whole project, so they are refused inside a language block with a warning: limits that count across the whole scan (minHealthScore, gateMaxSecrets, gateMaxSecuritySmells, gateMaxDuplicateBlocks, gateMaxNamingViolations, gateMaxParseErrors), presetId, and the enable* switches.
Which setting applies to a file is worked out in one shared place, so the sidebar, CLI, git hook, build hook and CI always agree. The sidebar’s file tab shows the language setting in use next to where the config came from (for example “Workspace config · Python override”). iris gate prints the limit that applied to each failing file, plus a “Per-language overrides active” note.
An unknown language key, such as an elixir block written for a newer Iris Code release, produces a warning and is skipped, so a newer config does not break an older installation.
A per-file gate limit set only inside a language block still applies to files of that language, even when no top-level limit is set.
Package guard (Free)
A package is code written by someone else that your project uses. ThepackageGuard block sets what the package guard stops when a coding agent, iris install or a push adds one. It is a safety policy rather than a threshold, so it works on every plan and presets do not restrict it.
onUnchecked("warn"or"block") decides what happens to a package the guard could not check.blockSeveritysets the lowest severity of known security problem (advisory) that blocks. A report that a package is malicious always blocks.minimumReleaseAgeDaysblocks versions released fewer than that many days ago.- Each
allowentry needs areason, or it is ignored and reported as an error. prePush: trueadds a check of your lockfile, the file listing exact package versions, to the git hook. This needs Pro.
Refactor policy (Free)
Therefactor block controls suggested fixes, where moved code should go and the checks run afterwards. Top-level settings work on every plan, whatever your preset. Signing in also lets you set them per language; saving them does not use a project action.
refactor block with mistakes in it is reported, rather than quietly replaced with defaults. Refactor configuration lists every key and its default.
Severity overrides
Severity is how serious a finding is reported as. Use theseverityOverrides object to change it for a kind of warning in this project. Each key accepts "error", "warning", or "info".
Packed code integrity (Free)
Squeezing several statements onto one line can sneak a file under a length limit. Verification integrity reports this ascode-packed. codePackedThreshold sets how many newly joined statements a file must have before that is reported.
It defaults to 3 and accepts whole numbers of 1 or more. Every preset and language uses the same top-level value; a languages block cannot change it.
rules-loosened.
The rule warns by default. severityOverrides["code-packed"]: "error" makes it block pushes and CI. Use "info" for the quietest severity, and ignoreFiles for generated files.
Agent handoff
MCP is a connection that lets a coding agent call Iris Code’s tools.agentHandoff is a Free true/false setting. Set "agentHandoff": false to turn off the Iris Code MCP tools that read this repository, for everyone using it.
It is read fresh on every tool call, including for Free users. true, or leaving the key out, adds no restriction for the repository and cannot loosen a rule set by your organisation. The package guard stays available either way.
See Team governance.
Schema graph (Free)
schemaGraph controls the Schema graph, the diagram of your database tables. It is on by default and skips files in your ignore rules. Presets do not affect it, so a Free preset never removes the sources you chose.
sources and Iris Code finds your schema files automatically. To choose them yourself, list each source (prisma, sql, drizzle, django, rails or diesel) with its paths, relative to the project. dialect applies only to SQL and accepts postgres, mysql or sqlite.
Set enabled to false to turn the schema graph off. Invalid source paths are refused rather than read from outside the project.