APPROVAL_RUNGS
constAPPROVAL_RUNGS: readonly ["read-only","write","auto-safe","full-auto","bypass"]
Defined in: _worktrees/docs-release/gaunt-sloth/packages/core/src/config/shell-policy.ts:388
CFG-27 (spec §1, §2) — the ladder. There is ONE approvals setting and it is a single ordered ladder of five rungs; each rung fully determines behaviour. There are no severity thresholds, no strictness levels and no independent rater on/off switch.
| # | Rung | Rater | LLM cost |
|---|---|---|---|
| 1 | read-only |
no | none |
| 2 | write |
no | none |
| 3 | auto-safe |
yes | 1 call per gated call |
| 4 | full-auto |
yes | 1–2 calls per gated call |
| 5 | bypass |
no | none |
Rungs 1, 2 and 5 are fully deterministic: no model is consulted, so behaviour is reproducible and costs nothing.
bypass is NOT a higher-autonomy rung than full-auto (§2.5). Both let the agent act
without asking; bypass is the same autonomy with the checks removed. The ordering below is the
order the rungs are offered in, and must never be presented as though full-auto were an
incomplete bypass.
Identifiers are kebab-case (§9.1) because the same token must work as a config value, a slash-command argument and a CLI flag — a space breaks the last two. Display names keep their spaces; see APPROVAL_RUNG_LABELS.