[codex] Add on-prem graph memory backend#1
Closed
heikog wants to merge 1 commit into
Closed
Conversation
Owner
Author
|
Replaced by upstream PR 666ghj#696, which is based directly on upstream main. |
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
Zep Cloud is expensive for this deployment. This keeps existing Zep behavior as the default while adding an on-premise path that can be enabled with GRAPH_MEMORY_BACKEND=graphiti_bridge.
Stack note
This PR is stacked on the i18n/prompt baseline branch so its diff stays focused on graph memory. After PR 666ghj#695 is merged, this branch can be rebased/retargeted to upstream main.
Validation