repowiserepowise
Sign in
volcengine/openviking
OverviewDocsArchitectureKnowledge GraphFilesCode HealthSecurityRefactoring

People & History

CommitsContributorsDecisions
Chat
Stats
repowiserepowise
ExplorePricingDocs
Sign in
repowisevolcengine/openviking
OP
OP

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.

Python★ 39,294
Use in your agentAsk this codebase

github.com/volcengine/openviking·Indexed at 66622aa·4mo ago·Up to date with upstream

About this codebase

2,522 files and 31,763 symbols in 15 modules, led by Python (1,335 files) and C++ (386).

Built from the index

Start reading

  • Knowledge graph2,522 files and how they depend on each other.→
  • Fix memory consolidation hook/session handling and make consolidation asyncDecisionProposed decision, from a pull request.→

Code health

5.8out of 10Fair

This codebase scores 5.8 out of 10 for code health, which we rate fair. Risk is concentrated, as it usually is: 388 of 2,522 files are git hotspots, and they average 3.7 — which is where the fixes pay off most.

Full health report →

On the leaderboards:#4 of 4 Agent memory layers·#38 of 44 Python repos

Do next

1 thing worth doing this quarter.

Worth planning

  • Delete 235 unused symbols and files (5,336 lines)

    Nothing in the graph reaches them, across 94 files; every reader and agent pays to skip them.

    symbols
    235
    lines
    5,336
    safe to delete
    Yes(inferred)
    Medium effort

Improve what Repowise can see

  • Add a test coverage report

    Without one, Repowise cannot tell tested code from untested code, so every test-related action says “unknown”.

    line coverage
    Unknown, no report
    Small effort
All actions in the Overview →

Use volcengine/openviking in your agent

Point Claude Code, Cursor, Codex or VS Code at this repository. Your agent gets the index this page is built from: cited answers, callers, history and health for any file.

https://api.repowise.dev/mcp/volcengine/openviking

One command, run anywhere. Adds the server to your local Claude Code config.

Docs
bash
claude mcp add --transport http repowise https://api.repowise.dev/mcp/volcengine/openviking \
  --header "Authorization: Bearer rw_live_xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx"
The snippet shows a placeholder key. Generate one to get a copyable secret.
Sign in and create an API key to connect.Sign in

This repo is public, so anyone with a Repowise account and an API key can connect.

Try asking

  • get_overview()
  • get_answer("how is openviking put together?")
  • get_why("why is openviking structured this way?")

Prefer local? pip install repowise && repowise init indexes your own checkout, no account needed.

Go deeper

  • OverviewEverything the index found, what changed this week, commits and decisions.→
  • DocumentationModule-by-module documentation, written from the source.→
  • ArchitectureDependency graph, layers and third-party dependencies.→
  • Code healthEvery file's score, the findings behind it, tests and refactoring plans.→
  • CommitsEach commit's effect on code health, with agent provenance.→
  • ContributorsWho owns what, and where one person holds most of the knowledge.→
  • DecisionsArchitectural decisions mined from commits and pull requests.→
  • Ask this codebaseSign inGrounded answers over the indexed code.→

Maintain this repo? Claim the 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.

Use this repo from Claude or ChatGPT

Add this URL as a custom connector and sign in with repowise when asked. No API key to copy.

https://api.repowise.dev/mcp/volcengine/openviking
Sign up to connect

For maintainers

Add a badge to your README

Every badge is public, cached, and updates on its own after every index. Nothing to install.

Repowise badge

Links to this page, with no score on it. Adding it also re-indexes the repo every week.

Repowise badge preview
[![repowise.dev](https://api.repowise.dev/badge/wiki/volcengine/openviking.svg)](https://repowise.dev/repo/volcengine/openviking?src=badge_wiki)

Code health badge

The repo's health score out of 10, from the latest index.

Code health badge preview
[![repowise.dev code health](https://api.repowise.dev/badge/health/volcengine/openviking.svg)](https://repowise.dev/repo/volcengine/openviking?src=badge_health)

Code health card

A larger card with the score, its change since the last index, and when it was measured. The HTML version follows the reader's light or dark theme.

Code health card preview
[![repowise.dev code health](https://api.repowise.dev/badge/health/volcengine/openviking.svg?style=card)](https://repowise.dev/repo/volcengine/openviking?src=badge_card)

How volcengine/openviking works

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 page is a map of the volcengine/openviking repository, written primarily in Python, rebuilt from the source each time it is indexed. Repowise parses every symbol, computes a dependency graph, scores per-file code health from complexity, duplication, test coverage and churn, mines git history for hotspots and ownership, and lifts the architectural decisions into documentation you can read here or query through MCP.

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.

Use the links above to open each view, or connect this repository to your agent for grounded answers inside Claude, Cursor, Codex or VS Code.