MCP server
volcengine / openviking
OpenViking is an open-source context database designed specifically for AI Agents(such as openclaw). OpenViking unifies the management of context (memory, resources, and skills) that Agents need through a file system paradigm, enabling hierarchical context delivery and self-evolving.
This connects Repowise to volcengine/openviking's code. It does not install openviking.
Repowise maps public repos from their source. Not affiliated with volcengine. What is Repowise?
github.com/volcengine/openvikingIndexed at 66622aa
What is openviking?
OpenViking is an open-source context database designed for AI Agents. It holds the memory, resources and skills an Agent needs and organizes them in a file system paradigm instead of flat vector storage. The core is written in Python, with a Rust command line tool and C++ extensions. To install it, run pip install openviking --upgrade --force-reinstall. Its code health is 5.9 out of 10 (Fair), ranked #220 of 4,000+ indexed repos. The last commit to openviking was on Jun 14, 2026.
As of commit 66622aa, indexed Jun 14, 2026. What it is comes from a model reading the README; the rest is measured from the source and git history, not from the maintainer.
For agentsopenviking.md
Repo facts: type, license, health, rank, contributors
| Type | MCP server |
|---|---|
| License | AGPL-3.0 |
| Code health | 5.9 / 10 (Fair) |
| Health rank | #220 of 4,000+ indexed repos |
| Last commit | Jun 14, 2026 |
| Bus factor | 4 |
| Size | 2,522 files, 528,563 lines |
Install openviking
Commands copied from the README
- 1Install the OpenViking Python package from PyPI, which requires Python 3.10 or higher.
pip install openviking --upgrade --force-reinstall
Releases on GitHub (latest v0.5.5, Nov 13, 2026)
Explore openviking
- DocumentationModule-by-module documentation, written from the source.
- ArchitectureDependency graph, layers and third-party dependencies.
- Code healthEvery file's score and the findings behind it.
- CommitsEach commit's effect on code health.
- OverviewEverything else the index found: contributors, decisions, what changed this week.
Ask about this code in your agent
This connects Repowise to openviking's code. It does not install openviking. To install openviking, use the install steps.
Useful if you want to change or fork openviking: your agent can ask how it is put together and get answers that cite its files.
How to use openviking
- 1Run the interactive setup wizard to configure local models through Ollama.
openviking-server init - 2Check your setup, including the config file, Python version and provider connectivity.
openviking-server doctor - 3Start the OpenViking server with the VikingBot agent enabled.
openviking-server --with-bot
Ask about openviking
Answers come from openviking's README and source, with the files they cite. Two free answers a day without an account.
Want this for your own codebase? Map your repo free
About this page
Get a page like this for your own codebase
Repowise built this map of volcengine/openviking from its source and git history. It parses every symbol, draws the dependency graph, scores each file's health from complexity, duplication, coverage and churn, finds hotspots and owners in the history, and writes documentation for every module. Your coding agent reads the same index over MCP, so its answers cite real files.
Free for 2 public repos, with a page like this one. No card. See how Repowise works
Prefer local? pip install repowise && repowise init indexes your own checkout, no account needed. Star Repowise on GitHub
volcengine/openviking FAQ
What is OpenViking?
OpenViking is an open-source context database designed for AI Agents. It manages the memory, resources and skills that an Agent needs using a file system paradigm.
How does OpenViking work?
OpenViking organizes agent context as files and directories and loads it in three tiers, L0, L1 and L2, on demand. It combines directory positioning with semantic search for retrieval and compresses conversation content into long-term memory.
How do I install OpenViking?
OpenViking is installed from PyPI with pip install openviking --upgrade --force-reinstall, and it needs Python 3.10 or higher. Running openviking-server init sets up local models through Ollama. See the install steps
What language is OpenViking written in?
OpenViking is primarily written in Python. The repository also includes C++ and TypeScript code, and Rust is used for the CLI and RAGFS components.
How is the OpenViking code organized?
The openviking directory holds the core Python package, bot holds the VikingBot agent framework, and crates holds the Rust CLI and RAGFS code. Tests, examples, docs and benchmark directories sit alongside them.
Who is OpenViking for?
OpenViking is for developers building AI Agents who need to manage agent memory, resources and skills in one place.
What license does OpenViking use?
OpenViking is licensed under AGPL-3.0.
Code health
Hotspots average 3.7, the place fixes pay off most.
On the leaderboards:#4 of 4 Agent memory layers#61 of 71 Python repos
Key features of openviking
- OpenViking unifies the memory, resources and skills an Agent needs under a file system paradigm.
- It loads context in three tiers, L0, L1 and L2, on demand rather than all at once.
- It combines directory positioning with semantic search for recursive context retrieval.
- It supports visualization of directory retrieval trajectories to help find the cause of retrieval problems.
- It automatically compresses conversation content and extracts long-term memory from sessions.
How volcengine/openviking works
The openviking directory holds the main Python package, which organizes and stores agent context. openviking/storage/viking_fs.py implements the storage layer that keeps context as files and directories. openviking/session/session.py handles conversation sessions, compressing content and extracting long-term memory from them. crates/ov_cli/src/main.rs is the entry point of the Rust CLI, which connects to a running server through its configured URL. bot/vikingbot/__main__.py starts VikingBot, an agent framework built on top of OpenViking, and it can run alongside the server.
The codebase has 2,522 files and 31,763 symbols in 15 modules, led by Python, C++ and TypeScript. Code health is 5.8 out of 10, rated fair.
Maintain volcengine/openviking?
Claim this page, add a badge to the README, or re-index it.
Claim this page
Sign in with GitHub and we check that you are an admin or maintainer of volcengine/openviking. Then add a badge to the README that links readers here.
Add a badge to your README
Readers click through to this page and can ask openviking's code a question. A badge also re-indexes the repo every week and marks you as the verified maintainer.
[](https://repowise.dev/repo/volcengine/openviking?src=badge_ask)Paste it at the top of README.md, under the title.
Added it already? Verify to get the mark now instead of tomorrow.
Need HTML or the larger health card? More formatsHide more formats
This badge as HTML
<a href="https://repowise.dev/repo/volcengine/openviking?src=badge_ask"><img src="https://api.repowise.dev/badge/wiki/volcengine/openviking.svg?label=ask" alt="repowise: Ask this codebase"></a>Code health card
The score, its change since the last index, and when it was measured. Follows the reader's light or dark theme.
<a href="https://repowise.dev/repo/volcengine/openviking?src=badge_card"><picture><source media="(prefers-color-scheme: light)" srcset="https://api.repowise.dev/badge/health/volcengine/openviking.svg?style=card&theme=light"><img src="https://api.repowise.dev/badge/health/volcengine/openviking.svg?style=card" alt="repowise code health" width="500" height="168"></picture></a>