Mason Daughertyandopen-swe[bot]
88b972731a
Added `FireworksPromptCachingMiddleware` to improve prompt-cache reuse across calls in the same agent thread. Explicit affinity settings take precedence, and no affinity is generated without a thread ID. --- Fireworks agents need consistent routing to reuse a replica's prompt cache across turns. `FireworksPromptCachingMiddleware` supplies session affinity from a SHA-256 hash of `config.configurable.thread_id`, while respecting explicit `user`, `prompt_cache_key`, and `x-session-affinity` settings on the selected model or request. Affinity is scoped to the call and applied by `ChatFireworks` when invoking the API. Generated affinity stays out of shared request settings, and model-local headers remain scoped to their owning model, including during fallback. This works with either ordering of the caching and fallback middleware for a Fireworks primary model. Related fallback cleanup for explicitly supplied cache settings is in #40886, stacked on this PR. This PR works independently of that change. --------- Co-authored-by: open-swe[bot] <open-swe@users.noreply.github.com>
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
model-profiles/ # Model capability profiles and CLI (`langchain-model-profiles`)
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.