# request_change Repository Configuration
This page documents the per-repository configuration options for the `request_change` tool.
Location
- `config/request_change.toml` (preferred when available)
- `config/request_change.json` (fallback)
Fields
- `allow`: list of glob patterns to explicitly permit (e.g., `["src/**"]`).
- `deny`: list of glob patterns to explicitly deny (e.g., `["dist/**","**/*.png"]`).
- `summary_allowed_regex` (optional): a regex string that defines the allowed characters for the agent-provided `summary`. If omitted, a permissive default is used (letters, digits, common punctuation and whitespace).
- `redundancy` (optional): object controlling n-gram redundancy checks. Example fields:
- `ngram_max_pct`: maximum fraction of summary tokens that may be covered by a repeated n-gram (default: 0.2)
- `ngram_max_count`: absolute maximum occurrences of any single n-gram (default: 3)
Semantics
- An explicit `allow` pattern matching a path will permit that path even if a broader deny pattern also matches.
- A deny pattern will block a path unless an explicit allow matches first.
- If no config file is present, safe defaults are used: a permissive allow (`**/*`) and a conservative deny list for common binary or generated artifacts (images, archives, `dist/`, `build/`, etc.).
Examples
JSON:
```json
{
"deny": ["dist/**", "node_modules/**", "**/*.png"]
}
```
TOML:
```toml
allow = ["src/**"]
deny = ["dist/**", "**/*.min.js"]
```
