reasoning & thinking for openrouter

[khoaofgod]

I tested but I could not do anything with thinking on OpenRouter, I added reasoning { enabled: true} already, but look like model still not think or streaming thinking data out.
is there anyway to output streaming thinking and make it think?

[Ganesh-403]

@khoaofgod
Whether this works depends on both Flowise and the model/provider.

From what I can tell:

• Flowise has added reasoning support in recent releases. :contentReference[oaicite:0]{index=0}
• However, streaming reasoning ("thinking") is only possible if the provider and model expose reasoning tokens/events through their API. Flowise can't stream reasoning that the upstream API doesn't send.

So if you've already configured:

{
  "reasoning": {
    "enabled": true
  }
}

and you're still not seeing any thinking output, here are the most likely causes:

1. The selected OpenRouter model doesn't expose reasoning

Not every model on OpenRouter supports reasoning, and among those that do, not all expose the reasoning trace or stream it back to clients.

Some models only use internal reasoning and return the final answer.

2. OpenRouter may not stream reasoning content

Even if a model supports reasoning, OpenRouter must forward those reasoning events in its streaming API. I couldn't find documentation confirming that all reasoning-capable models stream their thinking through OpenRouter.

3. Flowise may not yet render streaming reasoning

I also couldn't find documentation stating that Flowise currently displays streamed reasoning tokens from OpenRouter in the chat UI. It's possible Flowise only consumes the final completion even when reasoning is enabled.

Things to verify

• Which Flowise version are you using?
• Which OpenRouter model are you testing? (e.g. qwen, deepseek, gpt-5, claude, etc.)
• Does the same model return reasoning if you call the OpenRouter API directly (outside of Flowise)?

If it does stream reasoning via the raw OpenRouter API but not through Flowise, that would suggest a Flowise integration limitation or bug.

If it doesn't stream reasoning via the raw API either, then the limitation is likely with the selected model or OpenRouter's implementation rather than Flowise.

So, at this point I would first verify whether the behavior exists outside Flowise before concluding it's a Flowise issue.

If this solves your problem, feel free to mark it as the accepted answer so others can find it easily.