openclaw - 💡(How to fix) Fix Default DEFAULT_PLUGIN_DISCOVERY_CACHE_MS / DEFAULT_PLUGIN_MANIFEST_CACHE_MS of 1 second is too short for gateway use [2 comments, 3 participants]

Environment

• openclaw \2026.4.26\
• File: \src/plugins/cache-controls.ts\

Summary

Both \DEFAULT_PLUGIN_DISCOVERY_CACHE_MS\ and \DEFAULT_PLUGIN_MANIFEST_CACHE_MS\ default to \1e3\ (1 second). This makes the \capabilityProviderPluginIdCache\ and related snapshot caches effectively useless for any conversation-paced workload — a second message arriving >1s after the first always misses.

Current Code

\\ s const DEFAULT_PLUGIN_DISCOVERY_CACHE_MS = 1e3; const DEFAULT_PLUGIN_MANIFEST_CACHE_MS = 1e3;

function resolvePluginSnapshotCacheTtlMs(env) { const discoveryCacheMs = resolvePluginCacheMs(env.OPENCLAW_PLUGIN_DISCOVERY_CACHE_MS, DEFAULT_PLUGIN_DISCOVERY_CACHE_MS); const manifestCacheMs = resolvePluginCacheMs(env.OPENCLAW_PLUGIN_MANIFEST_CACHE_MS, DEFAULT_PLUGIN_MANIFEST_CACHE_MS); return Math.min(discoveryCacheMs, manifestCacheMs); } \\

Suggested Fix

Either: (a) Raise defaults to something like \60_000\ (1 min) or \300_000\ (5 min) for gateway mode, keeping \1e3\ only for one-shot CLI invocations; (b) Auto-detect gateway context (long-running process) and use a longer default there.

Impact

Setting \OPENCLAW_PLUGIN_DISCOVERY_CACHE_MS=300000\ and \OPENCLAW_PLUGIN_MANIFEST_CACHE_MS=300000\ in the gateway launcher already provides the performance benefit — so the current defaults are the only blocker.

Workaround

Set both env vars to \300000\ in the gateway startup script.