Add entity context for Codex memory saves#17
Open
ishaanxgupta wants to merge 1 commit into
Open
Conversation
cc44ba7 to
6ea9102
Compare
MaheshtheDev
requested changes
Jun 6, 2026
Member
MaheshtheDev
left a comment
There was a problem hiding this comment.
what about results? any improvements?
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 changed
Why
Claude Supermemory already sends entity-specific context on write calls, which lets Supermemory persist extraction guidance on the container tag. Codex was creating/saving to tags without that field, so container tags could show no entity context and extraction had less guidance.