ruvnet/RuVector

RuVector is a High Performance, Real-Time, Self-Learning Ai, Vector GNN, Memory DB built in Rust.

View on GitHub ↗Jump to charts ↓Open shareable report

Summary Information

Updated 36 minutes ago
Added to GitGenius on March 2nd, 2026
Created on November 19th, 2025
Open Issues & Pull Requests: 318 (+0)
GitHub issues: Enabled
Number of forks: 591
Total Stargazers: 4,476 (+1)
Total Subscribers: 38 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 45.6 hours
Mean response time: 11.7 days
90th percentile: 37.7 days
Tracked items: 248

How this project is maintained

Around half of the issues opened in the past year never receive a reply. Only 21% of open issues come from outside the core team — the tracker reads mainly as internal planning. Work labelled "adr" is answered fastest, typically in under an hour, while "enhancement" waits about 2 days. 23% 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: 112
New in 7 days: 11
Closed in 7 days: 5
Avg open age: 7 days
Stale 30+ days: 53
Stale 90+ days: 26

Recent activity

Opened in 7 days: 9
Closed in 7 days: 5
Comments in 7 days: 0
Events in 7 days: 11

Top labels

  • pir (37)
  • enhancement (34)
  • adr (28)
  • bug (9)
  • security (8)
  • cross-repo (6)
  • documentation (6)
  • wave-2 (6)

Detailed Description

RuVector is a vector database and memory substrate for AI agents built in Rust.

RuVector addresses the problem of persistent, adaptive memory for AI systems that need to retain information across sessions. It combines local semantic embeddings with persistent vector retrieval, graph relationships, and explicit feedback learning. The tool runs entirely locally by default, downloading and caching embedding models on first use, with no requirement for external database servers or API keys. Memory persists to disk under the project directory and can be recovered by reopening the same storage path in subsequent processes. The system treats learning as an explicit process driven by recorded outcomes and feedback rather than by read operations alone.

The tool suits developers building AI agents that need to remember context between invocations and want to avoid external service dependencies. It provides two typed memory layers: AgenticMemory, which unifies working, episodic, semantic, and procedural memory into a single runtime API, and AgenticDB, which persists specific agent artifacts including episodes, skills, causal edges, and policy state. The core store itself is general-purpose and supports multiple embedding providers including ONNX and Candle. Developers should note that the unified manager for AgenticMemory currently operates in-memory and its cross-type consolidation method remains incomplete.

The project receives issues from both core maintainers and external users, indicating adoption beyond the immediate team without an overwhelming support burden. Maintainers typically respond to new issues and pull requests within a few days. Work in the issue tracker centers on enhancements, bug fixes, and documentation.