openclaw - 💡(How to fix) Fix [Bug]: New version 2026.5.12 openrouter model tool calls results in http 500 error [1 comments, 2 participants]

Bug type

Regression (worked before, now fails)

Beta release blocker

No

Summary

2026.5.12, after updating, tool calls regardless of how heavy the task, if the models is set to a single model (i.e. deepseek v4 flash, gemini 2.5 flash, etc) tool call will fail and gateway/logs will show http 500 error until it times out completely and fails. only working solution is to use openrouter auto settings in the 2026.5.12 version. Update: Additional information, another fix (the one im on) is to just roll back to 2026.5.7. seems like the new update's tool call something is wrong

Steps to reproduce

I dont know if this is a specific error with this provider only or not.

1. openrouter api key
2. create folders and files on local system and ask openclaw to read
3. wait to fail.

Expected behavior

ai first gives brief description of its process, for me it was one sentence of what its first going to do, tool calls, tool call fails, error is reflected in logs, http 500 error.

Actual behavior

response ends at tool call. after tool call fails, dashboard becomes unresponsive. context compression also fails, only dashboard reload (webpage reload) works, but original issue remains. webpage reload only unstucks the dashbopard.

OpenClaw version

2026.5.12

Operating system

windows 11

Install method

npm

Model

deepseek v4 flash, gemini 2.5 flash, hy 4 preview, etc.

Provider / routing chain

openrouter

Additional provider/model setup details

No response

Logs, screenshots, and evidence

Impact and severity

2026.5.12 regression: OpenRouter DeepSeek v4 Flash fails with HTTP 500 after tool call, older OpenClaw works

Additional information

No response