Repository navigation
docs: rename deployment-named LangSmith pages and split Deploy agents from Agent Server - #7687
Merged
Merged
Conversation
Sean Angiolillo (seanangio)
requested review from
hari-dhanushkodi and
Victor Moreira (victorm-lc)
and removed request for
Florence Morris (fjmorris),
Lauren Hirata Singh (lnhsingh) and
Naomi Pentrel (npentrel)
November 12, 2026 21:53
Co-authored-by: robin-agent[bot] <215916821+robin-agent[bot]@users.noreply.github.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Contributor
|
Mintlify preview branch generated: Site preview: https://langchain-5e9cc07a-preview-seanangio-doc-1922-06ba9047.mintlify.site Important Preview links may take a few minutes to start working while the deployment finishes. Changed documentation pages (preview deep links):
Only the top 5 changed markdown files by diff size are listed. |
Victor Moreira (victorm-lc)
approved these changes
Nov 16, 2026
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.
Why
Follow-up to #7616, which renamed LangSmith Deployment to LangSmith Agent Server across the docs but deliberately kept every file name and URL slug. That left links that read
[Agent Server](/langsmith/deployment), and the product team asked for/deploymentto change (DOC-1922).Renaming the files turned up a bigger problem than stale slugs. The obvious new home for
deployment.mdx,agent-server.mdx, already existed. Withagent-server-overview.mdx, the docs had three pages titled some form of "Agent Server", all with the sidebar title "Overview":deployment.mdxagent-server-overview.mdxagent-server.mdxAfter the rename, a reader could no longer tell from titles alone where to go to deploy an agent and where to go to learn the Agent Server runtime. Moving files would have hidden this problem without fixing it.
The main change: separate the task from the product
This PR gives each question its own landing page:
/langsmith/deploy-overview, "Deploy agents" (formerly/langsmith/deployment). This page answers the task question: I have an agent, so where and how do I run it in production? It covers choosing a framework, choosing a hosting environment (Cloud, hybrid, self-hosted, standalone), pricing, and what to do after deploying. It stays the first page of the Deploy > Get started tab./langsmith/agent-server, "LangSmith Agent Server". This page answers the product question: what is the runtime, and how does it work?agent-server-overview.mdxis merged into it, and it becomes the landing page of the Agent Server tab. It covers assistants, threads, runs, persistence, the task queue, runtime architecture, auth, customization, and tutorials.Each page links to the other near the top, so a reader who lands on the wrong one gets redirected in one click.
Why
deploy-overviewand not anagent-server-*slugThis is the change most likely to draw debate, so here is the reasoning:
agent-serverto mean one thing. If the deploy page took anagent-server-*slug, the docs would still have two overlapping Agent Server landing pages, which is the problem this PR is trying to fix. Now the product name points at the product page.deploy-to-cloud,deploy-with-control-plane,deploy-standalone-server) already use verb-led slugs.deploy-overviewfits with them.The tradeoff is that "LangSmith Agent Server" no longer appears in the deploy page's title. The page still opens by naming and linking Agent Server as the runtime that agents deploy to, and the description keeps the product name for search.
Other changes
docs mv, which rewrote every inbound link and nav entry, and a redirect added for each old URL:deployment→deploy-overviewdeployment-revisions→agent-server-revisions(title now "Agent Server revisions")manage-deployment→manage-agent-servermonitor-deployment→monitor-agent-serverenable-self-hosted-deployment→enable-self-hosted-agent-serveragent-server-overviewmerged intoagent-server, with a redirect. The merged page adds what the old overview had and the runtime page lacked: streaming, human-in-the-loop, double-texting, webhooks, MCP/A2A, dependency setup, auth and customization cards, and tutorials. It also adds new, explicit coverage of who provisions PostgreSQL and Redis on Cloud, self-hosted, and standalone setups.deployment-quickstart-dadeleted. It was anoindexurl:stub that was not in the nav and had no inbound links. A redirect to the Managed Deep Agents quickstart replaces it./langgraph-platform/index,/langsmith/deployments,/langsmith/develop-agents-overview, and/langsmith/deploy-self-hosted-full-platformnow point to the new slugs. Two redirects that pointed at/langsmith/deployment#agent-servernow go to/langsmith/agent-server.Intentionally left alone
deployment-quickstart: its title is "Deploy your app to cloud", so "deployment" describes the task, not the product.smith-deployments-sdk: aurl:stub pointing atreference.langchain.com/.../deployment/sdk/. That URL lives outside this repo, so changing it is out of scope.{#langsmith-deployment-…}heading IDs (billing, usage, Terraform, and similar pages): they protect external#fragmentlinks and cost nothing to keep. The one on the old deploy page's environments heading was dropped, because the heading changed and nothing in the repo links to it.Review notes
deploy-overview/ "Deploy agents" naming above in particular./langsmith/deploymentand/langsmith/deployment-revisions. The new redirects cover both, but the product team should update them to the new slugs. [I could probably also point Robin at this...]Linear: DOC-1922