Skip to content

[codex] Add on-prem graph memory backend#1

Closed
heikog wants to merge 1 commit into
codex/i18n-prompt-baselinefrom
codex/onprem-graph-memory
Closed

[codex] Add on-prem graph memory backend#1
heikog wants to merge 1 commit into
codex/i18n-prompt-baselinefrom
codex/onprem-graph-memory

Conversation

@heikog

@heikog heikog commented Jun 13, 2026

Copy link
Copy Markdown
Owner

What changed

  • Adds a graph-memory adapter layer with Zep Cloud as the default backend.
  • Adds a Graphiti bridge adapter for on-premise graph memory.
  • Adds a separate Graphiti Bridge service backed by FalkorDB so Graphiti dependencies do not conflict with OASIS.
  • Adds an optional docker compose profile for graphiti-falkordb and graphiti-bridge.
  • Documents the on-premise graph-memory setup.

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

  • python3 -m compileall -q backend/app graphiti_bridge
  • docker compose --profile graphiti config
  • git diff --check
  • Manual smoke test on Paul using GraphitiBridgeGraphMemoryAdapter against graphiti-bridge/FalkorDB

@heikog

heikog commented Jun 13, 2026

Copy link
Copy Markdown
Owner Author

Replaced by upstream PR 666ghj#696, which is based directly on upstream main.

@heikog heikog closed this Jun 13, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant