Bug: autoRecallTimeoutMs declared in PluginConfig interface but missing from parsePluginConfig return

[jlin53882]

Bug Description

autoRecallTimeoutMs is declared in the PluginConfig interface (line 105), and used in the code at line 2261:

const AUTO_RECALL_TIMEOUT_MS = parsePositiveInt(config.autoRecallTimeoutMs) ?? 3_000;

However, it is completely missing from the parsePluginConfig return object, so the user-supplied value is never parsed, always falls back to the hardcoded default of 3000ms, and the config validator rejects the setting with:

Config invalid
plugins.entries.memory-lancedb-pro.config: invalid config: must NOT have additional properties

Root Cause

parsePluginConfig (line 3733+) builds the return object but skips autoRecallTimeoutMs. The interface has it (line 105), the code reads it, but parsePluginConfig never extracts it from cfg.

Fix

Add to the parsePluginConfig return object, between autoRecallMinRepeated and autoRecallMaxItems:

autoRecallTimeoutMs: parsePositiveInt(cfg.autoRecallTimeoutMs),

Impact

• Users cannot configure autoRecallTimeoutMs via openclaw.json (validation error)
• Remote embedding APIs that need longer timeout (>5s) cannot be supported
• Fix is a one-liner addition to the return object

Environment

• Plugin version: v1.1.0-beta.10

Reference

• Fix PR: fix: parse autoRecallTimeoutMs in parsePluginConfig #466

[jlin53882]

Duplicate of Issue #360

This same bug was reported by @Lee-take on 2026-03-28 (comment #4146283938) against Issue #360, which was closed by @AliceLJY on the assumption it was fixed.

Lee-take correctly identified the root cause:

• parsePluginConfig return object was missing autoRecallTimeoutMs
• This caused openclaw.json validation to reject the field with:

  invalid config: must NOT have additional properties
  

The issue was incorrectly closed without the parsePluginConfig fix being applied.

This PR #466 provides the fix.

Original comment: #360 (comment)