LangChain Adds Connections So Agents Can Use Each Caller’s Identity

A shared AI agent can now file a GitHub issue under the identity of the person who requested it, rather than a common bot account. LangChain has introduced Connections for Managed Deep Agents, a workspace-managed credential system for shared deployment access and per-caller credentials.

Available in Managed Deep Agents version 0.7.0 and later, Connections stores a named credential in a LangSmith workspace. Tools retrieve it at runtime through connections.get(), rather than embedding the credential in the application build.

The credential owner determines whose authority applies

Connections treats ownership and credential format as separate choices. A credential can belong to the agent or the user, and either can be a static secret or an OAuth grant. Agent-owned access is shared by every caller; user-owned access resolves for the individual making a request.

In LangChain’s GitHub example, an agent that creates an issue with a user-owned connection uses the requesting person’s identity. That also means two people can receive different search results from the same deployment when their repository access differs.

OAuth steps move into the managed runtime

For user-owned OAuth connections, Managed Deep Agents handles authorization, token retrieval, refresh-related flow and authorization interrupts. When a caller needs to grant access, the runtime can pause the run instead of requiring the project to build callback routes, token storage or consent screens.

The feature also supports MCP connections when a server supplies OAuth metadata and registers the client. LangChain uses Linear’s MCP server as an example of a route that avoids supplying a client ID, client secret or app registration.

Shared accounts remain available

Per-caller identity is optional. Agent-owned secrets can be rotated or revoked in the workspace without changing code or redeploying. Developers can also use a deployment-level OAuth grant so every caller acts as one shared account. The Connections catalog includes GitHub and 22 other services, alongside support for custom OAuth provider metadata.

Managed Deep Agents entered public beta in August with identity positioned as a way to establish trusted user context and access boundaries. Connections adds a credential layer to that earlier identity model.