volcengine/OpenViking

Self-evolving Context Database for AI Agents. Unify Agent Memory, Knowledge RAG and Skills.

View on GitHub ↗Jump to charts ↓Open shareable report

Summary Information

Updated 43 minutes ago
Added to GitGenius on March 22nd, 2026
Created on January 5th, 2026
Open Issues & Pull Requests: 509 (+0)
Number of forks: 2,504
Total Stargazers: 32,800 (+0)
Total Subscribers: 90 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 7.8 hours
Mean response time: 3.0 days
90th percentile: 4.7 days
Tracked items: 821

How this project is maintained

Around half of the issues opened in the past year never receive a reply. 94% of open issues come from outside the core team, so the backlog reflects real-world use rather than internal planning. Work labelled "question" is answered fastest, typically in about 3 hours, while "urgency:bug" waits about 2 days. Almost all tracked open issues have seen activity in the last three months. Only 9% of issues opened in the past year have been closed.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 172
New in 7 days: 63
Closed in 7 days: 24
Avg open age: 11 days
Stale 30+ days: 74
Stale 90+ days: 9

Recent activity

Opened in 7 days: 55
Closed in 7 days: 22
Comments in 7 days: 32
Events in 7 days: 217

Top labels

  • bug (288)
  • enhancement (121)
  • question (113)
  • scenario:kernel (40)
  • urgency:bug (27)
  • urgency:suggestion (11)
  • scenario:plugins (10)
  • urgency:fatal (8)

Detailed Description

OpenViking is a context database for AI agents that unifies agent memory, knowledge retrieval, and skills under a single virtual filesystem interface.

The tool addresses the challenge of managing fragmented context across multiple AI agent systems by presenting memories, resources, and skills as a unified `viking://` filesystem. Agents interact with their context deterministically using familiar filesystem operations like `ls`, `tree`, and `find` rather than querying opaque vector stores. Content is automatically processed into three abstraction tiers—L0 abstract, L1 overview, and L2 details—on write and loaded on demand based on task requirements. Directory-based recursive retrieval locates the highest-scoring directory first, then drills down layer by layer to return results with surrounding context intact. Every retrieval preserves its browsing trajectory, making it possible to debug and understand exactly which path produced a given result. Sessions automatically extract user preferences and agent experience into long-term memory after commit.

Teams building AI agents that need transparent, debuggable context management should consider this tool, particularly those frustrated with black-box vector store approaches or managing multiple disconnected memory systems. The tiered loading mechanism directly reduces token consumption by loading only the abstraction depth required for a given task. The filesystem metaphor makes context manipulation deterministic and familiar to developers accustomed to file-based workflows.

The project maintains a substantial base of external adopters who report real-world issues rather than the core team driving the issue tracker. Maintainers typically respond to new issues and pull requests within a day. Work in the issue tracker centers on bug reports, user questions, and enhancement requests.