$ the-wire · showcase
Faster settings startup, deferred plugin scope fix
By RepoJournal · Filed · About OpenClaw · Composed from the cited sources · methodology
OpenClaw's day is about cost per call: a settings helper that spent three seconds loading runtime config before its first write, a worktree registry that transacted against the wrong database, and a deferred CLI action that lost its plugin instance scope.
improve: reduce package metadata startup cost openclaw/openclaw
Importing FileSettingsStorage took 3.146 seconds before it could begin its first write because the settings-file helper loaded runtime configuration modules when it only needed package metadata; metadata-only imports now avoid that cold start, and the measured settings process reached its first locked callback in 142 ms, down from 3,228 ms on the same machine.
fix(plugins): preserve runtime scope for deferred CLI actions openclaw/openclaw
Registered Commander CLI actions executed after plugin registration had already left their instance scope, so the runtime store resolved an uninitialized value; the fix preserves plugin-instance runtime scope for deferred actions and installs channel runtime state for both setup and full plugin graphs. Maturity run 34681094383 had shown the Matrix E2EE CLI scenarios failing on exactly this.
fix(worktrees): preserve explicit-state registry transactions openclaw/openclaw
Worktree registry helpers using an explicit state directory could acquire a transaction on the ambient default database instead, letting valid writes fail or dropping snapshot chunks when worktree deletion failed. Registry writes now use the selected state directory consistently, a read-only unrelated default database no longer blocks them, and failed deletion preserves its snapshot chunks thro...
improve: reduce CPU for repeated session metadata reads openclaw/openclaw
Repeated session metadata reads were rebuilding identical query plans on the Gateway thread. The existing exact metadata queries and schema probes are now prepared once per database connection, cutting CPU while preserving entry, participant, and owner data and keeping callers' projection choices intact.
fix(memory): read the searched workspace for explicit agents (#147072) openclaw/openclaw
For explicitly owned multi-agent rosters relying on inherited workspace paths, memory_get returned a different file than memory_search; reads and searches now agree on the agent's workspace without a per-agent workspace pin, and explicit overrides remain authoritative. No files move and no index reset is needed.
