This folder contains apps, demos, and integrations that show what persistent memory enables in real products and workflows. Some examples are complete local projects; others are focused integrations that can be adapted into your own agent stack.
|
Earth Online is a memory-aware productivity game that turns everyday planning into a living quest log. |
Golutra presents a multi-agent workforce for engineering teams, extending the IDE model from a single assistant to coordinated agents. |
|
Record, visualize, and explore your tasting journey through an immersive 3D star map. |
Build AI that feels. Open-source persona engine — personality emerges from neural drives, not prompts. Inspired by Her. |
|
Ruminer brings persistent memory to a browser agent so it can carry personal context across web tasks. |
One command to connect any AI coding CLI to EverMemOS long-term memory. |
|
MCO equips your primary agent with an agent team that can work together to solve complex tasks. |
Study proactively with an agent that has self-evolving memory. |
|
Empowering individuals with advanced memory support and daily assistance. |
An iOS sci-fi mystery game where players explore and uncover the truth. |
|
An iOS app where users create, nurture, and live with a personalized AI companion called Mobi. |
A context-native AI wearable that listens to everyday life and converts conversations into memory. |
|
A 24/7 agent workflow with continuous learning memory across sessions. |
Add long-term memory to a real-time Live2D character, powered by TEN Framework. |
|
Run screenshot-based analysis with computer-use and store the results in memory. |
A demonstration of AI memory infrastructure through an interactive Q&A experience with A Game of Thrones. |
|
Persistent memory for Claude Code. Automatically saves and recalls context from past coding sessions. |
Explore stored entities and relationships in a graph interface. Frontend demo; backend integration is in progress. |
Before submitting a use case, please follow these best practices to keep the repository clean and lightweight.
Do not commit image files (.png, .jpg, .gif, .svg, etc.) to this repository. Images bloat the Git history and cannot be removed after the fact.
Instead, upload images to GitHub user-attachments and reference them by URL in your README:
Do not commit files that can be regenerated locally:
node_modules/— runnpm installto regeneratepackage-lock.json— already in.gitignorefor this folderdist/,build/,.next/— build output.env— use.env.examplewith placeholder values instead
Avoid duplicating logic across your use case. If multiple files share the same functionality, extract it into a shared utility. This makes examples easier to follow and maintain.
Before opening a PR, verify:
- No image files committed (use external URLs)
- No
node_modules, lock files, or build artifacts - No secrets or API keys (only
.env.examplewith placeholders) - README included with setup instructions
- Code is concise and avoids unnecessary repetition

















