feat: expose autoRecallTimeoutMs in plugin configuration schema#442
Draft
Displayer226 wants to merge 1 commit intoCortexReach:masterfrom
Draft
feat: expose autoRecallTimeoutMs in plugin configuration schema#442Displayer226 wants to merge 1 commit intoCortexReach:masterfrom
Displayer226 wants to merge 1 commit intoCortexReach:masterfrom
Conversation
AliceLJY
approved these changes
Apr 2, 2026
Collaborator
AliceLJY
left a comment
There was a problem hiding this comment.
LGTM. Clean, focused change.
What it does: Exposes the already-used autoRecallTimeoutMs config key in the plugin JSON schema so it becomes user-configurable through the standard config validation path.
Verified:
- The code in
index.tsalready readsconfig.autoRecallTimeoutMswith a fallback to5000, so the default here matches. - The
type: "integer"+minimum: 1+maximum: 60000constraints are reasonable — consistent with other timeout fields in the schema (e.g.,memoryReflection.timeoutMsusesminimum: 1000, maximum: 120000;llm.timeoutMsusesminimum: 1). - Placement between
autoRecallMinRepeatedandautoRecallMaxItemsfollows the existing naming group. - No behavioral change for existing users since the default matches the hardcoded fallback.
One minor note (non-blocking): minimum: 1 allows values like 1ms or 10ms which would effectively guarantee a timeout on every call. The memoryReflection.timeoutMs field uses minimum: 1000 as a floor. A minimum of ~500ms might be more practical, but this is fine as-is — users setting 1ms get what they asked for.
Approved.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Exposes
autoRecallTimeoutMsin the plugin configuration schema.Motivation
Users running local embedding or reranking services (e.g., Jina, TEI, or local Ollama instances) often encounter "auto-recall timed out" warnings during agent startup when their hardware has higher latency. Currently, this value is hardcoded or difficult to adjust via the standard config schema.
This change allows users to increase the timeout to match their specific infrastructure needs, ensuring stable memory injection.
Key Changes
autoRecallTimeoutMsto the properties inopenclaw.plugin.json.1msand a default of5000msto maintain backward compatibility while allowing flexibility.Testing
openclaw config validatepasses with the new key.autoRecallTimeoutMs: 15000in a live environment successfully prevents timeouts on slower local inference setups.