Skip to content

Changing settings

Every anti-hall setting lives in one file, ~/.anti-hall/settings.json, grouped into sections such as guards, safety, autoHandover and statusline. Nearly every hook has an on/off switch there; settings.js show lists the few parts that have none, and why. The full list, with defaults, is the Settings reference.

Three ways to change a setting

Tell the assistant what you want, in plain words:

turn off the merge gate
set auto-handover to 80%
show my anti-hall settings

The settings skill (/anti-hall:settings) applies the change with one command and only prints tables when you ask to see them.

Claude Code's native /config panel (Claude Code 2.1.269 or newer) shows the headline switches: auto-handover on/off and its threshold, Jev, the DevSwarm supervisor mode, model routing, limit conservation, the four safety guards, and the API keys. Everything else is set through the skill or the command line.

node plugins/anti-hall/scripts/settings.js show                      # common settings, one table per section
node plugins/anti-hall/scripts/settings.js show --section jev --all  # one section, with advanced settings
node plugins/anti-hall/scripts/settings.js get autoHandover.pct
node plugins/anti-hall/scripts/settings.js set limitConserve.threshold 90
node plugins/anti-hall/scripts/settings.js reset limitConserve.threshold

Every command takes --json for scripts.

Which value wins

From highest to lowest:

  1. an ANTIHALL_* environment variable;
  2. ~/.anti-hall/settings.json;
  3. a value set in the /config panel;
  4. an older per-feature config file (for example ~/.anti-hall/jev.json);
  5. the default.

The Source column of settings.js show tells you which one answered.

A /config value equal to the default

The /config panel cannot tell "set to the default" apart from "never set". To pin a value that equals the default, set it in settings.json instead.

Safety settings

Some settings protect you from destructive actions: the four safety.* guards (gitGuard, commandGuard, editGuard, swarmGuard) and the settings that weaken them. They are marked safety in the reference.

Changing one of these in the risky direction (turning a guard off, adding to an allow list) needs confirmation. Without it nothing changes, and you get one plain line saying what would stop being protected. A direct request from you counts as confirmation; otherwise the assistant shows you that line and asks. On the command line, add --confirmed. Turning a guard back on never needs confirmation.

Codex

Codex has no /config panel. Use the anti-hall-settings skill or the command line; both read and write the same ~/.anti-hall/settings.json.