openclaw - 💡(How to fix) Fix [Bug] memory_store tool fails when contextEngineRef is null (lazy initialization) [1 participants]

Problem

The memory_store tool returns error "Either sessionKey or sessionId is required to store memory." even when sessionKey parameter is provided.

Root Cause

In extensions/openviking/index.ts (lines 260-270), the tool checks for contextEngineRef before resolving the session:

if (!sessionId && sessionKeyIn && contextEngineRef) {
  sessionId = await contextEngineRef.resolveOVSession(sessionKeyIn);
}
if (!sessionId) {
  return { content: [{ type: "text", text: "Either sessionKey or sessionId is required to store memory." }] };
}

However, contextEngineRef is set via a factory function registered with api.registerContextEngine(), which is lazily initialized. When memory_store is called before the factory is invoked, contextEngineRef is still null.

Since resolveOVSession simply returns the sessionKey unchanged (context-engine.ts line 189), the check for contextEngineRef is unnecessary and causes the tool to fail.

Expected Behavior

memory_store should accept sessionKey and use it directly as the sessionId when contextEngineRef is not yet initialized.

Actual Behavior

Tool returns error even when valid sessionKey is provided.

Steps to Reproduce

1. Start OpenClaw with OpenViking plugin enabled
2. Call memory_store with sessionKey parameter early in session
3. Receive error: "Either sessionKey or sessionId is required to store memory."

Suggested Fix

// Before
if (!sessionId && sessionKeyIn && contextEngineRef) {
  sessionId = await contextEngineRef.resolveOVSession(sessionKeyIn);
}

// After
if (!sessionId && sessionKeyIn) {
  sessionId = contextEngineRef 
    ? await contextEngineRef.resolveOVSession(sessionKeyIn)
    : sessionKeyIn;
}

Environment

• OpenClaw version: 2026.3.23-2
• OpenViking plugin: local mode
• Node.js: v22.22.1

Related

• #52145 (shared mutable client agentId issue)