managed-deepagents 0.8 ships Managed Connections to fix agent OAuth auth
hwchase17 · x · 2026-09-25
managed-deepagents 0.8 released
@casparbr shipped managed-deepagents 0.8 and addressed why managed agent frameworks still matter when "code is free":
- Generating code is easy, but developers must decide how systems behave and apply those decisions consistently: whose credentials the agent uses, what it can share, what changes when new users join — auth, memory and channel integrations all need the same rules, hard to scale without an opinionated foundation
- Not every team should solve these from first principles; building on tested decisions has value
Managed Connections (0.7)
Agents must act as someone: a shared identity or the requester. Normally that means an OAuth app per service, token stores, refresh logic and consent flows. Now you declare identity in code with one argument:
- agent: uses the agent's own token
- user: uses the user's token, guiding them through consent if not connected
One argument replaces the whole OAuth dance. LangChain founder hwchase17 retweeted the announcement.
More from coding & agent
- Pigment Agents now reads and posts in Slack, inheriting user permissions — mattturck · 2026-11-12
- Map of the agent economy: 50+ startups across payments, spend control, identity, memory — venturetwins · 2026-11-12
- OpenCode launches Browse, an on-device browser agent with local logins — Saul_Loveman · 2026-11-12
- VentureTwins maps the B2A economy: dozens of agent infra and app companies in first series installment — venturetwins · 2026-11-12
- Google releases 76-page 'Agents Companion' whitepaper on agent engineering — mdancho84 · 2026-11-12
- Spinning up containers for 20-line agent tools is backwards: Safescript compiles provable, 50ms-deploy apps — uriwa · 2026-11-12