[ENHANCEMENT] Openrouter provider supports reasoning_details

Problem (one or two sentences)

OpenRouter reasoning details aren't preserved between conversation turns, breaking reasoning continuity for models like MiniMax-M2

Context (who is affected and when)

Users of Roo Code who use OpenRouter as their API provider with reasoning-capable models are affected during multi-turn conversations. This impacts the quality of responses in complex tasks that require the model to build upon previous reasoning, such as debugging sessions, architectural discussions, or iterative problem-solving workflows.

Desired behavior (conceptual, not technical)

When using reasoning-capable models through OpenRouter, the system should preserve the model's reasoning traces throughout the conversation. This allows the model to reference and build upon its previous reasoning in subsequent responses, maintaining a coherent thought process across multiple turns and improving the quality of assistance for complex, multi-step tasks.

Constraints / preferences (optional)

No response

Request checklist

I've searched existing Issues and Discussions for duplicates
This describes a specific problem with clear context and impact

Roo Code Task Links (optional)

No response

Acceptance criteria (optional)

No response

Proposed approach (optional)

No response

Trade-offs / risks (optional)

No response

feat: preserve reasoning details for OpenRouter models between conver…

additional context:

This also impacts models like Gemini 3 Flash

Date/time: 2025-12-19T10:49:16.974Z
Extension version: 3.36.14
Provider: openrouter
Model: google/gemini-3-flash-preview

OpenRouter completion error: Gemini models require OpenRouter reasoning details to be preserved in each request. Please refer to our docs: https://openrouter.ai/docs/guides/best-practices/reasoning-tokens#preserving-reasoning-blocks. Upstream error: {
  "error": {
    "code": 400,
    "message": "Unable to submit request because function call `default_api:update_todo_list` in the 16. content block is missing a `thought_signature`. Learn more: https://docs.cloud.google.com/vertex-ai/generative-ai/docs/thought-signatures",
    "status": "INVALID_ARGUMENT"
  }
}

Navigation Menu

Repository navigation

[ENHANCEMENT] Openrouter provider supports reasoning_details #9125

Problem (one or two sentences)

Context (who is affected and when)

Desired behavior (conceptual, not technical)

Constraints / preferences (optional)

Request checklist

Roo Code Task Links (optional)

Acceptance criteria (optional)

Proposed approach (optional)

Trade-offs / risks (optional)

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

[ENHANCEMENT] Openrouter provider supports reasoning_details #9125

Description

Problem (one or two sentences)

Context (who is affected and when)

Desired behavior (conceptual, not technical)

Constraints / preferences (optional)

Request checklist

Roo Code Task Links (optional)

Acceptance criteria (optional)

Proposed approach (optional)

Trade-offs / risks (optional)

Activity

piiq commented on Dec 19, 2025

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions