evermind-ai/everos

One portable memory layer for every AI agent: local-first, Markdown-native, user-owned, and self-evolving across apps, tools, and workflows.

View on GitHub ↗Jump to charts ↓

Summary Information

Updated 41 minutes ago
Added to GitGenius on September 1st, 2026
Created on October 28th, 2025
Open Issues & Pull Requests: 79 (+0)
GitHub issues: Enabled
Number of forks: 912
Total Stargazers: 12,762 (+0)
Total Subscribers: 112 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 3.1 days
Mean response time: 18.7 days
90th percentile: 86.1 days
Tracked items: 92

How this project is maintained

Around half of the issues opened in the past year never receive a reply. 82% of open issues come from outside the core team, so the backlog reflects real-world use rather than internal planning. Work labelled "enhancement" is answered fastest, typically in about 17 hours, while "use cases" waits about 8 days. 35% of tracked open issues have had no activity in three months. Only 12% of issues opened in the past year have been closed.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 51
New in 7 days: 4
Closed in 7 days: 2
Avg open age: 86 days
Stale 30+ days: 44
Stale 90+ days: 15

Recent activity

Opened in 7 days: 4
Closed in 7 days: 2
Comments in 7 days: 1
Events in 7 days: 3

Top labels

  • methods (28)
  • enhancement (16)
  • use cases (16)
  • bug (15)
  • benchmarks (9)
  • documentation (4)

Most active issues this week

Detailed Description

EverOS is a memory runtime for AI agents that provides a portable, local-first memory layer across multiple applications and workflows.

The tool addresses the fragmentation of agent memory across different tools and platforms by creating a unified memory system that persists conversations, files, and agent trajectories as human-readable Markdown files. It maintains local SQLite and LanceDB indexes alongside these files to enable fast retrieval and support self-evolving memory reuse. The approach keeps data under user control while allowing agents to access and build upon their history across different applications and devices.

Developers should choose EverOS if they are building agentic systems that need to maintain coherent memory across multiple tools, coding assistants, or workflows. It suits projects where preserving conversation history and agent trajectories in a portable, inspectable format matters, and where fast indexed retrieval is necessary for agent decision-making. The tool is particularly relevant for teams building on top of language models and wanting to avoid vendor lock-in through its local-first, user-owned data model.

The project maintains active community engagement through multiple channels and shows ongoing development of integrations with the broader AI agent ecosystem. Documentation and examples are available to guide adoption, and the codebase is structured as a Python library designed for straightforward integration into existing agent workflows.