# OpenAI ships Agents SDK v0.24.0-alpha.7 with durable sessions and usage budgets

published: 2026-11-08T07:05:25.891Z
topic: frameworks
source: https://github.com/openai/openai-agents-python/releases/tag/v0.24.0-alpha.7
url: https://aiagentnews.io/stories/openai-ships-agents-sdk-v0-24-0-alpha-7-with-durable-sessions-and-usage-budgets

OpenAI released alpha 7 of its Agents SDK, adding durable root sessions, hosted tools and observed usage budgets to the native runtime. The alpha also changes several defaults and names, so existing projects should review the upgrade steps before moving over.

The release adds SessionStore, SQLiteSessionStore and CustomStorage so applications can keep root conversation history and automatic Python tool results in their own storage. Uncertain tool calls can be reported for explicit reconciliation, and neither local profiles nor custom stores replay them automatically. Hosted FileSearch, CodeInterpreter and ImageGeneration tools are also added, but they require an API-key provider and a compatible standard Responses model.

Context handling gets new hooks, including Agent.transform_context, before_compact and before_complete, which can accept, continue or stop a proposed answer. RunBudget caps root request admissions, reported tokens or estimated cost, and children are excluded from it. MCP sessions can list and read resources and prompts, and speech workflows can now run on native sessions.

Several changes affect existing code. New environments default to a strict write policy that requires a compatible Linux or macOS executor, and child step callbacks now receive a single ChildStepContext. The default reasoning effort for gpt-6-astra, gpt-6.1-sol and gpt-5.6-sol moves from low to medium, and MCP approval modes are renamed to "native" and "preapproved".

## Why it matters if you build agents

Developers who want conversation history in their own storage can now use SessionStore, SQLiteSessionStore or CustomStorage, but they must handle uncertain tool calls through explicit reconciliation. Anyone upgrading from alpha.6 should check write policies, reasoning settings and MCP approval names before running existing agents. Because this is a pre-release, treat these interfaces as unstable.