EverOS/use-cases

Use Cases

Use cases show what persistent memory makes possible in real products and workflows. Some examples are packaged in this repository; others point to external demos or integrations you can study and adapt.

Reunite - Find with EverOS Parents describe what they remember. Children describe what they recall. Reunite uses semantic memory to surface the connections. Learn more	Hive Orchestrator Browser-native hive-mind for CLI coding agents — Claude Code, Codex, Gemini, and OpenCode collaborate as real PTY processes via a team protocol. Code
AI Coding Assistants with EverOS Universal long-term memory layer for AI coding assistants, powered by EverOS. Code	AI Data Techician An agentic AI system that learns from scientist interaction to inspect, analyze, and classify high-dimensional time series data — with persistent memory that improves across sessions. Code
Rokid AI Assistant with EverOS Connect to EverOS within Rokid Glasses enabling long-term memory for all of your smart activities. Coming soon	Creative Assistant with Memory Creative assistant with long-term memory, never forget your crativites anymore. Coming soon
Earth Online Memory Game Earth Online is a memory-aware productivity game that turns everyday planning into a living quest log. Code	Multi-Agent Orchestration Platform Golutra presents a multi-agent workforce for engineering teams, extending the IDE model from a single assistant to coordinated agents. Code
Your Personal Tasting Universe Record, visualize, and explore your tasting journey through an immersive 3D star map. Code	EverOS Open Her Build AI that feels. Open-source persona engine — personality emerges from neural drives, not prompts. Inspired by Her. Code
Browser Agent for Personal Memory Ruminer brings persistent memory to a browser agent so it can carry personal context across web tasks. Plugin	EverMem Sync with EverOS One command to connect any AI coding CLI to EverMemOS long-term memory. Code
MCO - Orchestrate AI Coding Agents MCO equips your primary agent with an agent team that can work together to solve complex tasks. Code	Study Buddy with Self-Evolving Memory Study proactively with an agent that has self-evolving memory. Code
Alzheimer’s Memory Assistant Empowering individuals with advanced memory support and daily assistance. Code	Memory-Driven Multi-Agent NPC Experience An iOS sci-fi mystery game where players explore and uncover the truth. Code
Mobi Companion An iOS app where users create, nurture, and live with a personalized AI companion called Mobi. Code	AI Wearable with Memory A context-native AI wearable that listens to everyday life and converts conversations into memory. Code
OpenClaw Agent Memory A 24/7 agent workflow with continuous learning memory across sessions. Plugin	Live2D Character with Memory Add long-term memory to a real-time Live2D character, powered by TEN Framework. Code
Computer-Use with Memory Run screenshot-based analysis with computer-use and store the results in memory. Live Demo	Game of Thrones Memories A demonstration of AI memory infrastructure through an interactive Q&A experience with A Game of Thrones. Code
Claude Code Plugin Persistent memory for Claude Code. Automatically saves and recalls context from past coding sessions. Code	Memory Graph Visualization Explore stored entities and relationships in a graph interface. Frontend demo; backend integration is in progress. Live Demo

Contributing Guidelines

Before submitting a use case, please follow these best practices to keep the repository clean and lightweight.

No images in the repo

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:

![Screenshot](https://github.com/user-attachments/assets/your-image-id)

No generated or dependency files

Do not commit files that can be regenerated locally:

• node_modules/ — run npm install to regenerate
• package-lock.json — already in .gitignore for this folder
• dist/, build/, .next/ — build output
• .env — use .env.example with placeholder values instead

Keep code DRY

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.

General checklist

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.example with placeholders)
• README included with setup instructions
• Code is concise and avoids unnecessary repetition