LangSmith Managed Deep Agents Introduces Caller-Specific Identity Management with Connections Feature

The Connections feature was introduced in LangSmith Managed Deep Agents v0.7.0+, overcoming the limitations of API keys hardcoded in existing .env files. While the previous approach recorded all actions under a service account, making it impossible to identify 'who' made the request, Connections provides unique identities per caller by referencing named credentials stored in the LangSmith workspace at runtime.

Separation of Ownership and Credential Type

Connections is composed of two independent axes: Ownership (Agent vs User) and Credential Type (Static Secret vs OAuth Grant). Agent-owned credentials are tied to the deployment and shared by all callers, while User-owned credentials are resolved per caller at runtime. Agent-owned secrets are used when user-specific permissions are identical, such as for web search or geocoders, and are not automatically collected during mda deploy, enhancing security.

OAuth Automation and User-Specific Permission Handling

User-owned OAuth connections allow for the automation of authentication for 23 services, including GitHub. When connections.get() is called, unauthenticated users trigger an OAuth flow, while authenticated users use cached tokens. Upon token expiration, execution is paused to request new permissions but does not fail. This ensures that tasks like create_issue are performed under the actual user account rather than a bot, and search results vary according to caller-specific permissions.

Development and Deployment Workflow

In development environments, Agent-owned connections are resolved via MDA_DEV_<SLUG> variables in .env, while User-owned connections resolve to the developer logged into mda dev as the actual principal. The OAuth catalog is embedded in the binary, automating endpoint configuration. When working across multiple services, a single interruption displays the list of unassigned connections, resuming after approval. Each connection is managed in three stages: creation, reference, and redeployment.