Agent Upstart

Cool things people are building with agents — and practical help getting the most out of them.

Playbooks · Teams

Devin adds budgets, self-serve SSO and a usage API

Written November 13, 2026

Budget hierarchies, self-serve OIDC/SAML, approval-required tokens and a daily session-consumption API: Devin's November admin batch.

The batch

Cognition's Devin release notes for this period read as an admin release: six controls for the people who pay for Devin, govern sign-in, and answer for its use. None of them changes how an engineer prompts the agent. All of them change how an organization contains it. Taken together, they cover spend, identity, tokens, sharing, sign-out and reporting.

Spend: budget hierarchies

The notes announce budgets: enterprises can organize user spend and organization spend in a budget hierarchy, and enterprise admins can grant granular permissions to manage a budget, including sub-budget limits. The structure is the feature — a top-level allocation that delegates downward, so a central admin sets the shape and budget owners manage their own limits inside it. The notes publish no default amounts; the numbers are each enterprise's own.

Identity: self-serve SSO

Enterprise admins can now set up single sign-on themselves. The notes describe the flow: verify ownership of the email domain with a DNS record, then create, name, edit and delete OIDC or SAML connections from Settings, under Authentication, without contacting support. A related entry adds that signing out of an enterprise SAML login can also end the session at the identity provider, when a sign-out URL is configured for the connection. SSO setup stops being a support ticket and becomes an admin task with a defined checklist.

Tokens, sharing and sign-out

Reporting: a daily consumption API

The notes add a daily session-consumption endpoint for enterprises: GET /v3/enterprise/consumption/daily/sessions, returning per-day session consumption. Paired with the budget hierarchy, it gives a finance or platform team a programmatic feed of what Devin used each day, per enterprise, instead of a dashboard someone has to remember to open. Budgets set the limits; this endpoint is how you reconcile what actually ran against them.

How the pieces fit together

Read as a set, the six items describe one posture: spend delegated downward through budgets, identity set up by the enterprise itself, tokens granted by approval rather than by default, sessions shared within bounds an admin chose, a single sign-out that actually ends access, and a daily feed that shows what was consumed. Each item is small on its own. Together they are the difference between Devin as a collection of individual subscriptions and Devin as a governed platform a security review can sign off — which is the audience these release notes are plainly written for.

What to do

Related playbooks

Sources

Back to: Teams playbooks hub · Also: Run Claude Managed Agents in your own cloud · SWE-2 Flash: Devin's cheaper model, closed weights · Claude Fable 5.2 arrives in Devin Desktop and CLI