volcengine/OpenViking

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

What it solves

OpenViking provides a transparent, structured way for AI agents to store and retrieve knowledge, memories, and skills. Unlike traditional vector databases that act as "black boxes," OpenViking organizes context as a virtual filesystem, allowing both agents and human users to inspect, edit, and manage what an agent knows.

How it works

It implements a virtual filesystem under the viking:// URI scheme. Agents interact with this system using familiar file-like commands (such as ls, read, and grep). To optimize retrieval, it uses a three-tier loading system:

  • L0 (Abstract): A one-sentence summary for quick relevance checks.
  • L1 (Overview): Core information and usage scenarios for planning.
  • L2 (Details): The full original data, loaded only when necessary.

Semantic search can be scoped to specific directories or subtrees rather than scanning a flat index, and sessions can be archived as Markdown files for later inspection or merging.

Who it’s for

  • AI Agent Developers: Those building agents that require long-term memory and structured knowledge bases.
  • AI Agent Users: Users of tools like Claude Code, Cursor, or TRAE who want cross-session memory and the ability to audit their agent's knowledge.

Highlights

  • Virtual Filesystem Interface: Treats agent context as a directory structure, making it human-readable and manageable.
  • Multi-tier Context: Reduces token usage and latency by allowing agents to read summaries before full content.
  • L0/L1/L2 Layering: Specifically designed to reduce input tokens and query latency.
  • Broad Integration Support: Plugins available for major coding agents (Claude Code, Cursor, TRAE) and frameworks like LangChain.
  • Open Source: Available under the AGPLv3 license.

Related

  • Project
  • Project
  • Project
  • Project
  • Project