Repository navigation
docs(langsmith): call tunnels from Agent Servers - #7672
Merged
raghavverma-langchain merged 7 commits intoNov 13, 2026
Merged
Conversation
Deployed agents can call a tunnel URL with the deployment's own LANGSMITH_API_KEY in X-Api-Key. Document that, the X-Tunnel-Origin- headers for services that use their own X-Api-Key or Cookie, and that access is org-wide.
raghavverma-langchain
requested a review
from Sean Angiolillo (seanangio)
as a code owner
November 12, 2026 15:14
…ithub.com/langchain-ai/docs into raghavverma/tunnels-from-deployments-docs
Sean Angiolillo (seanangio)
requested review from
Florence Morris (fjmorris) and
Lauren Hirata Singh (lnhsingh)
as code owners
November 13, 2026 14:23
Sean Angiolillo (seanangio)
approved these changes
Nov 13, 2026
Sean Angiolillo (seanangio)
left a comment
Contributor
There was a problem hiding this comment.
raghavverma-langchain added a commit with some small edits. A few questions that may (or may not) warrant your attention:
- AWS prod test (11x): Has calling a tunnel from an Agent Server been tested on AWS prod yet? The dev test only covered the GCP dev edge, and the page says tunnels work in every region. Should we hold the merge until it passes, or publish now since the edge code is shared?
- Orgs with an IP allowlist: The dev test notes say this is untested, and the edge's auth check might see the edge's IP instead of the Agent Server's. Did AutoGrab confirm whether they use an allowlist? If it's still unknown, should the page add a caveat?
- Personal organizations: The test notes say the UI blocks personal orgs from creating tunnels. That's not on the page today. Should we add a line, for example "Tunnels are not available to personal organizations"?
Feel free to merge when ready.
Sean Angiolillo (seanangio)
removed request for
Florence Morris (fjmorris) and
Lauren Hirata Singh (lnhsingh)
November 13, 2026 14:25
Contributor
Author
|
Sean Angiolillo (@seanangio) thanks for the edits!
|
Contributor
|
Mintlify preview branch generated: Site preview: https://langchain-5e9cc07a-preview-raghavverma-tunnels-from-4817979b.mintlify.site Important Preview links may take a few minutes to start working while the deployment finishes. Changed documentation pages (preview deep links): |
raghavverma-langchain
deleted the
raghavverma/tunnels-from-deployments-docs
branch
November 13, 2026 15:46
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.
Summary
agents running on agent servers in langsmith cloud can already call a tunnel url. they just send the agent server's own
LANGSMITH_API_KEYasX-Api-Key, which every agent server already has. the tunnels page didn't list agent servers as a consumer, so this adds them and explains the headers. it uses the new agent server name from #7616.X-Tunnel-Origin-X-Api-Key/X-Tunnel-Origin-Cookiefor services that use their own key or cookiePart of LSD-2176
Test Plan
LANGSMITH_API_KEYand got the service's response (200). without the key it got403 connection access denied, and with the tunnel disabled403 connection is disabled.X-Tunnel-Origin-X-Api-Keyarrived at the service asX-Api-Key, and LangSmith's own key was strippedsrc/langsmith/tunnels.mdx: 0 errors, 0 warnings, 0 suggestions/langsmith/deploy-to-cloud,/langsmith/control-plane#langsmith-integrationdocs devand the broken-links check. relying on the preview and CIPrepared with Claude Code.
Demo