Skip to main content
AI News

BusinessNews

How Temporal plans to keep AI-agent access decisions consistent

The authorization features remain in development. Reporting differs on how many Oso employees are joining Temporal, and no financial terms for the team move have been disclosed.

Business Desk · AI News

3 min read

Engineers diagram an agent's permissions across connected services, with a loop for a retry.

Temporal has brought Oso employees onto its team to speed development of authorization controls for AI agents: rules that determine who an agent can act for and what it is allowed to do. The company says the planned controls should carry those decisions across services and preserve them through retries or failures, but they are not available yet, GeekWire reported.

The move adds Oso’s authorization expertise to Temporal’s effort to secure agents that perform tasks across connected software. How many Oso employees are joining is disputed in the reporting, and no financial terms for their move to Temporal have been disclosed.

What controls is Temporal developing for AI agents?

Authorization determines which actions a person or software system may take. Temporal says its planned controls are intended to establish whose permissions an agent should use, then keep those decisions consistent as it calls different tools and services.

The problem, as Temporal describes it, is that permissions are often checked separately in the application code for each service. An agent moving between services could therefore face inconsistent access decisions. Temporal’s aim is to connect those checks, including when an agent’s work resumes after a crash or retry.

That plan is distinct from Temporal’s existing Durable Execution technology, which the company says preserves an application’s state and execution history through failures. Temporal also says its current products include visibility into agent activity and Nexus connectivity. The Oso announcement does not change what customers can use today; the authorization features remain in development, with no release date specified.

The distinction matters to businesses using agents to carry out work on a person’s behalf. If the planned controls work as intended, they are meant to help keep agent actions within that person’s permissions even when tasks cross services or resume after interruption. Temporal has described the goal, not demonstrated the forthcoming features in an independent evaluation.

Free newsletter

Get the morning briefing

Start each day with the AI stories that matter and why — a short, free email from our newsroom.

Free. One email a day, one-click unsubscribe. See our privacy policy.

Did Temporal acquire Oso?

No. Tiny, a separate company, acquired Oso Cloud’s assets. Tiny said the purchase closed Thursday, Oct. 1, for approximately $1.9 million. That price was for Oso Cloud’s assets; the available reporting does not establish it as payment to Temporal or as the value of hiring Oso employees.

Oso’s co-founder and CEO, Graham Neray, described most of Oso’s current team as joining Temporal. The Puget Sound Business Journal, citing a Temporal spokesperson, reported that 11 of Oso’s 40 employees were making the move. The accounts do not establish a settled headcount. Oso Cloud is to continue operating under Tiny, and the terms of the personnel move to Temporal have not been disclosed.

The split means Oso’s authorization product and its joining employees have different destinations: Tiny acquired the product assets, while Temporal is adding team members to work on its own agent-security plans. Tiny said it intends to keep investing in Oso Cloud.

How does the move fit Temporal’s growth?

Temporal announced a $550 million Series E financing at a $12.55 billion valuation on Sept. 14. The company also reported an annualized revenue run rate above $250 million, meaning it was projecting a year’s revenue from its current pace, and said the figure had grown more than 200% year over year. Those operating figures are company-reported and do not establish that the planned security controls work.

Temporal said it had more than 4,300 paying customers and processed more than 1.9 trillion Temporal Cloud actions in August. The company’s funding and reported business scale provide context for the hire, but not evidence of the effectiveness of the authorization work.

The key unanswered questions are when Temporal will release the controls, what they will include in practice and how they will be evaluated. For now, the Oso team’s move signals a development effort, not a new security feature customers can turn on.

Related coverage

More from Business

More Business