[yonib05]

Human Overview

Description

Users running OpenAI reasoning models through the Responses provider in the default stateless mode lose the model's earlier reasoning on every model call in a tool loop. Both SDKs drop reasoning blocks from history with only a log warning and never request reasoning.encrypted_content, so nothing on the docs page tells users this happens or how to avoid it.

This adds a short "Reasoning Models" section to the OpenAI Responses page that shows how to set reasoning effort through params, states the stateless-mode limitation for both SDKs, points to server-side conversation state (stateful), which chains on previous_response_id with store: true and so keeps prior reasoning on OpenAI's side, and links the tracking issue. The note can be removed once #3389 lands.

Related Issues

#3389

Documentation PR

This PR is the documentation change.

Type of Change

Documentation update

Testing

Checked the claims against strands-ts/src/models/openai/responses-adapter.ts (formatResponsesMessages, formatResponsesRequest) and strands-py/src/strands/models/openai_responses.py (_format_request_messages, _format_request). Ran npm run build in site/ (no broken links) and confirmed the section and <Syntax> toggle render. npm run typecheck passes; npm run format:check and npm test report the same pre-existing failures as clean main.

• I ran hatch run prepare

Checklist

• I have read the CONTRIBUTING document
• I have reviewed and understand every line of code in this PR, including any generated by AI tools, and I can explain why it works
• My change is focused and reasonably small; I have split unrelated work into separate PRs
• I have added any necessary tests that prove my fix is effective or my feature works
• I have updated the documentation accordingly
• I have added an appropriate example to the documentation to outline the feature, or no new docs are needed
• My changes generate no new warnings
• Any dependent changes have been merged and published

---

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

[yonib05]

Closing: we're merging the fix itself (#3419) instead of documenting the limitation.