Skip to content

quest: rule checks also give Codex the session rules hook #523

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
kixelated merged 1 commit into from
Nov 6, 2026
Merged

quest: rule checks also give Codex the session rules hook #523

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 8 additions & 0 deletions quest/m0/token-waste/rule-checks.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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
Expand Down