## Description
Adds an "Add the `managed-deep-agents` skill" section to the Managed
Deep Agents quickstart, between Prerequisites and the build steps.
Readers who build with a coding agent get better results with the
[`managed-deep-agents`
skill](https://github.com/langchain-ai/langchain-skills/blob/main/config/skills/managed-deep-agents/SKILL.md)
installed, so the section links the skill and gives the `npx skills add
langchain-ai/langchain-skills --skill managed-deep-agents --yes` install
command.
Placement is the main thing worth a look: the skill is most useful
before the reader starts scaffolding, but it can move to Next steps if
that reads better.
Docs-only change; no new pages, so `src/docs.json` is untouched. `make
lint_prose` passes on the changed file. Written by an AI agent (Open
SWE) at the requester's direction.
## Test Plan
- [ ] Preview the quickstart page and confirm the new section renders
with the heading in code formatting.
Made by [Open
SWE](https://openswe.vercel.app/agents/25e9b868-246d-5f0a-afc6-dffbd06e42a5)
---------
Co-authored-by: Caspar Broekhuizen <25157475+casparb@users.noreply.github.com>
Co-authored-by: open-swe[bot] <open-swe@users.noreply.github.com>
Two entries in the sidebar navigation (`src/docs.json`) point to pages
that
immediately redirect the user elsewhere:
- `oss/python/langchain/retrieval` redirects to
`/oss/python/deepagents/retrieval`
- `oss/javascript/langchain/retrieval` redirects to
`/oss/javascript/deepagents/retrieval`
The content was moved to the `deepagents/` path and redirects were added
correctly, but the navigation was not updated. Every user clicking the
nav
link gets an unnecessary redirect hop instead of landing directly on the
canonical page.
Fix: update the 2 nav entries in `src/docs.json` to point directly to
`oss/python/deepagents/retrieval` and
`oss/javascript/deepagents/retrieval`.
Verified with a full pipeline build (no warnings, JSON valid). Fix
ready.
Fixes DOC-1544
## Summary
- Added a `<Note>` callout after the `helm upgrade` command in the
Kubernetes self-hosted deployment guide explaining that the namespace
must already exist before running the command
- Instructs users to either pre-create the namespace with `kubectl
create namespace <namespace>` or append `--create-namespace` to the helm
command
## Links
- Linear: https://linear.app/langchain/issue/DOC-1544
- Slack:
https://langchain.slack.com/archives/C09G1T60QV9/p1787010227131159
## Verification
- `make lint_prose` — no errors in `kubernetes.mdx` (pre-existing errors
in other files are unrelated)
- `make check-cross-refs` — ✅ all cross-references resolved
## Reviewers
Requested review from: @katmayb, @fjmorris
Co-authored-by: Docs Bot <brace@langchain.dev>
## Summary
Automated daily refresh of the LangSmith Platform API spec.
## Details
- Fetched latest spec from api.smith.langchain.com
- Applied post-processing: hid fleet/internal endpoints, added
human-readable group tags
- Output: `src/langsmith/langsmith-platform-openapi.json`
- Generated by `scripts/process_langsmith_openapi.py`
🤖 This PR was created automatically by GitHub Actions
Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
Fixes DOC-1523
## Summary
Documents the **Include extended stats** evaluator setting so users can
determine when to enable it and which data it makes available.
- Clarifies run-level support and the multi-turn evaluator limitation.
- Distinguishes `feedback_stats` from individual feedback records
available to code evaluators.
- Adds supported LLM-as-a-judge variable-mapping guidance and a
feedback-filtered chaining link.
## Validation
- `make lint_prose FILES='src/langsmith/evaluators.mdx
src/langsmith/online-evaluations-code.mdx'`
- `make broken-links-with-anchors`
## Notes
This PR was prepared with AI agent assistance and reviewed against the
LangSmith UI and backend implementation.
---------
Co-authored-by: Lauren Hirata Singh <lauren@langchain.dev>
## Summary
Rewrites one sentence in the `<Info>` block of the "Short-term memory
(State)" section on the Python tools page
(`src/oss/langchain/tools.mdx`).
Old:
> Add `runtime: ToolRuntime` to your tool signature to access state.
This parameter is automatically injected and hidden from the LLM - it
won't appear in the tool's schema.
New:
> To access state, add `runtime: ToolRuntime` to your tool signature.
When the tool runs, the runtime (for example, `ToolNode`) supplies the
value, not the model, and the parameter is omitted from the tool schema
sent to the model.
## Why
"Automatically injected" is ambiguous about who acts. Injection is
opt-in: the user declares the `runtime: ToolRuntime` parameter
themselves. What is automatic is that, once declared, the value is
supplied at call time by the runtime (e.g. `ToolNode`) rather than
generated by the model, and the parameter is omitted from the
model-facing tool schema. The new wording makes that distinction
explicit and matches the "hidden from the model" phrasing used in the
`<Warning>` further down the same page.
No other content changed. Vale prose lint passes on the edited file.
---
AI-assisted change (reviewed and verified against the repo's style
conventions).
---------
Co-authored-by: Docs Bot <brace@langchain.dev>
The sandbox pages had accumulated claims the implementation no longer
honors. Some are cosmetic; several actively break anyone who copies
them. Each item below was checked against `smith-go/sandboxes`, the
LangSmith CLI, and the SDKs.
## Wrong in a way that breaks users
- **`wait_for_ready` removed from the REST examples.** The field was
deleted from `CreateSandboxPayload` and is now silently ignored.
Creating a sandbox already boots it and returns once it reports `ready`,
so the parameter is redundant rather than load-bearing. The name
survives as a *client-side* SDK kwarg (default `True`), which is
probably how the REST examples drifted.
- **CLI `--wait` and the `wait` subcommands removed.** `--wait`,
`--timeout`, `sandbox wait`, and `snapshot wait` no longer exist, for
the same reason: `create` returns ready. Snapshot builds are genuinely
asynchronous, so those keep a documented poll.
- **CLI output default corrected.** It is human-readable tables, with
`--format json` for scripting; the docs had it backwards. Also fixed on
the CLI overview and profile pages.
- **GCS mount `scopes` removed from the examples.** The SDK drops the
field when building `mount_config.auth.gcp` and the backend rejects it
outright, deriving the scope from each mount's `read_only`. Also
documents that one `mount_config` cannot mix read-only and writable GCS
mounts.
## Wrong numbers and facts
- **Running-command idle timeout is 1 hour**, not 5 minutes. Five
minutes is the finished-session TTL, which was previously left
unnumbered and is now stated.
- **Builder sandbox default is 0.5 vCPU**, not "a single core".
- **The 2-vCPU Dockerfile builder example** paired 2 vCPU with 4 GiB,
landing exactly on the edge of the 4 GiB per vCPU tolerance. Now 8 GiB,
matching the JS SDK README.
- **AWS and GCP auth-rule limits count disabled rules too**, so "at most
one enabled GCP rule" was wrong.
- **`/tmp` is not a tmpfs.** Only `/dev/shm` is, so `/tmp` lives on the
sandbox disk and is captured. The old note claimed the opposite while
the stop/start example on the same page relied on `/tmp` persisting.
## Reachable but undocumented
Memory snapshots (`include_memory`, `restore_memory`,
`preserve_memory_on_stop`), the CPU/memory/filesystem limits, labels,
and the CLI `--vcpus` / `--memory` sizing flags. Memory snapshots are
documented as REST-only, since the `langsmith.sandbox` clients do not
expose them.
## Stop and start
Sandboxes wake on their next request, so the docs no longer walk users
through starting one by hand. Explicit `start` is gone from the prose,
examples, and the CLI command reference; `stop` stays where releasing
resources early is the point. The `start` API and CLI command still
exist, they are just no longer presented as a step you take.
## Worth a careful look
- The `/tmp` claim is the one I could not confirm on a live sandbox,
because the only endpoint configured locally is production. It rests on
three code sources agreeing: the guest init mounts only `/dev/shm` as
tmpfs, the rootfs image adds no `/tmp` tmpfs, and `e2e/snapshot_test.go`
says the same in a comment. Happy to confirm on a real box if you would
rather not take the code's word for it.
- The GCS `scopes` behavior reads as a product bug rather than a doc
bug, and is documented as-is here: the SDK silently drops a field the
backend would have rejected.
## Test plan
- [x] `make lint_prose` clean on all changed files
- [x] `make build` succeeds; the one new anchor (`#resume-from-memory`)
resolves
- [x] Every changed claim traced to the implementation in
`smith-go/sandboxes`, `langsmith-cli`, or `langsmith-sdk`
Written with Claude Code.
`src/oss/deepagents/backends.mdx` contains 22 em dashes written as
`word — word` (with surrounding spaces), which violates the
`LangChain.DashesSpaces` Vale rule enforced by `make lint_prose` (CI).
Per AGENTS.md: "Add spaces around em dashes — write word—word not
word — word (make lint_prose enforces this)."
Fix: replace all 22 instances of ` — ` with `—` in prose lines
(the 2 instances inside code block comments are untouched).
1 file changed, 23 lines. Pipeline build clean. Fix ready.
## Summary
Automated update of package download statistics from pepy.tech and npm
## Details
- Updates download counts in `packages.yml`
- Regenerates provider overview page at
`src/oss/python/integrations/providers/overview.mdx`
- Regenerates integration download tables under `src/snippets/oss/`
- Generated by GitHub Actions workflow `update-package-downloads.yml`
- Scheduled to run every Sunday at 11:59 PM UTC
🤖 This PR was created automatically by GitHub Actions
Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
Co-authored-by: Lauren Hirata Singh <lauren@langchain.dev>
## Why
Ten self-hosted releases published with only the `Internal improvements
and maintenance updates` placeholder even though they shipped real
customer-facing changes. This restores 33 notes.
**Root cause:** the deployed `helm-changelog-bot` runs code from before
2026-06-25, so it only scrapes the legacy `## Self-Hosted Release Note`
PR-body section. Three features merged that day were never deployed (the
repo has no CI, deploys are manual):
- `f3cd4f3` read `.changelog/*.yaml` fragments
- `2537c64` PR-title fallback for fragment-less PRs
- `2bbda07` honor the `skip-changelog` label
As `langchainplus` migrated to fragments, every fragment-sourced note
was silently dropped. Evidence: langsmith-0.16.1 published the polished
*legacy* Release Note from langchainplus#33020, not that PR's fragment
body.
## What changed
Notes re-derived from the fragments and PR titles, following the
resolution order in the bot's current `main`.
| Release | Notes restored |
|---|---|
| 0.16.7 | 1 |
| 0.16.2 | 1 |
| 0.16.0-rc.29 | 5 |
| 0.16.0-rc.28 | 4 |
| 0.16.0-rc.27 | 2 |
| 0.16.0-rc.24 | 6 |
| 0.16.0-rc.23 | 2 |
| 0.16.0-rc.22 | 1 |
| 0.16.0-rc.16 | 10 |
| 0.17.0-rc.1 | 1 |
The fix propagates through the image-dedup links: 0.16.3 and 0.16.4
point at 0.16.2, and 0.17.0-rc.2 through rc.6 point at 0.17.0-rc.1.
## Please review carefully
**Wording.** These were condensed from fragment bodies by hand, not by
the bot's LLM polish step. Past tense per the changelog's established
voice.
**Deliberate exclusions:**
- Two `status: held` fragments still gated behind Eppo flags
(`forge_issue_board_enabled` on 0.16.0-rc.29, `threads_aq` on
0.17.0-rc.1). Worth noting the bot does not check `status` at all, so
once redeployed it would publish gated features early.
- Notes referencing SmithDB, which was not available for self-hosted at
those versions. Matches `SELF_HOSTED_EXCLUDED_TERMS` and the precedent
in #4476.
- Raw internal PR titles with no customer meaning (CI pinning, token
minting, service co-hosting, internal flag gating).
**Untouched and correct:** 0.16.5, 0.16.0-rc.25, rc.20, rc.18, 0.15.17,
and 0.15.16 shipped only chore bumps or opted-out PRs, so their
placeholders are accurate.
## Follow-up outside this PR
1. Redeploy the bot from `main`, and add deploy automation so merges
cannot silently fail to ship again.
2. Teach `get_pr_release_notes` to skip fragments where `status !=
"ready"`.
3. Backport PRs into `v16-stable` carry `self_hosted: false` fragments
authored for Cloud (langchainplus#33187, #33719, and six rc.16 PRs), so
genuinely self-hosted changes are marked Cloud-only.
4. Security fixes are being labeled `skip-changelog`
(langchainplus#33480, vulnerable Python dependency bumps). Self-hosted
operators generally want those.
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Fixes DOC-1540
## Summary
- Remove the word "normal" from the opening sentence on both the MDA
middleware and MDA tools pages
- `managed-deep-agents-middleware.mdx`: "the normal Deep Agents
`middleware` configuration surface" → "the Deep Agents `middleware`
configuration surface"
- `managed-deep-agents-tools.mdx`: "the normal Deep Agents `tools`
configuration surface" → "the Deep Agents `tools` configuration surface"
This was flagged by Eli Verdun as informal — "normal" implies an awkward
hierarchy. Eli suggested just saying "Deep Agents" directly.
## Links
- Linear:
https://linear.app/langchain/issue/DOC-1540/replace-normal-deep-agents-with-clearer-terminology-in-mda-middleware
- Slack:
https://langchain.slack.com/archives/C09G1T60QV9/p1786826676152809
## Verification
Not run; docs-only copy change (two single-word removals).
## Reviewers
Requested review from: @fjmorris, @katmayb
Co-authored-by: Docs Bot <docs-bot@langchain.dev>
Week covered: August 10-17, 2026
Source fragments:
- .changelog/2026-08-11-* (21 ready, 5 held)
- .changelog/2026-08-12-* (10 ready, 5 held)
- .changelog/2026-08-13-* (14 ready, 4 held)
- .changelog/2026-08-14-* (4 ready, 0 held)
Held or skipped:
- 14 held fragments stayed out of the published changelog because they
are still gated / not fully rolled out.
- 0 invalid fragments in this week’s range.
Agent involvement: drafted and published by an AI agent.
Co-authored-by: Lauren <lauren@langchain.dev>
Fixes DOC-1538
## Summary
- Follow AGENTS.md style guide: "Managed Deep Agents" (product name,
always capitalized) vs. "a managed deep agent" (common noun — an
instance the user creates, lowercase)
- Fix Tab title from title case `"Model & Configuration"` → sentence
case `"Model & configuration"` in `managed-deep-agents-overview.mdx`
(`#example-agent` section)
- Fix 5 other inline prose occurrences across MDA docs pages where the
singular instance was incorrectly capitalized as a proper noun
**Files changed:**
- `src/langsmith/managed-deep-agents-overview.mdx` — Tab title sentence
case
- `src/langsmith/managed-deep-agents-memory.mdx` — "a Managed Deep
Agent's" → "a managed deep agent's"
- `src/langsmith/managed-deep-agents-mcp-connectors.mdx` — "to a Managed
Deep Agent" → "to a managed deep agent"
- `src/langsmith/managed-deep-agents-channels.mdx` — "a Managed Deep
Agent to" → "a managed deep agent to"
- `src/langsmith/managed-deep-agents-channels-slack.mdx` — 2 instances
of "Managed Deep Agent" → "managed deep agent"
- `src/langsmith/managed-deep-agents-sandboxes.mdx` — "a Managed Deep
Agent" → "a managed deep agent"
## Links
- Linear:
https://linear.app/langchain/issue/DOC-1538/fix-sentence-case-for-managed-deep-agent-and-product-name
- Slack:
https://langchain.slack.com/archives/C09G1T60QV9/p1786826257729819
## Verification
- `make check-cross-refs` — ✅ All cross-references resolved
- `make lint_prose` — No errors in changed files (60 pre-existing errors
in other unrelated files)
## Reviewers
Requested review from: @lnhsingh, @fjmorris
---------
Co-authored-by: Docs Bot <docs-bot@langchain.dev>
## Description
The mirroring guide told users to use mutable `latest` tags, which can
lead to mixed service versions during releases. It now directs users to
the Helm chart `appVersion` and uses a concrete version in Docker
examples.
## Test Plan
- [x] Run Vale on the changed page
- [x] Verify the example image tag exists on Docker Hub
Made by [Open
SWE](https://openswe.vercel.app/agents/72c6367c-4a4b-9450-bc47-ab5f5754a7c2)
---------
Co-authored-by: open-swe[bot] <open-swe@users.noreply.github.com>
## Overview
Update Gemini docs to use 3.7 Flash in examples.
## Type of change
**Type:** Update existing documentation
## Related issues/PRs
- Slack thread:
## Checklist
- [x] I have read the [contributing guidelines](README.md), including
the [language
policy](https://docs.langchain.com/oss/python/contributing/overview#language-policy)
- [x] I have tested my changes locally using `docs dev`
- [x] All code examples have been tested and work correctly
- [x] I have used **root relative** paths for internal links
- [x] I have updated navigation in `src/docs.json` if needed
(Internal team members only / optional): Create a preview deployment as
necessary using the [Create Preview Branch
workflow](https://github.com/langchain-ai/docs/actions/workflows/create-preview-branch.yml)
## Additional notes
<!-- Any other information that would be helpful for reviewers -->
## Summary
Removes the hardcoded "every 6 hours" scan-cadence claim from the
LangSmith Engine docs and describes recurring scans as running on a
dynamic schedule tuned to balance cost and performance instead.
- `src/langsmith/engine.mdx`: updated the LCU cost table's "Recurring
scans" trigger and the accompanying prose.
- `src/langsmith/engine-overview.mdx`: updated the "How Engine runs"
section.
## Why this approach?
The scan interval is an internal implementation detail that can change
over time to optimize cost and performance. Documenting a fixed 6-hour
interval creates a stale, overly specific commitment; describing the
cadence as dynamic keeps the docs accurate without needing a follow-up
edit whenever the interval changes.
## Test Plan
- [x] `make lint_prose FILES="src/langsmith/engine.mdx
src/langsmith/engine-overview.mdx"` — 0 errors, 0 warnings, 0
suggestions
- [x] Verified no other `.mdx` file in the repo references Engine's scan
interval as a fixed hour count
## Release Note
Updated the Engine docs to describe scan cadence as dynamic (tuned for
cost/performance) rather than a fixed 6-hour interval.
Fixes DOC-1333
## Summary
- Adds a new `### Add process-level resource attributes` section to the
OTel tracing docs (`src/langsmith/trace-with-opentelemetry.mdx`), under
the existing "Use environment variables for global configuration"
subsection.
- Explains how to use the standard `OTEL_RESOURCE_ATTRIBUTES` env var to
attach custom metadata (deployment environment, service version, team,
region, etc.) to all traces emitted by a process, without modifying
application code.
- Also adds `OTEL_RESOURCE_ATTRIBUTES` to the existing env var listing
code block.
## Links
- Linear:
https://linear.app/langchain/issue/DOC-1333/add-otel-resource-attributes-paragraph-to-otel-tracing-docs
- Slack:
https://langchain.slack.com/archives/C09G1T60QV9/p1783186731049369
## Verification
Cross-references checked: `make check-cross-refs` ✅. Prose linting
(Vale) not available in sandbox — docs-only copy change.
## Reviewers
Requested review from: @katmayb, @fjmorris
---------
Co-authored-by: Docs Writer Bot <brace@langchain.dev>
Co-authored-by: Kathryn May <44557882+katmayb@users.noreply.github.com>
Fixes DOC-1430
## Summary
- Expands the `return_direct` docs on parallel tool calls.
`create_agent` routes to `END` only when **every** client-side tool call
in the step has `return_direct=True`; all tools in the batch execute
first, and the final response carries every `ToolMessage`.
- Adds a `<Warning>` for mixed parallel calls: a `return_direct=True`
tool called alongside a normal tool does **not** exit the loop. The
agent routes back to the model with all results.
- Adds a Python-only "Return a Command with return_direct" subsection
covering `Command` returns from a `return_direct` tool, the
matching-`ToolMessage` requirement, and the `graph=Command.PARENT`
escape hatch.
- Corrects the pre-existing "Return a Command" section, which said a
`Command` could be returned "with or without including a `ToolMessage`".
A matching `ToolMessage` is required when the `Command` targets the
current graph.
- Scopes Python-only claims by language. `ToolNode` validation and the
`ValueError` exist only in Python, and the tool call ID accessor differs
between languages, so both now sit in `:::python` / `:::js` fences.
## Correction to an earlier revision of this description
An earlier version of this description claimed the agent exits when
**any** tool in a parallel batch has `return_direct=True`, citing
`chat_agent_executor.py`. That is the behavior of the legacy
`langgraph.prebuilt.create_react_agent`, not the
`langchain.agents.create_agent` this page documents. The two
implementations genuinely differ. The page's `all` wording is correct
and was never changed to `any`.
## Verification
Verified against `langchain-ai/langchain` `master` and
`langchain-ai/langgraph` `main` as of 2026-08-14.
**Parallel `return_direct` (`all`, not `any`):**
`libs/langchain_v1/langchain/agents/factory.py`,
`_make_tools_to_model_edge` → `tools_to_model`. Exit condition is
`client_side_tool_calls and
all(tool_node.tools_by_name[c["name"]].return_direct for c in
client_side_tool_calls)`. A mixed batch falls through to the default
case and routes back to the model.
For contrast, `langgraph`
`libs/prebuilt/langgraph/prebuilt/chat_agent_executor.py`
`route_tool_responses` returns `END` as soon as one trailing
`ToolMessage` matches `should_return_direct`, with an `any(...)`
fallback for tools executed in a separate `Send`. That is
`create_react_agent`, a different entry point.
**`ToolMessage` requirement:** `langgraph`
`libs/prebuilt/langgraph/prebuilt/tool_node.py`,
`_validate_tool_command`. The `ValueError` is guarded by
`require_terminator and updated_command.graph is None and not
has_matching_tool_message`, which confirms both the requirement for the
current graph and that `graph=Command.PARENT` lifts it. Matching is on
`message.tool_call_id == call["id"]`.
**JavaScript:** `langgraphjs`
`libs/langgraph-core/src/prebuilt/tool_node.ts` has no equivalent of
`_validate_tool_command` and never raises on a missing `ToolMessage`, so
the `ValueError` claim is Python-only. `runtime.toolCallId` is confirmed
in `langchainjs` `libs/langchain/src/agents/tests/tools.test.ts`.
**Linting and build:** `make lint_prose` → 0 errors, 0 warnings. `make
build` → clean; the generated JS page keeps the shared requirement and
drops both Python-only blocks. `make check-cross-refs` → all
cross-references resolved.
## Links
- Linear:
https://linear.app/langchain/issue/DOC-1430/document-return-direct-behavior-gaps-on-oss-tools
- Slack:
https://langchain.slack.com/archives/C09G1T60QV9/p1784904894989719
## AI involvement
Drafted by an AI agent and revised by a second agent session, which
verified every behavioral claim against the langchain, langgraph,
langchainjs, and langgraphjs sources. Human review still needed.
## Reviewers
Requested review from: @npentrel, @lnhsingh
---------
Co-authored-by: Docs Bot <brace@langchain.dev>
Co-authored-by: Naomi Pentrel <5212232+npentrel@users.noreply.github.com>
Co-authored-by: Lauren Hirata Singh <lauren@langchain.dev>
Co-authored-by: Claude Opus 5 (1M context) <noreply@anthropic.com>
Fixes DOC-1527
## Summary
- Removes the "Supported in Python only" label from the configurable
base URLs / API keys accordion in the LLM Gateway quickstart
- Splits the supported chat models list into Python and TypeScript
sections
- Adds TypeScript providers: `@langchain/anthropic >= 1.5.4`,
`@langchain/fireworks >= 0.2.7`, `@langchain/openai >= 1.5.7`
- Notes the TypeScript env var (`OPENAI_BASE_URL`) alongside the Python
one (`OPENAI_API_BASE`) in the override example
- Updates the resolution table description to mention both `*_API_BASE`
(Python) and `*_BASE_URL` (TypeScript) patterns
## Links
- Linear:
https://linear.app/langchain/issue/DOC-1527/update-llm-gateway-quickstart-configurable-base-urls-and-api-keys-now
- Slack:
https://langchain.slack.com/archives/C09G1T60QV9/p1786578739338799
## Verification
Verified JS gateway support directly in `langchain-ai/langchainjs`
source:
- `@langchain/core/src/utils/gateway.ts` —
`resolveLangSmithGatewayConfig` handles `LANGSMITH_GATEWAY` /
`LANGSMITH_GATEWAY_API_KEY`
- `@langchain/openai`, `@langchain/anthropic`, `@langchain/fireworks`
all call `resolveLangSmithGatewayConfig` and respect provider-specific
base URL env vars as overrides
- Google Gemini and Baseten are not yet supported in JS (not included)
## Reviewers
Requested review from: @katmayb, @fjmorris
---------
Co-authored-by: Docs Writer <brace@langchain.dev>
Co-authored-by: Lauren Hirata Singh <lauren@langchain.dev>
Co-authored-by: Claude Opus 5 (1M context) <noreply@anthropic.com>
Fixes DOC-1529
## Summary
- Renamed the section heading `## Additional images for Fleet and
Insights` → `## Additional images for Fleet` on the self-host mirroring
images page
- Updated the opening sentence of that section to remove the reference
to "Insights", since Insights is now part of `langsmith-insights-engine`
and is already documented in the "Additional images for Engine" section
immediately above
## Links
- Linear: https://linear.app/langchain/issue/DOC-1529
- Slack:
https://langchain.slack.com/archives/C09G1T60QV9/p1786595268005789
## Verification
No new prose lint errors introduced. No pages moved or deleted.
## Reviewers
Requested review from: @katmayb, @fjmorris
---------
Co-authored-by: Docs Bot <brace@langchain.dev>
Co-authored-by: Lauren Hirata Singh <lauren@langchain.dev>
The sandbox auth proxy page never mentioned a proxy rule's `env_vars`,
and its GitHub example told readers to prefix every command with
`GH_TOKEN=dummy` — which is exactly what the field removes.
- Adds `env_vars` to the rule field table and a section covering what it
is for, the plaintext warning, and the precedence order (enabled rules <
the sandbox's own `env_vars` < variables managed by an enabled AWS or
GCP auth rule).
- Updates the GitHub example so the rule sets `GH_TOKEN`, and the `gh`
commands run unprefixed.
## Test Plan
- [x] `make lint_prose FILES=src/langsmith/sandbox-auth-proxy.mdx` — 0
errors, 0 warnings, 0 suggestions
Co-authored-by: open-swe[bot] <open-swe@users.noreply.github.com>
Context Hub repos can be mounted into sandboxes, but that was documented
nowhere — the sandbox SDK page covers files, service URLs, tunnels, and
retention, and never mentions mounts.
Adds a **Mount a Context Hub repo** section to `sandbox-sdk.mdx` with
Python and TypeScript examples, the mount-path rules, and the two sync
options (`initial_pull_only`, `read_only`). Links to it from the Context
Hub page's next steps.
⚠️ The `context_hub_mount` / `contextHubMount` helpers used in the
examples come from langchain-ai/langsmith-sdk#3351 — merge this after
the langsmith release that ships them.
---------
Co-authored-by: open-swe[bot] <open-swe@users.noreply.github.com>
## Why
An agent-readiness audit of docs.langchain.com flagged failures in page
size, llms.txt coverage, and llms-full.txt size. Investigating those
turned up three problems that also affect human readers, and two
reported failures that turned out not to be real.
## What changed
### 1. Extracted 7.9 MB of base64 images out of the markdown
Eight integration pages embedded images as base64 data URIs directly in
their markdown. `google_imagen.mdx` was 6,685,937 characters, of which
6,680,932 were four PNG blobs; two of the four were byte-identical. It
served as a **6.69 MB response**.
That bloat dominated the agent-facing corpus: `llms-full.txt` is 15.1 MB
and this base64 was roughly half of it.
Nine rendered images now live under `src/images/integrations/`, deduped
and recompressed where the source was a photo. **Diagrams and charts
stay byte-identical PNGs** so their text stays crisp. Two blobs sat
inside ```` ```html ```` fences as literal `plt_img_base64()` output
rather than rendered images; those are truncated in place so the example
still shows the shape of a data URI without 52 KB of payload.
Markdown removed: 7,881,055 chars. Images added: 1.08 MB. Build output
drops 30.1 MB → 22.8 MB.
### 2. Custom llms.txt so the index is not truncated
The generated `llms.txt` was capped at 100,000 characters and said so in
its own last line:
> `_Note: this index was truncated to stay under 100,000 characters; 569
pages and 3 OpenAPI specs omitted._`
Coverage was 970 of 1,536 sitemap pages (63%). **This was not a
navigation problem** — 166 of the omitted pages are already in
`docs.json`, including most self-hosted and admin documentation. They
were simply past the cutoff.
Mintlify's docs state that a custom `llms.txt` at the project root
overrides the generated file and is uncapped, so the build now emits
one. **2,038 pages indexed, up from 970.**
OpenAPI endpoint pages never exist as MDX (Mintlify renders them at
deploy time), so they are derived from the specs referenced in
`docs.json`. Deriving them correctly took three passes — see the review
note below.
### 3. Split the SmithDB SDK migration guide by API area
At **514,135 characters served** this was the largest page on the site
by a factor of three. It reads as 9 KB of source because the bulk
arrives through 292 nested snippet imports, so neither file-size checks
nor the audit's page sample ever flagged it.
The guide keeps its URL as an overview (context, deprecation dates,
minimum SDK versions, exceptions, discontinued methods) plus a card
group linking to six per-area pages. Worst page: **514 K → ~150 K**.
Runs are split across two pages rather than one: `runs-query` alone
expands to 110 K, so grouping it with retrieve and get-URL would have
left a ~251 K page and largely defeated the split.
## Areas needing careful review
- **The embedded agent prompt.** The guide told coding agents to fetch
the single `.md` as the source of truth. The split would have silently
broken that, so the prompt now lists the per-area URLs. Worth a read to
confirm it still reads correctly to an agent.
- **Anchor links.** Three snippets deep-linked to `#runs-query` and
`#traces-query` and described them as appearing "above". Those now point
at the area pages. **`make broken-links` does not catch this** — it
validates paths, not anchors. `#exceptions` and `#about-self-hosted`
still resolve, since both sections stay on the overview.
- **Card descriptions and area prose** on the six new pages are newly
written. Each factual claim was checked against the snippets
(`list_runs`→`runs.query`, `read_run`→`runs.retrieve`, `get_run_url`).
## Found in self-review
A self-audit pass caught defects in my own earlier commits, fixed in
4cfe5f5:
- **47 fabricated API URLs in llms.txt.** The slug rule was wrong twice:
underscores were collapsed to hyphens (the spec carries both
`annotation-queues` and `annotation_queues` as distinct tags rendering
to different directories), and `x-hidden` operations were emitted
despite Mintlify rendering no page for them. Plus apostrophes became
separators, and duplicate summaries were dropped rather than given
Mintlify's numeric suffix. Derived URLs now match the production sitemap
exactly: **599 derived, 599 present, 0 fabricated.**
- **An upscaled image.** `sips -Z` enlarges images smaller than the
target, so a 602×800 photo became 770×1024 — inventing pixels.
Regenerated at native size, and smaller on disk.
Three regression tests cover the tag-slug rule, apostrophe handling, and
hidden/duplicate operations.
## Two reported failures that are not real
- **Markdown URL support (reported 87%)**: not reproducible. 120 random
sitemap URLs all return 200 for `.md`; 60/60 for HTML.
`/oss/langchain/models` 404s for both HTML and `.md` because that URL
does not exist — the canonical is `/oss/python/langchain/models`. No
change made.
- **Content parity (reported 2 of 14 pages)**: not a defect. Regular
pages differ by 0.7–3.9%, all UI chrome. The only >10% gaps are OpenAPI
pages, where the **markdown is richer than the HTML** (175 words vs 55)
— the html-only tokens are API-playground widgets. No change made.
## Not included
Changelog splitting is deliberately out of scope. Measured growth
(self-hosted ~22 KB/month) means no humane time boundary holds 100 KB,
and changelogs are the page type where truncation degrades gracefully
since they are reverse-chronological.
## Validation
- `make build` clean
- `make lint` and `make lint_prose` clean on all touched files
- `make broken-links`: no broken links
- 206 tests pass (3 new)
- 45 random derived API URLs re-checked against production: all 200
- llms.txt: 0 malformed entries, 0 empty titles, 0 duplicate URLs across
2,038 lines
## AI disclosure
Authored with Claude Code (Claude Opus 5). All findings were verified
against the live site, the OpenAPI specs, and production sitemap rather
than asserted; the self-review section above documents defects it caught
in its own earlier work.
---------
Co-authored-by: Claude Opus 5 (1M context) <noreply@anthropic.com>
Caspar Broekhuizen