LangChain launched LangSmith Fleet with two agent types: user-credentialed Assistants and fixed-credential Claws, solving the agent auth identity problem.
LangChain launched LangSmith Fleet, introducing two distinct agent authorization models: Assistants (which operate on-behalf-of individual users using their own credentials) and Claws (which use a fixed, dedicated set of credentials regardless of who is interacting). The platform also added channel integrations — Slack, Gmail, Outlook, and Teams — with different channel support for each agent type. The launch addresses a real-world identity problem: when multiple users interact with a shared agent, whose credentials does it use? Future roadmap includes user-specific memory permissions to prevent cross-user data leakage.
This formalizes the agent credential problem that's been a source of serious security bugs — agents leaking one user's data into another's session. LangSmith Fleet's Assistant vs. Claw split maps cleanly to two architectural patterns you're likely already hacking around: per-user OAuth token injection at runtime vs. a service account model. The channel integrations (Slack, Gmail, Teams) mean you can skip building your own webhook routing and credential vaulting for multi-user agents.
If you're building a multi-user agent today without per-user credential isolation, spin up a LangSmith Fleet Assistant this week and test whether the runtime credential injection actually prevents cross-user data access — verify it before shipping to prod.
Open smith.langchain.com and navigate to the Fleet section
Tags
Also today
Signals by role
Also today
Tools mentioned