Skip to main content
Version: 0.37.2

Configuration

agnix works with zero configuration. To customize, add .agnix.toml to your project root.

Example

target = "ClaudeCode"
tools = ["claude-code"]
max_files_to_validate = 10000
locale = "en"

[rules]
disabled_rules = []

Options

OptionTypeDefaultDescription
targetstringGenericLegacy single tool focus: Generic, ClaudeCode, Cursor, Codex, Kiro
toolsstring[][]Multi-tool targeting. Overrides target. Use values like claude-code, cursor, codex, kiro, github-copilot, cline, opencode, gemini-cli, amp, roo-code, windsurf, generic.
severitystringWarningMinimum severity level: Warning, Error, or Info
max_files_to_validateint10000Maximum files to scan
localestring"en"Output locale
[rules].disabled_rulesstring[][]Rule IDs to skip (e.g. ["CC-MEM-005"])
[rules].disabled_validatorsstring[][]Validator names to skip
[files]tabledefault excludesInclude or exclude non-standard files
[[overrides]]table array[]Per-file disabled rule overrides

CLI flags

CLI flags override .agnix.toml values:

# Target a specific tool
agnix --target cursor .

# Apply fixes
agnix --fix .

# JSON output for CI
agnix --format json .

# SARIF output for GitHub Code Scanning
agnix --format sarif .

# Strict mode
agnix --strict .

--strict, --fix, --fix-safe, --fix-unsafe, --dry-run, --show-fixes, and --format are CLI flags, not .agnix.toml keys.

Full reference

For the complete configuration specification, see docs/CONFIGURATION.md in the repository.