Configuration
Code Guardian creates code-guardian.conf on its first run, only if it is missing, and never overwrites it afterwards. This page lists the switches.
code-guardian.conf
| Switch | Default | Effect |
|---|---|---|
plan_modus |
true | Only the literal false switches this off: then there is no one-click approval, instead the plan carries stated assumptions and a cold plan review runs alongside it |
orchestrator_takt |
true | Enables the orchestrator's pacing |
orchestrator_takt_min |
20 | allows values from 1 to 1440 |
task_orchestrator_takt |
true | The session holding the task orchestrator role compares the open items of the task list with git at a fixed interval |
task_orchestrator_takt_min |
20 | that interval in minutes, allows values from 1 to 1440 |
rueckfrage |
not set | Only the value sperre has an effect: every question from the command guards then becomes a refusal with a hint on what to do instead, for runs where nobody can answer a question. The installer does not add this line |
riegel_zusatz |
not set | Switches on two extra latches, comma-separated: rechts (legal gate) and data-analytics (data analysis gate). It takes effect only after running bash install.sh again, because the installer registers the hooks. Without this line neither of them blocks |
The installer does not extend an existing file. Anyone who wants the newer switches adds them by hand; without them, the default applies.
Environment variables
| Variable | Meaning |
|---|---|
CG_STOP_AUFSCHUB |
currently has no effect: the end-of-answer gates that read it are deregistered |
CG_FRISCHE_TTL |
throttles the freshness check, in seconds, default 600 (see the Network chapter) |
CLAUDE_CONFIG_DIR |
respected, moves where configuration files are read from |
In one sentence
The configuration file is created once and never changed automatically afterwards, anyone who wants a different setting edits it themselves.