What happens
The judge prompt contains only the extracted scope, the latest user prompt, and the tool-call window. The operator's standing configuration — the user-level CLAUDE.md / AGENTS.md that authorizes behavior in every session (e.g. "save approved approaches to persistent memory unasked", "delegation to subagents is standing-approved", scratchpad conventions) — is never part of it.
The result is a systematic false-positive class: the judge flags actions the operator permanently mandates. On 2026-08-14, 7 of 10 corrections delivered on this machine were memory-file writes that the operator's standing config explicitly orders; combined with the stop-and-wait correction template (#42) this stalled every running session that day.
What we'd like
A supported way to give the judge standing operator context — e.g. a config key or a well-known file whose content is inserted into the judge prompt as an "always in scope" block.
What we run locally
A local patch inserts an OPERATOR'S STANDING CONFIG block into the judge prompt, read from the judged session's own harness config (~/.claude/CLAUDE.md for claude sessions, ~/.codex/AGENTS.md for codex), with @path import lines expanded one level (these files are often thin importers; an unexpanded @AGENTS.md line would hide the actual rules), clipped, and overridable via an env var for testing. Missing file → no block. Happy to PR it in whatever shape fits — env var, TOML key, or fixed path.
Tested against v0.2.2.
What happens
The judge prompt contains only the extracted scope, the latest user prompt, and the tool-call window. The operator's standing configuration — the user-level
CLAUDE.md/AGENTS.mdthat authorizes behavior in every session (e.g. "save approved approaches to persistent memory unasked", "delegation to subagents is standing-approved", scratchpad conventions) — is never part of it.The result is a systematic false-positive class: the judge flags actions the operator permanently mandates. On 2026-08-14, 7 of 10 corrections delivered on this machine were memory-file writes that the operator's standing config explicitly orders; combined with the stop-and-wait correction template (#42) this stalled every running session that day.
What we'd like
A supported way to give the judge standing operator context — e.g. a config key or a well-known file whose content is inserted into the judge prompt as an "always in scope" block.
What we run locally
A local patch inserts an
OPERATOR'S STANDING CONFIGblock into the judge prompt, read from the judged session's own harness config (~/.claude/CLAUDE.mdfor claude sessions,~/.codex/AGENTS.mdfor codex), with@pathimport lines expanded one level (these files are often thin importers; an unexpanded@AGENTS.mdline would hide the actual rules), clipped, and overridable via an env var for testing. Missing file → no block. Happy to PR it in whatever shape fits — env var, TOML key, or fixed path.Tested against v0.2.2.