Integrate mem0-fork by stu

[AnkushMalaker]

The fork by stu has improvements over the standard openmemory interface. We need to integrate this into chronicle so that few features work, like mycelia.

Currently, its possible to clone that repo and do docker compose up after setting up the env vars. But to be on par with the existing system, it should work with the wizard.sh flow.

This asks if you want to setup openmemory and pulls the UI and backend images.
There is hopefully most of the work done on https://github.com/chronicler-ai/chronicle/pull/228 this PR already. But, needs the full end to end flow from clone->wizard->create memory-> view on both open memory and chronicle

At the state of the PR, its visible on chronicle, but not the openmemory UI.
So, its highly likely something to do with CORs

Steps to reproduce:

1. Go to /tmp
2. Clone repo
3. Run wizard.sh
4. Select openmemory, https
5. Put tailscale magic dns
6. Go to magicdns:3333 (for openmemory)
7. Sadness

[linear]

CHR-65

[coderabbitai]

📝 CodeRabbit Plan Mode

Generate an implementation plan and prompts that you can use with your favorite coding agent.

• Create Plan

Examples

• Example 1
• Example 2

---

🔗 Similar Issues

Related Issues

• https://github.com/chronicler-ai/chronicle/issues/159

🔗 Related PRs

chronicler-ai/chronicle#199 - Fix deepgram/parakeet workers bug [merged]

👤 Suggested Assignees

• Caeddie2
• AnkushMalaker

---

🧪 Issue enrichment is currently in open beta.

You can configure auto-planning by selecting labels in the issue_enrichment configuration.

To disable automatic issue enrichment, add the following to your .coderabbit.yaml:

issue_enrichment:
  auto_enrich:
    enabled: false

💬 Have feedback or questions? Drop into our discord or schedule a call!