Issue Station
Sign In
Tools hereToolbox

openclaw - 💡(How to fix) Fix [Bug]: doctor emits repeated tool-policy removal audit lines at normal console level

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…

openclaw doctor emits repeated agents/tool-policy audit lines at normal console level for expected profile filtering.

Root Cause

openclaw doctor emits repeated agents/tool-policy audit lines at normal console level for expected profile filtering.

Fix Action

Fix / Workaround

Local workaround verified

Code Example

[agents/tool-policy] tool policy removed 5 tool(s) via tools.profile (coding): agents_list, gateway, message, nodes, tts
RAW_BUFFERClick to expand / collapse

Summary

openclaw doctor emits repeated agents/tool-policy audit lines at normal console level for expected profile filtering.

Version

OpenClaw 2026.5.27 (27ae826)

Observed

With tools.profile set to coding, running doctor printed this line repeatedly before the doctor report:

[agents/tool-policy] tool policy removed 5 tool(s) via tools.profile (coding): agents_list, gateway, message, nodes, tts

In the reproduced case it appeared five times during one doctor run. The doctor itself completed successfully.

Why this looks like a bug

The message appears to be an audit/debug signal for expected tool-profile filtering, not an actionable doctor finding. At info/normal console level it makes the doctor output look noisy and potentially broken, even though the tool removal is expected under the selected profile.

No raw local logs, session ids, tokens, provider command output, project ids, or environment values are included here.

Expected

One of:

  • log this at debug/file-audit level only;
  • suppress it during doctor/tool schema probing;
  • dedupe it per doctor run.

Local workaround verified

Changing the tool-policy audit emission for removed tools from info to debug removed the repeated lines from normal doctor output while preserving the diagnostic path for verbose/debug logging.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING