PluginBench
Skill
Fail
Audit score 45

openviking-context-database

reason-machines/trending-skills

Open-source context database for AI agents with filesystem-based memory, resources, and skills management

What is openviking-context-database?

OpenViking is a unified context database for AI agents that replaces fragmented vector stores with a filesystem paradigm. It organizes agent memory, resources, and skills in a tiered L0/L1/L2 structure, enabling hierarchical context delivery and observable retrieval trajectories. Use it when you need persistent, searchable agent memory with semantic retrieval and self-evolving session management.

  • Organize agent context as a filesystem with memories (L0), resources (L1), and skills (L2) directories
  • Perform semantic search across namespaces with configurable embedding providers (OpenAI, Volcengine, Jina)
  • Track retrieval trajectories to observe which context layers are accessed during queries
  • Auto-compress session conversations into long-term memories via session management
  • Support multiple VLM providers (OpenAI, Volcengine, LiteLLM) for vision and language tasks
  • Query context with directory-scoped retrieval and direct path reads

How to install openviking-context-database

npx skills add https://github.com/reason-machines/trending-skills --skill openviking-context-database
Prerequisites
  • Python 3.10 or higher
  • Go 1.22+ (for AGFS components)
  • GCC 9+ or Clang 11+ (for core extensions)
  • Configuration file at ~/.openviking/ov.conf with LLM provider credentials
Claude Code
Cursor
Windsurf
Cline

How to use openviking-context-database

  1. 1.Install via pip: pip install openviking --upgrade --force-reinstall
  2. 2.Create ~/.openviking/ov.conf with your embedding and VLM provider settings (OpenAI, Volcengine, or LiteLLM)
  3. 3.Initialize OpenViking in your code: ov = OpenViking(config_path='~/.openviking/ov.conf')
  4. 4.Create a namespace for your agent: brain = ov.namespace('my_agent')
  5. 5.Write memories, resources, and skills using brain.write() to organize context hierarchically
  6. 6.Query context semantically: results = brain.search('your query', top_k=5)
  7. 7.Use sessions to track conversations and auto-compress into long-term memory: session = brain.session('task_name')
  8. 8.Enable trajectory tracking to observe retrieval decisions: with brain.observe() as tracker: results = brain.search(...)

Use cases

Good for
  • Build a coding assistant that learns user preferences and code style over time
  • Create a multi-turn agent that automatically extracts and stores insights from conversations
  • Implement RAG systems with observable retrieval decisions across memory tiers
  • Manage hierarchical skill libraries that are retrieved based on task similarity
  • Develop agents with persistent context that survives across sessions and deployments
Who it's for
  • AI agent developers building persistent memory systems
  • Teams implementing RAG (Retrieval-Augmented Generation) pipelines
  • Developers needing observable, auditable context retrieval for agents
  • Engineers managing multi-skill agent architectures

openviking-context-database FAQ

What embedding and VLM providers does OpenViking support?

OpenViking supports OpenAI, Volcengine, and LiteLLM for VLMs. For embeddings, it supports OpenAI, Volcengine, and Jina. LiteLLM enables integration with Claude, DeepSeek, Ollama, and other models.

How does the L0/L1/L2 tiered structure reduce token consumption?

L0 (memories) is always loaded for core identity and preferences. L1 (resources) is fetched on demand per task. L2 (skills) are retrieved via semantic similarity. This minimizes unnecessary context while keeping relevant information available.

Can I use OpenViking with local LLMs like Ollama?

Yes, via LiteLLM provider. Configure the VLM with provider='litellm', model='ollama/llama3.1', and api_base='http://localhost:11434'.

How does session compression work?

Sessions track conversation turns and can auto-compress after many interactions. The compress() method extracts long-term insights and writes them to the memories/ directory, then close() persists the session.

What is retrieval trajectory tracking?

Trajectory tracking (via brain.observe()) records which context paths are accessed during a search, showing the L0/L1/L2 levels accessed and their relevance scores for debugging and optimization.

Full instructions (SKILL.md)

Source of truth, from reason-machines/trending-skills.


