openclaw - 💡(How to fix) Fix [Bug]: memory compaction allowlist warning hides why core tools are unavailable [1 pull requests]

Bug type

Behavior bug (incorrect output/state without crash)

Beta release blocker

No

Summary

During a memory-triggered compaction run, tools.allow can warn that configured shipped core tools are unknown without saying that memory compaction intentionally exposes only read and append-only write.

Steps to reproduce

1. Run a memory-triggered compaction path with tools.allow configured for normal coding tools such as exec, sessions_list, and related core tools.
2. Let the memory-triggered request build its reduced tool catalog.
3. Observe the tools.allow allowlist contains unknown entries warning.

Expected behavior

The warning should identify the active gating reason when shipped core tools are configured but unavailable because the memory-triggered compaction catalog is intentionally reduced.

Actual behavior

The warning reports the configured shipped core tool names as unavailable in the generic current runtime/provider/model/config state, which makes the expected memory compaction restriction look like an unexplained config or provider failure.

OpenClaw version

NOT_ENOUGH_INFO

Operating system

NOT_ENOUGH_INFO

Install method

pnpm dev

Model

NOT_ENOUGH_INFO

Provider / routing chain

NOT_ENOUGH_INFO

Additional provider/model setup details

The observed warning occurs before provider generation, while building the active tool catalog for a memory-triggered compaction run.

Logs, screenshots, and evidence

[tools] tools.allow allowlist contains unknown entries (edit, exec, process, update_plan, sessions_list, sessions_history, sessions_send, sessions_spawn, sessions_yield, subagents, session_status, web_search, web_fetch). These entries are shipped core tools but unavailable in the current runtime/provider/model/config.

Impact and severity

Affected: memory-triggered compaction runs with a normal coding-tool allowlist. Severity: Medium; the run still proceeds with the reduced memory-safe tool catalog, but the warning sends operators toward provider/config debugging instead of the actual memory compaction restriction. Frequency: Observed once in gateway logs. Consequence: Operators cannot tell whether the configured tools are unavailable by design for the memory compaction pass or because of a provider/model/config mismatch.

Additional information

The implicated code path first reduces memory-triggered tool runs to read plus append-only write, then applies the regular tool policy warning pipeline against that reduced catalog.