Repository navigation
ai-memory 2.4.1: real Codex capture observed after the /hooks trust (receipt addendum) - #344
Merged
seathatflowsinourveins merged 6 commits intoSep 26, 2026
Conversation
Adds a dated addendum to the 2.4.1 qualification receipt and a retained probe (evidence/artifacts/ai-memory-241-codex-capture-20260926/): after the user trusted the 7 rewritten Codex hook commands, one codex exec session wrote session-start, user-prompt, pre-tool-use, post-tool-use, stop and session-end observations through production 2.4.1 (store V67). The failed first attempt (outside a git repository, Codex directory-trust refusal) is kept. The two decision records get dated update notes; original limitations stay as recorded. Co-Authored-By: Claude Opus 5.5 (1M context) <[email protected]>
Co-Authored-By: Claude Opus 5.5 (1M context) <[email protected]>
|
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
Cross-family review (Codex, DISAGREE) found five overclaims: - the directory-trust error was not retained for attempt 1; - the trust action is not in the logs; - the PreCompact explanation had no support; - the prompt-allowlist behaviour was not verified; - the Codex version history was not in the logs. Changes: - attribute the trust to the user's report; - add codex-hook-events.txt (per-event command counts) and capture-attempt1-repro.txt (the no-git-repo condition, complete stderr); - state PreCompact as unverified; - drop the allowlist and version-history statements. Co-Authored-By: Claude Opus 5.5 (1M context) <[email protected]>
Co-Authored-By: Claude Opus 5.5 (1M context) <[email protected]>
…rified (recheck residuals) Co-Authored-By: Claude Opus 5.5 (1M context) <[email protected]>
Co-Authored-By: Claude Opus 5.5 (1M context) <[email protected]>
Collaborator
Author
|
Held for the v2026.09.26.1 release window (session 9a). |
seathatflowsinourveins
deleted the
claude/ai-memory-241-codex-capture-20260926
branch
September 26, 2026 16:23
seathatflowsinourveins
pushed a commit
that referenced
this pull request
Sep 26, 2026
…ow-up files Co-Authored-By: Claude Opus 5.5 (1M context) <[email protected]>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
This closes the one pending limitation on the ai-memory 2.4.1 cutover receipt for host
nativestack-5975wx-20260925: Codex capture.The 2.4.1 cutover (#307, receipt
evidence/receipts/ai-memory-241-qualification-20260925.json) rewrote the binary path in 7 Codex hook commands. Codex skips new or changed hooks until they are trusted, solimitations[0]recorded that real Codex capture through 2.4.1 had not been observed. On 2026-09-26 the user reported trusting the commands in Codex/hooks. The trust action itself is not retained; what is retained is its observable result, the hooks running.addenda[0], dated 2026-09-26). The claim, the original limitations anddata.cutover.pendingstay as recorded, following the rtk 0.50.0 hook recipe: exclude git show REV:path in every global-option form and git branch #318 addenda style.evidence/artifacts/ai-memory-241-codex-capture-20260926/:capture.txtrecords ai-memory 2.4.1, codex-cli 0.157.1, and 7/7 Codex hook commands ontools/ai-memory-2.4.1.codex exec -s read-onlywith one echo command, which exited 0 with the expected output.session-start,user-prompt,pre-tool-use,post-tool-use,stopandsession-end.codex-stderr-hook-lines.txtholds only the version banner and thehook:lines; session id, workdir and model lines are dropped.codex_capture_count.pyis the query that was used.capture-attempt1-untrusted-dir.txt, Codex exited 1 and 0 Codex sessions wrote observations. Its working directory and stderr were not retained.capture-attempt1-repro.txtran from outside any git repository and keeps the complete stderr: "Not inside a trusted directory and --skip-git-repo-check was not specified.", with 0 sessions. It establishes only its own failure, not the cause of the first attempt's.codex-hook-events.txtshows one 2.4.1 command for each of the seven events, PreCompact included.docs/decisions/2026-09-25-workstation-sota-refresh.mdanddocs/decisions/2026-09-25-ai-memory-2-4-0-release-review.md.manifests/evidence.jsonregisters the 10 files. The component matrix and grand list were regenerated with no change.Not covered
Checks
uv run --no-project --python 3.13 … scripts/validate.py:{"components": 69, "hashed_files": 6591, "profiles": 4, "receipts": 158, "status": "passed"}. That covers integrity and scope checks only.core.hooksPathisscripts/git-hooks, and the pre-commit hooks ran.Review
A Codex cross-family review (
codex exec -s read-only, gpt-6-astra, high) of the first head returned DISAGREE with five overclaims:The fixes are in
bbd9978b. A Codex recheck marked items 2, 4 and 5 FIXED. For 1 and 3 it found wording residues: the first attempt's cause was still implied, and the decision note said "unexercised".2e5c7897fixes both exactly as the recheck asked. The recheck also computed sha256 and byte counts for all 10 files and found they matchmanifests/evidence.json, and it found no personal paths, session ids or credential material. Under the bounded review loop (one review plus one repair round), there is no third round.SOTA sources
433a19f3), which is the binary pinned inmanifests/stack.json.evidence/receipts/rtk-050-qualification-20260925.json.🤖 Generated with Claude Code