# Configuration Radforge builds plans from files in your repository and CLI options. There is no separate hosted configuration for mutation planning. ## Project detection `rad init` and `rad doctor` detect supported TypeScript and Python workspaces. Use `--repo-root` to point to another Git working tree. Use `--language` to choose `auto`, `mixed`, `typescript`, or `python` during setup and diagnosis. ## Ignore rules `rad changed --exclude ` removes matching source files from mutation analysis. Repeat the option to add more patterns. Radforge also reads `.muttignore`. Ignored files are not mutated, but tests can still import them as dependencies. ## Bounds and fallbacks - `--budget ` limits total candidates in the generated plan. - `--dry-run` prints a plan instead of submitting it. - `--allow-broad-tests` allows a broad test set when Radforge cannot select a smaller one. - `--json` selects machine-readable output where the command supports it. ## Scope files and plan artifacts A scope file lists source paths relative to the repository root, one path per line. A plan is generated JSON. Do not edit it by hand. Before submission, the CLI checks its format against the current server version. The [CLI reference](/reference/cli/rad/) is generated from `rad --help` and lists the options available in this source revision.