openclaw - 💡(How to fix) Fix [Bug]: Assistant turn fails before content when active custom tool schema is unsupported

Bug type

Crash (process/app exits or hangs)

Beta release blocker

No

Summary

An active custom local tool with an unsupported dynamic input schema caused assistant turns to fail before producing any content. openclaw doctor completed without clearly identifying the active tool schema as the blocker, even though the same schema later caused the real assistant runtime to fail.

Steps to reproduce

Run OpenClaw with an active custom local plugin or tool. The custom tool exposes an unsupported dynamic input schema. Start a normal assistant turn through Web UI or Telegram. The assistant turn fails before producing content. Run openclaw doctor. Doctor does not clearly identify the active tool schema as the fatal issue.

Expected behavior

OpenClaw should fail gracefully if an active tool schema is unsupported.

openclaw doctor should validate active tool schemas against the same runtime tool projection path used during actual assistant turns.

If a tool schema is unsupported, OpenClaw should clearly name the offending tool/plugin, disable or skip that tool, and allow the assistant to continue replying without it.

Actual behavior

The assistant failed before producing content. Web UI and Telegram sessions appeared stuck or broken.

openclaw doctor completed without clearly identifying the active unsupported schema as the blocker.

Runtime investigation showed an error equivalent to:

dynamic tool input schema is not supported for an active custom tool

The issue came from a custom experimental local plugin/tool, not a core OpenClaw tool.

OpenClaw version

OpenClaw 2026.5.20, build e510042

Operating system

Ubuntu 26.04 LTS

Install method

npm global install

Model

gpt-5.5

Provider / routing chain

openai-codex -> openai-codex-responses -> gpt-5.5

Additional provider/model setup details

Logs, screenshots, and evidence

Runtime investigation showed an error equivalent to:

dynamic tool input schema is not supported for an active custom tool

I no longer have the full original log line in active logs because the local system was already repaired.

Impact and severity

Affected: users running custom local tools/plugins with unsupported schemas.

Severity: high, because the assistant turn fails before producing content.

Frequency: occurs when the bad custom tool/plugin is active.

Consequence: the assistant cannot reply until the bad tool/plugin path is removed or disabled manually.

Additional information

The local workaround was:

1. Disabled/removed the bad custom plugin path from active OpenClaw config.
2. Removed the unsupported tool from active allow/config.
3. Removed stale plugin/MCP references.
4. Verified the primary model remained correct.
5. Verified fallbacks were empty.
6. Ran a fresh agent reply test successfully.

Suggested improvement:

Add a doctor/runtime validation check for active tool schemas against the actual runtime tool projection path.

Runtime tool loading should fail gracefully:

bad tool -> disable/report tool -> assistant still replies

instead of:

bad tool -> whole assistant turn fails before content