[Bug]: OpenClaw memory_recall tool returns 404 — API path mismatch with OpenViking 0.3.2

[fkc0p]

Bug type

Behavior bug — OpenClaw plugin compatibility issue with OpenViking 0.3.2

Summary

The OpenClaw openviking plugin's memory_recall tool calls POST /api/v1/memory/recall, which does not exist in OpenViking 0.3.2. The correct endpoint is POST /api/v1/search/search.

Meanwhile, the context engine (auto-recall via before_prompt_build) within the same plugin uses the correct /api/v1/search/search path and works fine — it successfully injects relevant-memories into every message. This means two code paths within the same OpenClaw plugin are targeting different API routes.

Steps to reproduce

1. Install OpenClaw 2026.4.1 with OpenViking 0.3.2 (pip install openviking)
2. Enable the openviking plugin in openclaw.json:

   "openviking": {
     "enabled": true,
     "config": {
       "mode": "local",
       "configPath": "/home/user/.openviking/ov.conf",
       "port": 1933
     }
   }

3. Store a memory via memory_store tool → succeeds (data written to session)
4. Wait for extraction to complete → memory appears in relevant-memories header ✅
5. Use memory_recall tool to search for the same memory → returns "No relevant memories found" ❌

Expected behavior

memory_recall should return matching memories from OpenViking, consistent with the auto-recall context engine results.

Actual behavior

memory_recall always returns empty. OpenViking access log shows:

"POST /api/v1/memory/recall HTTP/1.1" 404

OpenViking 0.3.2 API surface (from /openapi.json) has no /api/v1/memory/* routes. The search endpoints are:

• POST /api/v1/search/search ← correct endpoint
• POST /api/v1/search/find
• POST /api/v1/search/grep
• POST /api/v1/search/glob

Evidence

Manual curl to the correct endpoint returns results:

curl -s http://127.0.0.1:1933/api/v1/search/search \
  -X POST -H "Content-Type: application/json" \
  -d '{"query":"咖啡","limit":5}'
# → returns matching memory with score 0.64

The context engine's auto-recall works correctly every time, proving data exists and is searchable.

Root cause

The OpenClaw openviking plugin (bundled in OpenClaw dist) has two separate code paths:

1. Context engine (before_prompt_build / auto-recall) → calls /api/v1/search/search ✅
2. memory_recall tool → calls /api/v1/memory/recall ❌ (404)

The plugin source is maintained at examples/openclaw-plugin in this repo. The tool path appears to target an API spec that does not match OpenViking 0.3.2.

Environment

• OpenViking: 0.3.2 (latest on PyPI as of 2026-04-02)
• OpenClaw: 2026.4.1 (da64a97)
• OS: Linux (Kali, kernel 6.18.12)
• Python: 3.13

Additional notes

• memory_store and memory_forget tools may have similar path issues (not fully tested, memory_store did write to sessions but committed 0 memories initially)
• VLM extraction pipeline also has issues — 智谱 glm-4.5-flash 429 rate limiting causes summary generation failures (separate issue)
• OpenClaw plugin maintainers per OpenViking Maintainer Map / 模块找人地图与贡献入口 #1082: @Mijamind719 @wlff123

[qin-ctx]

Thanks for reporting this.

I checked the current OpenViking repo and the situation is slightly different from the root-cause description in this issue:

1. OpenViking server does not expose POST /api/v1/memory/recall.
   The current server routes under /api/v1/search/*, including /api/v1/search/find and /api/v1/search/search.

2. In the current examples/openclaw-plugin source, memory_recall is not calling /api/v1/memory/recall.
   It goes through the client find() path, which sends POST /api/v1/search/find.

3. The current auto-recall path in the same plugin also uses find(), not /api/v1/search/search.

So based on the current repo state, this does not look like a bug in OpenViking server routing, and it also does not match the current examples/openclaw-plugin implementation.

Our current assessment is that the 404 you observed is likely coming from a different or older OpenClaw-bundled plugin build, rather than from the current plugin source in this repository.

If you can share one of the following, we can help narrow it down further:

• the exact OpenClaw plugin source file or packaged dist file that issues POST /api/v1/memory/recall
• the corresponding OpenClaw commit / release artifact
• a request log showing which component emitted that path

If the packaged OpenClaw distribution is still shipping an older plugin implementation, then that would be a compatibility bug on the OpenClaw plugin packaging side rather than a missing OpenViking API endpoint.

Thanks again for the report.