Bug type
Regression (worked before, now fails)
Summary
All OpenClaw tools with required parameters are failing validation because they receive empty {} arguments instead of the correctly passed parameters. The Gateway appears to be failing to parse parameters before they reach the tool implementation.
Example: Sending {"command": "echo test"} to exec tool results in error: Validation failed: command: must have required property 'command'. Received arguments: {}
Steps to reproduce
Steps to reproduce the behavior:
- Install OpenClaw: npm install -g [email protected]
- Restart gateway: openclaw gateway restart
- Attempt to use any tool with required parameters (exec, read, write, sessions_spawn, etc.)
- All tools fail with "must have required property" error despite correct parameter syntax
Expected behavior
Tools should receive the correctly passed parameters and execute successfully. For example, exec with {"command": "echo test"} should execute the command.
Actual behavior
All tools receive empty {} arguments, causing validation failures:
| Tool |
Error Message |
exec |
Validation failed: command: must have required property 'command'. Received arguments: {} |
read |
Missing required parameter: path alias |
write |
Validation failed: content: must have required property 'content'. Received arguments: {} |
edit |
Missing required parameters: path alias, oldText alias, newText alias |
sessions_spawn |
Validation failed: task: must have required property 'task'. Received arguments: {} |
web_fetch |
Validation failed: url: must have required property 'url'. Received arguments: {} |
process |
Validation failed: action: must have required property 'action'. Received arguments: {} |
Environment
OpenClaw Version: 2026.3.24 (also tested 2026.3.22)
OS: Windows 10
Node.js: v24.14.0
Shell: PowerShell
Install Method: npm install -g [email protected]
OpenClaw version
2026.3.24
Operating system
Windows 10
Install method
npm install
Model
Kimi code
Provider / routing chain
openclaw -> local-gateway (port 18789) -> kimi-api (anthropic-messages) -> kimi-code
Additional provider/model setup details
No response
Logs, screenshots, and evidence
Impact and severity
Impact: Complete automation blockage - cannot spawn agents, read/write files, execute commands, or fetch web data.
Additional information
Additional context
Attempted fixes:
Upgrade to 2026.3.24: Partial fix initially (exec worked ~30%), now completely broken
Downgrade to 2026.3.22: Same issue persists
Multiple gateway restarts: No effect
Environment variable fixes: No effect
Working tools: Only subagents (read-only) appears functional.
Related issues: Possibly related to #47317, #44203, #34810 based on similar parameter validation reports.
Bug type
Regression (worked before, now fails)
Summary
All OpenClaw tools with required parameters are failing validation because they receive empty {} arguments instead of the correctly passed parameters. The Gateway appears to be failing to parse parameters before they reach the tool implementation.
Example: Sending {"command": "echo test"} to exec tool results in error: Validation failed: command: must have required property 'command'. Received arguments: {}
Steps to reproduce
Steps to reproduce the behavior:
Expected behavior
Tools should receive the correctly passed parameters and execute successfully. For example, exec with {"command": "echo test"} should execute the command.
Actual behavior
All tools receive empty {} arguments, causing validation failures:
execValidation failed: command: must have required property 'command'. Received arguments: {}readMissing required parameter: path aliaswriteValidation failed: content: must have required property 'content'. Received arguments: {}editMissing required parameters: path alias, oldText alias, newText aliassessions_spawnValidation failed: task: must have required property 'task'. Received arguments: {}web_fetchValidation failed: url: must have required property 'url'. Received arguments: {}processValidation failed: action: must have required property 'action'. Received arguments: {}Environment
OpenClaw Version: 2026.3.24 (also tested 2026.3.22)
OS: Windows 10
Node.js: v24.14.0
Shell: PowerShell
Install Method: npm install -g [email protected]
OpenClaw version
2026.3.24
Operating system
Windows 10
Install method
npm install
Model
Kimi code
Provider / routing chain
openclaw -> local-gateway (port 18789) -> kimi-api (anthropic-messages) -> kimi-code
Additional provider/model setup details
No response
Logs, screenshots, and evidence
Impact and severity
Impact: Complete automation blockage - cannot spawn agents, read/write files, execute commands, or fetch web data.
Additional information
Additional context
Attempted fixes:
Upgrade to 2026.3.24: Partial fix initially (exec worked ~30%), now completely broken
Downgrade to 2026.3.22: Same issue persists
Multiple gateway restarts: No effect
Environment variable fixes: No effect
Working tools: Only subagents (read-only) appears functional.
Related issues: Possibly related to #47317, #44203, #34810 based on similar parameter validation reports.