#Pass back reasoning_detail
1 messages · Page 1 of 1 (latest)
I'm an AI assistant - my answers may be incorrect and I cannot see screenshots. Please verify information with the OpenRouter docs.
To help debug this issue, I need a bit more information:
- What is the exact model identifier you're using for Claude (e.g.,
anthropic/claude-3-opus, etc.)? - Can you share the specific API call or code snippet you're using to pass back the
reasoning_details? - What is the full error message or response you see from the API or in the OpenRouter logs?
These details will help pinpoint if this is a model-specific limitation, an API usage issue, or something else.
-# This is an automated response powered by Answer HQ. Use !mute to stop the bot from responding, or !close when your question is resolved.
Probably an issue with the client app
But same client seems to work for Grok
Thanks for clarifying that the same client and method work for Grok models but not for Claude. To identify the root cause, I need the following details:
- What is the exact model identifier for Claude you’re using (e.g.,
anthropic/claude-3-opus,anthropic/claude-3-haiku, etc.)? - What API parameters are you sending for Claude—especially any related to reasoning, output fields, or streaming?
- Can you provide the full response or error from the Claude API call, including any relevant logs?
This information will help determine if the issue is due to model capabilities, parameter differences, or an API-specific quirk.
-# This is an automated response powered by Answer HQ. Use !mute to stop the bot from responding, or !close when your question is resolved.
can you replicate this on the OR chat?
btw, did TypingMind fix that other issue?
Great that u remember! They are working on that, but I suspect this is a separate issue because I see the diff between Grok and Claude on the OR log.
Claude does not use reasoning on the OR chat, because reasoning.enabled or reasoning.effort should be explicitly passed, i guess
you have to turn it on in the model's settings, if you hover over it
Reproduced on both OR chat and lobe chat.
The missing input tokens in the follow-up queries are the reasoning tokens of the previous reponses
<@&1384697330254610442>
this is an app implementation detail not a bug in our api