ov-memory-doctor

Diagnose and fix OpenViking memory plugin install, configuration, and server connection failures.

34.8k|2.7k|Updated Jan 5, 2026
One-click install
npx skills add https://github.com/volcengine/OpenViking --skill ov-memory-doctor
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ov-memory-doctor
Source: https://github.com/volcengine/OpenViking/tree/main/examples/claude-code-memory-plugin/skills/ov-memory-doctor
Command: npx skills add https://github.com/volcengine/OpenViking --skill ov-memory-doctor

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

When the OpenViking memory plugin for Claude Code silently stops working — no context injection, empty recall, captures not landing, or MCP tools failing with 401/403 — this Skill pinpoints the root cause across the plugin install, client configuration, and server connection instead of leaving you to guess.

Core Features & Use Cases

  • Automated diagnostic report: Runs a doctor script covering six sections — Environment, Plugin install, Configuration, Connection, Server health, and Recent activity — with a summary of every failure and its fix.
  • Finding-to-fix mapping: A lookup table translates each doctor finding (e.g., unparseable ovcli.conf, rejected API key, stale plugin cache, proxy/TLS issues) into a concrete remediation step.
  • Targeted manual probes: Provides curl and CLI commands to verify hooks, API key identity, the /mcp endpoint, and capture delivery when the report is inconclusive.
  • Use Case: After updating the plugin your statusline shows offline and recall returns nothing; run the doctor, find that an env var is overriding ovcli.conf, remove it, and confirm the fix with a rerun.

Quick Start

Ask the assistant to run the OpenViking memory doctor and diagnose why the memory plugin is not working on this machine.

Frequently Asked Questions about ov-memory-doctor

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I troubleshoot the OpenViking memory plugin not working?

Run the ov-memory-doctor.mjs script from the plugin's scripts directory. It produces a six-section report covering environment, install, configuration, connection, server health, and recent activity, with each failure mapped to a specific fix.

Why is OpenViking recall empty even though the server is healthy?

Empty recall usually means a rejected API key (a 401 reads as no results), a wrong account or user identity, peer-scope filtering, or a score threshold that is too high. Check last-recall.json for the reason field and verify the key against /api/v1/system/status.

Why does the OpenViking statusline show green but MCP tools return 401?

The /health endpoint answers 200 without authentication, so a green statusline only proves reachability. A 401 on MCP tools means the API key is invalid, revoked, or belongs to a different deployment; re-issue the key and update ovcli.conf.

Does the OpenViking plugin work behind a corporate proxy or private CA?

Node's fetch ignores HTTP(S)_PROXY and custom CAs by default, so curl may work while the plugin fails. Set NODE_USE_ENV_PROXY=1 or NODE_EXTRA_CA_CERTS in the env block of ~/.claude/settings.json for the environment that launches Claude Code.

Why did claude plugin update not fix my OpenViking plugin bug?

Claude Code caches plugins by version string, so an update is a no-op when the version did not change. Run marketplace update, then uninstall and reinstall the plugin to force a fresh copy.

Can the memory doctor restart or fix my OpenViking server automatically?

No. The doctor is read-only and never stops, restarts, or edits the server without asking. Server-side issues like embedding or vectordb failures require running openviking-server doctor in the server's own Python environment.