name: openviking-context-database description: Expert skill for using OpenViking, the open-source context database for AI Agents that manages memory, resources, and skills via a filesystem paradigm. triggers:

  • set up OpenViking for my AI agent
  • how do I use OpenViking context database
  • configure OpenViking with my LLM provider
  • add memory to my AI agent with OpenViking
  • OpenViking filesystem context management
  • integrate OpenViking RAG into my project
  • OpenViking agent memory and skills setup
  • how to query OpenViking context database

OpenViking Context Database

Skill by ara.so — Daily 2026 Skills collection.

OpenViking is an open-source context database for AI Agents that replaces fragmented vector stores with a unified filesystem paradigm. It manages agent memory, resources, and skills in a tiered L0/L1/L2 structure, enabling hierarchical context delivery, observable retrieval trajectories, and self-evolving session memory.


Installation

Python Package

pip install openviking --upgrade --force-reinstall

Optional Rust CLI

# Install via script
curl -fsSL https://raw.githubusercontent.com/volcengine/OpenViking/main/crates/ov_cli/install.sh | bash

# Or build from source (requires Rust toolchain)
cargo install --git https://github.com/volcengine/OpenViking ov_cli

Prerequisites

  • Python 3.10+
  • Go 1.22+ (for AGFS components)
  • GCC 9+ or Clang 11+ (for core extensions)

Configuration

Create ~/.openviking/ov.conf:

{
  "storage": {
    "workspace": "/home/user/openviking_workspace"
  },
  "log": {
    "level": "INFO",
    "output": "stdout"
  },
  "embedding": {
    "dense": {
      "api_base": "https://api.openai.com/v1",
      "api_key": "$OPENAI_API_KEY",
      "provider": "openai",
      "dimension": 1536,
      "model": "text-embedding-3-large"
    },
    "max_concurrent": 10
  },
  "vlm": {
    "api_base": "https://api.openai.com/v1",
    "api_key": "$OPENAI_API_KEY",
    "provider": "openai",
    "model": "gpt-4o",
    "max_concurrent": 100
  }
}

Note: OpenViking reads api_key values as strings; use environment variable injection at startup rather than literal secrets.

Provider Options

RoleProvider ValueExample Model
VLMopenaigpt-4o
VLMvolcenginedoubao-seed-2-0-pro-260215
VLMlitellmclaude-3-5-sonnet-20240620, ollama/llama3.1
Embeddingopenaitext-embedding-3-large
Embeddingvolcenginedoubao-embedding-vision-250615
Embeddingjinajina-embeddings-v3

LiteLLM VLM Examples

{
  "vlm": {
    "provider": "litellm",
    "model": "claude-3-5-sonnet-20240620",
    "api_key": "$ANTHROPIC_API_KEY"
  }
}
{
  "vlm": {
    "provider": "litellm",
    "model": "ollama/llama3.1",
    "api_base": "http://localhost:11434"
  }
}
{
  "vlm": {
    "provider": "litellm",
    "model": "deepseek-chat",
    "api_key": "$DEEPSEEK_API_KEY"
  }
}

Core Concepts

Filesystem Paradigm

OpenViking organizes agent context like a filesystem:

workspace/
├── memories/          # Long-term agent memories (L0 always loaded)
│   ├── user_prefs/
│   └── task_history/
├── resources/         # External knowledge, documents (L1 on demand)
│   ├── codebase/
│   └── docs/
└── skills/            # Reusable agent capabilities (L2 retrieved)
    ├── coding/
    └── analysis/

Tiered Context Loading (L0/L1/L2)

  • L0: Always loaded — core identity, persistent preferences
  • L1: Loaded on demand — relevant resources fetched per task
  • L2: Semantically retrieved — skills pulled by similarity search

This tiered approach minimizes token consumption while maximizing context relevance.


Python API Usage

Basic Setup

import os
from openviking import OpenViking

# Initialize with config file
ov = OpenViking(config_path="~/.openviking/ov.conf")

# Or initialize programmatically
ov = OpenViking(
    workspace="/home/user/openviking_workspace",
    vlm_provider="openai",
    vlm_model="gpt-4o",
    vlm_api_key=os.environ["OPENAI_API_KEY"],
    embedding_provider="openai",
    embedding_model="text-embedding-3-large",
    embedding_api_key=os.environ["OPENAI_API_KEY"],
    embedding_dimension=1536,
)

Managing a Context Namespace (Agent Brain)

# Create or open a namespace (like a filesystem root for one agent)
brain = ov.namespace("my_agent")

# Add a memory file
brain.write("memories/user_prefs.md", """
# User Preferences
- Language: Python
- Code style: PEP8
- Preferred framework: FastAPI
""")

# Add a resource document
brain.write("resources/api_docs/stripe.md", open("stripe_docs.md").read())

# Add a skill
brain.write("skills/coding/write_tests.md", """
# Skill: Write Unit Tests
When asked to write tests, use pytest with fixtures.
Always mock external API calls. Aim for 80%+ coverage.
""")

Querying Context

# Semantic search across the namespace
results = brain.search("how does the user prefer code to be formatted?")
for result in results:
    print(result.path, result.score, result.content[:200])

# Directory-scoped retrieval (recursive)
skill_results = brain.search(
    query="write unit tests for a FastAPI endpoint",
    directory="skills/",
    top_k=3,
)

# Direct path read (L0 always available)
prefs = brain.read("memories/user_prefs.md")
print(prefs.content)

Session Memory & Auto-Compression

# Start a session — OpenViking tracks turns and auto-compresses
session = brain.session("task_build_api")

# Add conversation turns
session.add_turn(role="user", content="Build me a REST API for todo items")
session.add_turn(role="assistant", content="I'll create a FastAPI app with CRUD operations...")

# After many turns, trigger compression to extract long-term memory
summary = session.compress()
# Compressed insights are automatically written to memories/

# End session — persists extracted memories
session.close()

Retrieval Trajectory (Observable RAG)

# Enable trajectory tracking to observe retrieval decisions
with brain.observe() as tracker:
    results = brain.search("authentication best practices")
    
trajectory = tracker.trajectory()
for step in trajectory.steps:
    print(f"[{step.level}] {step.path} → score={step.score:.3f}")
    # Output:
    # [L0] memories/user_prefs.md → score=0.82
    # [L1] resources/security/auth.md → score=0.91
    # [L2] skills/coding/jwt_auth.md → score=0.88

Common Patterns

Pattern 1: Agent with Persistent Memory

import os
from openviking import OpenViking

ov = OpenViking(config_path="~/.openviking/ov.conf")
brain = ov.namespace("coding_agent")

def agent_respond(user_message: str, conversation_history: list) -> str:
    # Retrieve relevant context
    context_results = brain.search(user_message, top_k=5)
    context_text = "\n\n".join(r.content for r in context_results)
    
    # Build prompt with retrieved context
    system_prompt = f"""You are a coding assistant.

## Relevant Context
{context_text}
"""
    # ... call your LLM here with system_prompt + conversation_history
    response = call_llm(system_prompt, conversation_history, user_message)
    
    # Store interaction for future memory
    brain.session("current").add_turn("user", user_message)
    brain.session("current").add_turn("assistant", response)
    
    return response

Pattern 2: Hierarchical Skill Loading

# Register skills from a directory structure
import pathlib

skills_dir = pathlib.Path("./agent_skills")
for skill_file in skills_dir.rglob("*.md"):
    relative = skill_file.relative_to(skills_dir)
    brain.write(f"skills/{relative}", skill_file.read_text())

# At runtime, retrieve only relevant skills
def get_relevant_skills(task: str) -> list[str]:
    results = brain.search(task, directory="skills/", top_k=3)
    return [r.content for r in results]

task = "Refactor this class to use dependency injection"
skills = get_relevant_skills(task)
# Returns only DI-related skills, not all registered skills

Pattern 3: RAG over Codebase

import subprocess
import pathlib

brain = ov.namespace("codebase_agent")

# Index a codebase
def index_codebase(repo_path: str):
    for f in pathlib.Path(repo_path).rglob("*.py"):
        content = f.read_text(errors="ignore")
        # Store with relative path as key
        rel = f.relative_to(repo_path)
        brain.write(f"resources/codebase/{rel}", content)

index_codebase("/home/user/myproject")

# Query with directory scoping
def find_relevant_code(query: str) -> list:
    return brain.search(
        query=query,
        directory="resources/codebase/",
        top_k=5,
    )

hits = find_relevant_code("database connection pooling")
for h in hits:
    print(h.path, "\n", h.content[:300])

Pattern 4: Multi-Agent Shared Context

# Agent 1 writes discoveries
agent1_brain = ov.namespace("researcher_agent")
agent1_brain.write("memories/findings/api_rate_limits.md", """
# API Rate Limits Discovered
- Stripe: 100 req/s in live mode
- SendGrid: 600 req/min
""")

# Agent 2 reads shared workspace findings
agent2_brain = ov.namespace("coder_agent")
# Cross-namespace read (if permitted)
shared = ov.namespace("shared_knowledge")
rate_limits = shared.read("memories/findings/api_rate_limits.md")

CLI Commands (ov_cli)

# Check version
ov --version

# List namespaces
ov namespace list

# Create a namespace
ov namespace create my_agent

# Write context file
ov write my_agent/memories/prefs.md --file ./prefs.md

# Read a file
ov read my_agent/memories/prefs.md

# Search context
ov search my_agent "how to handle authentication" --top-k 5

# Show retrieval trajectory for a query
ov search my_agent "database migrations" --trace

# Compress a session
ov session compress my_agent/task_build_api

# List files in namespace
ov ls my_agent/skills/

# Delete a context file
ov rm my_agent/resources/outdated_docs.md

# Export namespace to local directory
ov export my_agent ./exported_brain/

# Import from local directory
ov import ./exported_brain/ my_agent_restored

Troubleshooting

Config Not Found

# Verify config location
ls -la ~/.openviking/ov.conf

# OpenViking also checks OV_CONFIG env var
export OV_CONFIG=/path/to/custom/ov.conf

Embedding Dimension Mismatch

If you switch embedding models, the stored vector dimensions will conflict:

# Check current dimension setting vs stored index
# Solution: re-index after model change
brain.reindex(force=True)

Workspace Permission Errors

# Ensure workspace directory is writable
chmod -R 755 /home/user/openviking_workspace

# Check disk space (embedding indexes can be large)
df -h /home/user/openviking_workspace

LiteLLM Provider Not Detected

# Use explicit prefix for ambiguous models
{
  "vlm": {
    "provider": "litellm",
    "model": "openrouter/anthropic/claude-3-5-sonnet",  # full prefix required
    "api_key": "$OPENROUTER_API_KEY",
    "api_base": "https://openrouter.ai/api/v1"
  }
}

High Token Usage

Enable tiered loading to reduce L1/L2 fetches:

# Scope searches tightly to avoid over-fetching
results = brain.search(
    query=user_message,
    directory="skills/relevant_domain/",  # narrow scope
    top_k=2,                               # fewer results
    min_score=0.75,                        # quality threshold
)

Slow Indexing on Large Codebases

# Increase concurrency in config
{
  "embedding": {
    "max_concurrent": 20  # increase from default 10
  },
  "vlm": {
    "max_concurrent": 50
  }
}

# Or batch-write with async
import asyncio

async def index_async(files):
    tasks = [brain.awrite(f"resources/{p}", c) for p, c in files]
    await asyncio.gather(*tasks)

Environment Variables Reference

VariablePurpose
OV_CONFIGPath to ov.conf override
OPENAI_API_KEYOpenAI API key for VLM/embedding
ANTHROPIC_API_KEYAnthropic Claude via LiteLLM
DEEPSEEK_API_KEYDeepSeek via LiteLLM
GEMINI_API_KEYGoogle Gemini via LiteLLM
OV_LOG_LEVELOverride log level (DEBUG, INFO, WARN)
OV_WORKSPACEOverride workspace path

Resources