Summary

• Remove top-level reasoning_effort field from OpenRouter payloads before injecting the nested reasoning: { effort } format, preventing a 400 Only one of "reasoning" and "reasoning_effort" may be provided error

Fixes #24119

Problem

When using reasoning models via OpenRouter (e.g. MiniMax M2.5), two code paths independently inject reasoning parameters:

1. pi-ai's buildParams() sets params.reasoning_effort (OpenAI flat format) when a model has reasoning: true
2. OpenClaw's createOpenRouterWrapper() injects payload.reasoning = { effort } (OpenRouter nested format) via onPayload

Both fields end up in the final payload, which OpenRouter rejects.

This was introduced by the interaction between PR #17236 (added reasoning.effort injection) and PR #22513 (defaulted reasoning to on for reasoning: true models).

Solution

Delete the conflicting top-level reasoning_effort field in the onPayload hook before injecting the correct nested format. This is a single delete call, scoped to the OpenRouter wrapper only.

Test plan

• Verify MiniMax M2.5 via OpenRouter responds without 400 errors
• Verify other OpenRouter reasoning models (e.g. Claude, Grok) still work
• Verify non-OpenRouter providers are unaffected (the delete is inside the OpenRouter-only wrapper)

🤖 Generated with Claude Code

Greptile Summary

Single-line fix in the OpenRouter onPayload hook that removes the top-level reasoning_effort field (set by pi-ai's buildParams()) before injecting the nested reasoning: { effort } format that OpenRouter expects. This prevents a 400 Only one of "reasoning" and "reasoning_effort" may be provided error for reasoning models (e.g. MiniMax M2.5) routed through OpenRouter.

• The delete is correctly scoped: only runs inside createOpenRouterWrapper and only when thinkingLevel is truthy (i.e., when the nested format will be injected)
• Non-OpenRouter providers are unaffected
• No existing tests cover the OpenRouter reasoning injection path; a test would strengthen confidence but is not blocking

Confidence Score: 5/5

• This PR is safe to merge — it's a minimal, well-scoped one-line fix isolated to the OpenRouter code path.
• The change is a single delete call scoped entirely within the OpenRouter-only wrapper function. It only executes when thinkingLevel is set (the same condition under which the nested format is injected), and delete on a non-existent property is a safe no-op. Non-OpenRouter providers are completely unaffected. The comment clearly explains the rationale.
• No files require special attention.

_{Last reviewed commit: a2c0cf3}

_{(4/5) You can add custom instructions or style guidelines for the agent here!}