Skip to content

docs(langsmith): call tunnels from Agent Servers - #7672

Merged
raghavverma-langchain merged 7 commits into
mainfrom
raghavverma/tunnels-from-deployments-docs
Nov 13, 2026
Merged

raghavverma-langchain merged 7 commits into
mainfrom
raghavverma/tunnels-from-deployments-docs

Conversation

@raghavverma-langchain

@raghavverma-langchain raghavverma-langchain commented Nov 12, 2026 •

Copy link
Copy Markdown
Contributor

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_KEY as X-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.

  • adds agent servers to the list of places you can use a tunnel url
  • new "call a tunnel from an agent server" section with a python example
  • covers X-Tunnel-Origin-X-Api-Key / X-Tunnel-Origin-Cookie for services that use their own key or cookie
  • notes that any agent server in the org can call any tunnel in it

Part of LSD-2176

Test Plan

  • tested end to end on dev: a deployed agent called a tunnel url with its LANGSMITH_API_KEY and got the service's response (200). without the key it got 403 connection access denied, and with the tunnel disabled 403 connection is disabled. X-Tunnel-Origin-X-Api-Key arrived at the service as X-Api-Key, and LangSmith's own key was stripped
  • the code example matches the code that ran in that test
  • vale on src/langsmith/tunnels.mdx: 0 errors, 0 warnings, 0 suggestions
  • link targets exist: /langsmith/deploy-to-cloud, /langsmith/control-plane#langsmith-integration
  • not run locally: docs dev and the broken-links check. relying on the preview and CI

Prepared with Claude Code.

Demo

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.

@robin-agent robin-agent Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Robin Review found 2 potential issues.

Open in Web • View Robin trace

Comment thread src/langsmith/tunnels.mdx Resolved
Comment thread src/langsmith/tunnels.mdx Resolved
@raghavverma-langchain raghavverma-langchain changed the title docs(langsmith): call tunnels from Cloud deployments docs(langsmith): call tunnels from Agent Servers Nov 12, 2026

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

raghavverma-langchain added a commit with some small edits. A few questions that may (or may not) warrant your attention:

  1. 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?
  2. 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?
  3. 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.

@raghavverma-langchain

Copy link
Copy Markdown
Contributor Author

Sean Angiolillo (@seanangio) thanks for the edits!

  1. aws: checked on aws prod that an agent server reaches the aws tunnel edge, and the success path is the same edge code that passed on dev, so publishing now.
  2. ip allowlist: still untested for orgs that use one, but i'd rather not put an unverified caveat on the page.
  3. personal orgs: good call, added it to the availability line in a705a18.

@github-actions

Copy link
Copy Markdown
Contributor

Mintlify preview branch generated: preview-raghavverma-tunnels-from-4817979b

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
raghavverma-langchain merged commit 921e011 into main Nov 13, 2026
31 checks passed
@raghavverma-langchain
raghavverma-langchain deleted the raghavverma/tunnels-from-deployments-docs branch November 13, 2026 15:46
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

internal langsmith For docs changes to LangSmith

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants