From 6f0b2a35f1d2eb2636cc6131d79026aaf35eed0f Mon Sep 17 00:00:00 2001 From: Luke Curley Date: Thu, 5 Nov 2026 15:32:59 -0800 Subject: [PATCH] quest: rule checks also give Codex the session rules hook Co-Authored-By: Claude Opus 5.5 --- quest/m0/token-waste/rule-checks.md | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/quest/m0/token-waste/rule-checks.md b/quest/m0/token-waste/rule-checks.md index 07f973cf..56b2a61c 100644 --- a/quest/m0/token-waste/rule-checks.md +++ b/quest/m0/token-waste/rule-checks.md @@ -30,6 +30,14 @@ Recommendations for the implementer: [Rules load once](/quest/m0/token-waste/rule-loading.md) installs its `SessionStart` hook, since repositories write no hooks. Give Codex the equivalent `hooks.json` entries where its hooks can match. +- Codex parity for the always-on rules too (coordinator, 2026-11-05, + follow-up of [moq-dev/quest#517](https://github.com/moq-dev/quest/pull/517), + which gave Claude Code the `SessionStart` rules hook and Codex none): + `quest setup` writes the same `SessionStart` entry (`compact` included) + to `~/.codex/hooks.json`, with an `additionalContextLimit` that fits the + rules. `quest review` runs Codex with `--ignore-user-config`; confirm in + a review transcript that this keeps the user hook out of reviews, and + keep it out if not. Codex asks to trust each hook once through `/hooks`. - Keep a check narrow enough that it never blocks legitimate work: a force push the user asked for, an em dash quoted from someone else, `/tmp` used by a tool rather than for agent scratch. A check that cannot tell these