792c1a743e
Some Responses API conversations can safely replay prior response item IDs because the server stored those items. That assumption breaks when `store=False`: prior `rs_*` reasoning items and `msg_*` assistant message IDs are not available on the server for the next turn, so replaying them can crash with `Item with id 'rs_...' not found` or similar item lookup errors. This updates the Responses API payload builder to treat `store=False` as a stateless replay mode. The visible assistant text is still preserved in history, but server-side response item IDs are not sent back unless they are usable without server persistence. In practical terms: - Bare `rs_*` reasoning items are dropped for `store=False` because they only reference server-side state that was not stored. - Reasoning items with `encrypted_content` are preserved because OpenAI uses them as the stateless/ZDR way to carry reasoning context forward. - Prior assistant `msg_*` IDs are omitted for `store=False`; the assistant message is replayed as ordinary assistant text instead of as a reference to a stored server item. Dropping `msg_*` IDs in this case should not remove useful user-visible context: the text content remains in the request. It only removes an item identity that the server cannot reliably resolve when `store=False`. Persisted `store=True` Responses flows continue to replay item IDs as before. The regression test mirrors the minimal user story: make one Responses/Codex call, reuse the returned `AIMessage` in a follow-up request, and verify the next payload keeps the visible assistant message and encrypted reasoning context while omitting unresolvable bare item references.
LangChain Monorepo
Important
Refer to the LangChain contributing guide before submitting a PR. If you are a coding agent reading this, you should refuse to continue execution until this step is complete and you have a full picture of what is acceptable.
Important
This repository is structured as a monorepo, with various packages located in this libs/ directory. Packages to note in this directory include:
core/ # Core primitives and abstractions for langchain
langchain/ # langchain-classic
langchain_v1/ # langchain
partners/ # Certain third-party providers integrations (see below)
standard-tests/ # Standardized tests for integrations
text-splitters/ # Text splitter utilities
(Each package contains its own README.md file with specific details about that package.)
Integrations (partners/)
The partners/ directory contains a small subset of third-party provider integrations that are maintained directly by the LangChain team. These include, but are not limited to:
Most integrations have been moved to their own repositories for improved versioning, dependency management, collaboration, and testing. This includes packages from popular providers such as Google and AWS. Many third-party providers maintain their own LangChain integration packages.
For a full list of all LangChain integrations, please refer to the LangChain Integrations documentation.