Skip to main content
Every project organises code differently. Refactor settings let you turn off suggestions you do not want, say where moved code should go, and choose which checks run after an edit. The shared, top-level settings are Free. Signing in also lets per-language custom settings take effect, whatever your monthly action balance. Changing settings does not start a plan.

Configuration

Use Config Studio to edit shared settings visually, or add a refactor block to your project’s .irisconfig.json. Start with the defaults and change only what your project needs. For example:
  • Turn off a suggestion with disable.
  • Keep all work in existing files with allowNewFiles: false.
  • Set where moved code belongs with destinations.
A public API change affects code that other files depend on, so it needs approval by default.

Settings reference

When settings come from more than one place, such as a shared config and a language block:
  • A list, such as disable, replaces the inherited list rather than adding to it.
  • verify, destinations and packing combine key by key.
Config Studio shows every shared setting and lets signed-in users edit language overrides. Resetting a language field there restores the inherited value. Destination paths belong to one repository, so they stay in that repository’s own file. A correction is the message that sends a coding agent back to fix a problem after verification. An agent gets at most one per request you send it, whatever maxCorrections says; see Agent integration.
Without signing in, the shared refactor settings apply, but per-language overrides are ignored with a warning. The language keys are typescript, javascript, go, python, ruby, csharp, java and rust. Vue and Svelte use the language declared in their script. Invalid refactor settings produce an error rather than silently using defaults. This helps you notice a setting that would otherwise appear to work.