feat(code): trust user-declared endpoints for cold-cache policies - #5462
Merged
Mason Daugherty (mdrxy) merged 2 commits intoAug 18, 2026
Merged
Conversation
Mason Daugherty (mdrxy)
force-pushed
the
mdrxy/code/cold-cache-trusted-endpoints
branch
from
August 13, 2026 20:14
484e9e0 to
e4c26c5
Compare
Mason Daugherty (mdrxy)
force-pushed
the
mdrxy/code/cold-cache-warning
branch
from
August 14, 2026 20:50
1b9ad13 to
a0fb2c2
Compare
Mason Daugherty (mdrxy)
force-pushed
the
mdrxy/code/cold-cache-warning
branch
from
August 17, 2026 05:40
1cdc2fe to
e6fe7b3
Compare
Mason Daugherty (mdrxy)
force-pushed
the
mdrxy/code/cold-cache-trusted-endpoints
branch
from
August 17, 2026 05:52
f751d78 to
66d31d3
Compare
Mason Daugherty (mdrxy)
force-pushed
the
mdrxy/code/cold-cache-warning
branch
from
August 17, 2026 06:00
e6fe7b3 to
dd4d340
Compare
Mason Daugherty (mdrxy)
force-pushed
the
mdrxy/code/cold-cache-trusted-endpoints
branch
from
August 17, 2026 06:00
66d31d3 to
414aeaa
Compare
Mason Daugherty (mdrxy)
force-pushed
the
mdrxy/code/cold-cache-warning
branch
from
August 17, 2026 06:17
dd4d340 to
07c156a
Compare
Mason Daugherty (mdrxy)
force-pushed
the
mdrxy/code/cold-cache-trusted-endpoints
branch
from
August 17, 2026 06:17
414aeaa to
687b1cb
Compare
Mason Daugherty (mdrxy)
force-pushed
the
mdrxy/code/cold-cache-warning
branch
2 times, most recently
from
August 18, 2026 01:34
6a95f6b to
a37a4c5
Compare
Mason Daugherty (mdrxy)
force-pushed
the
mdrxy/code/cold-cache-trusted-endpoints
branch
3 times, most recently
from
August 18, 2026 03:31
2ae956b to
39a5231
Compare
Mason Daugherty (mdrxy)
force-pushed
the
mdrxy/code/cold-cache-trusted-endpoints
branch
from
August 18, 2026 03:45
39a5231 to
ada1bb7
Compare
Mason Daugherty (mdrxy)
deleted the
mdrxy/code/cold-cache-trusted-endpoints
branch
August 18, 2026 03:49
Mason Daugherty (mdrxy)
added a commit
to langchain-ai/docs
that referenced
this pull request
Aug 18, 2026
…#5524) Draft documentation for two `deepagents-code` features: - [langchain-ai/deepagents#5439](langchain-ai/deepagents#5439) — warn before expensive cold-cache turns - [langchain-ai/deepagents#5462](langchain-ai/deepagents#5462) — trust user-declared endpoints for cold-cache policies Generated with AI assistance (Deep Agents Code).
Mason Daugherty (mdrxy)
pushed a commit
that referenced
this pull request
Aug 18, 2026
> [!CAUTION] > Merging this PR will automatically publish to **PyPI** and create a **GitHub release**. For the full release process, see [`.github/RELEASING.md`](https://github.com/langchain-ai/deepagents/blob/main/.github/RELEASING.md). --- _Release notes preview: keep this section in sync with the package `CHANGELOG.md`. Publish reads the merged CHANGELOG via `release.yml`, not this PR description — keep them aligned anyway so the PR stays an accurate historical record for reviewers and anyone returning later._ --- ## [0.1.57](deepagents-code==0.1.56...deepagents-code==0.1.57) (2026-08-18) ### Features - Added warnings before expensive cold-cache turns and trust user-declared endpoints for cold-cache policies ([#5439](#5439), [#5462](#5462)). - Made the chat input resizable by dragging its top border ([#5524](#5524)). - Added a `multi_select` question type to `ask_user` ([#5097](#5097)). - Added support for ACP approval modes ([#5394](#5394)). - Added `DeepSeek-V4-Pro-0813` to the model picker ([#5512](#5512)). - Show conversation turns alongside message counts ([#5571](#5571)). - Include `TERM_PROGRAM` in the resume hint ([#5548](#5548)). ### Bug Fixes - Report total context after `/offload` ([#5488](#5488)). - Fixed transcript and thread restoration issues, including hydration lag, scrolling resumed threads to the bottom, and hiding empty previous-thread hints ([#5479](#5479), [#5543](#5543), [#5552](#5552)). - Fixed Auto-mode approval handling by binding “yes” to the paired `ask_user` question and avoiding duplicate Auto denial notices ([#5038](#5038), [#5501](#5501)). - Improved reload behavior by keeping the chat input responsive during `/reload`, reporting MCP server changes, and avoiding plugin reload prompt flashes or startup hints ([#5529](#5529), [#5504](#5504), [#5500](#5500), [#5502](#5502)). - Improved dependency update UI by preserving editable fields and hiding dependency details after updates ([#5521](#5521), [#5519](#5519)). - Fixed chat UI polish issues, including detached spacer mount anchors, the unfocused input cursor, and relative timestamp toggle display ([#5516](#5516), [#5258](#5258), [#5503](#5503)). - Refresh the splash version after updates ([#5520](#5520)). _End release notes preview._ --- > [!NOTE] > A **community contributors** list and a **Special thanks** section (crediting the users who filed the issues this release's PRs closed) are appended to the GitHub release notes automatically at publish time (see [Release Pipeline](https://github.com/langchain-ai/deepagents/blob/main/.github/RELEASING.md#release-pipeline), step 3). --------- Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com> Co-authored-by: langchain-oss-automated-triage[bot] <248757908+langchain-oss-automated-triage[bot]@users.noreply.github.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Depends on #5439
Docs
Some users don't talk to model providers directly — they go through a gateway or corporate proxy (for example, LangSmith's gateway, or a company-internal relay). The cold-cache warning from #5439 stays silent for all of them, because it only trusts the provider's official API address. This PR adds a setting to say "my endpoint plays by the provider's rules," turning the warnings back on:
One entry covers every provider routed through that endpoint — no need to repeat it per provider.
Why trust is per-endpoint, not global. The warning's dollar estimates are only accurate if the thing sitting between you and the provider passes your cache settings through untouched and keeps cached data for as long as the provider documents. A proxy that quietly drops those settings would make the warning's numbers fiction. So instead of one blanket "trust everything" switch, you name the specific endpoints you've verified, and everything else stays silent.
One case stays silent even on a trusted endpoint. LangSmith's gateway can translate between API formats — for example, you can send an OpenAI-shaped request and have it answered by an Anthropic model. During that translation, your cache settings get rewritten to a generic 5-minute cache (or dropped entirely), so the provider's documented cache behavior no longer applies and any estimate would be a guess. When dcode can see a request will take one of these translated routes (the model name carries a cross-provider prefix like
openai:anthropic/claude-...), it skips the warning rather than show numbers built on wrong assumptions. Requests that stay in their own format — the normal case — are forwarded by the gateway byte-for-byte (verified against the gateway source), so their warnings remain exactly as accurate as going direct.Test plan
notsmith.langchain.com,smith.langchain.com.evil.example), and malformed config tolerance.