Memoryvolcengine/OpenViking42.1k
Organize agent memory, knowledge, and skills as files
A context database that organizes agent knowledge, memories, and skills under viking:// URIs. Inspect stored context, search specific subtrees, and extract editable memories from sessions.
Install
This plugin is not installed with a one-line command. Follow the install steps in its readme
At a glance
- Browse and edit agent context through a virtual filesystem
- Scope semantic retrieval to a project directory or memory subtree
- Read L0 abstracts and L1 overviews before loading full L2 content
- Archive committed sessions and extract memories as editable Markdown
- Compile source material into wikis, knowledge graphs, or reports with VikingBot enabled
What does OpenViking do?
OpenViking is an open-source context database for AI agents. It places knowledge, memories, and skills in a virtual filesystem addressed through viking:// URIs. Developers can inspect and edit stored context, while agents can navigate it with file-style operations.
Resources can contain documents and code; memories capture preferences and experience; skills describe task procedures.
Core features
- Browse context with operations including
ls,tree,read,write, andgrep. - Limit semantic retrieval to a project directory or memory subtree. Use
findfor direct queries andsearchfor retrieval planned from session context. - Load context in stages: L0 abstracts for an initial relevance check, L1 overviews for more context, and L2 content for full details. Semantically processed directories carry generated summaries.
- Commit sessions to archive conversations and extract Markdown memories that can be inspected, edited, and merged.
- With VikingBot enabled, use
ov compileto turn source material into a wiki, knowledge graph, or report.
How to use OpenViking
The README offers a browser-based OpenViking Studio demo that requires no installation and points to separate instructions for self-hosting Web Studio.
When working with stored context, navigate to the relevant viking:// directory, review its abstract or overview, and retrieve full content as needed. Scope searches to the relevant project or memory branch, and commit sessions to preserve conversations and extract memories.
The supplied excerpt does not document DSH installation steps or identify an npm package.
Questions about OpenViking
How do I install OpenViking?
OpenViking has no one-line install on npm. Follow the steps in its readme.
Is OpenViking free to use?
The source is public at volcengine/OpenViking under the AGPL-3.0 license. Check that license if you plan to use it commercially.
Is OpenViking still maintained?
The last code push was on Nov 12, 2026, and the latest release is python-sdk@0.1.20. We last refreshed this data on Nov 12, 2026. DeepSeek Harness changes quickly, so a plugin untouched for months may no longer load.
Has Plugin DSH tested OpenViking?
No. It is listed from its public repository and we have not installed it. Read the source and recent issues before you run it.
How is context organized?
Documents, code, memories, and skills have viking:// URIs within a virtual filesystem. Agents can navigate this context using operations such as ls, tree, read, write, and grep.
What is the difference between find and search?
find executes a query directly, while search uses session context to plan retrieval. Semantic queries can be scoped to a directory or subtree.
What happens when a session is committed?
The conversation is archived, and memories are extracted into Markdown that can be inspected, edited, and merged.
Is a DSH installation command available?
The supplied README excerpt provides no DSH installation command, and the repository information does not identify an npm package. It does offer a browser-based Studio demo and references self-hosted Web Studio.