From 05fce28ec0678a402dc6df41d2ffa072e9c8142d Mon Sep 17 00:00:00 2001 From: Shakker Date: Mon, 27 Apr 2026 12:24:59 +0100 Subject: [PATCH] docs: document installed manifest fallback cache --- docs/plugins/architecture-internals.md | 10 ++++++++++ 1 file changed, 10 insertions(+) diff --git a/docs/plugins/architecture-internals.md b/docs/plugins/architecture-internals.md index 355d7cb5271..72bd94ce88f 100644 --- a/docs/plugins/architecture-internals.md +++ b/docs/plugins/architecture-internals.md @@ -93,10 +93,20 @@ OpenClaw keeps short in-process caches for: These caches reduce bursty startup and repeated command overhead. They are safe to think of as short-lived performance caches, not persistence. +Gateway hot paths should prefer the current `PluginLookUpTable` or an explicit +manifest registry passed through the call chain. For callers that still rebuild +manifest metadata from the persisted installed plugin index, OpenClaw also keeps +a small bounded fallback cache keyed by the installed index, request shape, +config policy, runtime roots, and manifest/package file signatures. That cache is +only a fallback for repeated installed-index reconstruction; it is not a mutable +runtime plugin registry. + Performance note: - Set `OPENCLAW_DISABLE_PLUGIN_DISCOVERY_CACHE=1` or `OPENCLAW_DISABLE_PLUGIN_MANIFEST_CACHE=1` to disable these caches. +- Set `OPENCLAW_DISABLE_INSTALLED_PLUGIN_MANIFEST_REGISTRY_CACHE=1` to disable + only the installed-index manifest-registry fallback cache. - Tune cache windows with `OPENCLAW_PLUGIN_DISCOVERY_CACHE_MS` and `OPENCLAW_PLUGIN_MANIFEST_CACHE_MS`.