fix(codex): filter synthetic AGENTS startup messages#1346
Merged
nicoloboschi merged 1 commit intovectorize-io:mainfrom Apr 30, 2026
Merged
Conversation
Contributor
Author
|
Also has some relevance to my issue #1345 |
nicoloboschi
approved these changes
Apr 30, 2026
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.
Summary
Filters Codex synthetic AGENTS.md startup messages out of the Codex integration transcript reader.
Codex can persist project startup instructions as a normal
response_itemwithrole: "user"and content shaped like:# AGENTS.md instructions for ...<INSTRUCTIONS>...</INSTRUCTIONS>The Codex integration previously treated that as normal user conversation, so auto-retain and recall transcript composition could include agent rules/setup context instead of only the actual user/assistant session.
Why
This can pollute retained memory with hook rules, memory policy, MCP setup instructions, and other agent-control text that the user did not actually say as part of the working conversation.
In long-running Codex sessions, this can also contribute to oversized auto-retain payloads because the retained transcript includes synthetic setup context before the real conversation starts.
Implementation
Validation
pytest hindsight-integrations/codex/tests/test_content.pypytest hindsight-integrations/codex/tests/test_hooks.py