I’ve been incredibly pleased with DeepSeek this past week. Wonderful product, I love seeing its brain when it’s thinking.
I’ve been incredibly pleased with DeepSeek this past week. Wonderful product, I love seeing its brain when it’s thinking.
> Please note that if the reasoning_content field is included in the sequence of input messages, the API will return a 400 error. Therefore, you should remove the reasoning_content field from the API response before making the API request
So the best I can do is pass the reasoning as part of the context (which means starting over from the beginning).
would be nice if they made them visible now
Nevertheless, R1's reasoning chains are already shorter in tokens than o1's while having similar results, and apparently o3-mini's too.
from way how it thinks/responds looks like it's one of destinations , likely llama one I also suspect that many of free/cheap providers also serve llama instead of real R1
[0] https://www.perplexity.ai/search/how-can-i-construct-a-list-...
I think you misread something. AWS mainly offers the full size model on Bedrock: https://aws.amazon.com/blogs/aws/deepseek-r1-models-now-avai...
They talk about how to import the distilled models and deploy those if you want, but AWS does not appear to be officially supporting those.
https://aws.amazon.com/blogs/machine-learning/deploy-deepsee...
I gave the same prompt to sonnet 3.5 and not a single hiccup.
Maybe not an indication that Deepseek is worse/bad (I am using a distilled version), but moreso speaks to much react/nextjs is out in the world influencing the front-end code that is referenced.
This tracks when considering that the model was trained on western model outputs and then tuned post-training to (poorly) align it with Chinese values.
They have under utilized the chain of thought in their resoning, it ought to be thinking something like "I need to be careful to not say anything that could bring embarrassment to the party"..
but perhaps the online versions do actually preload the reasoning this way. :P