Skip to content
openma

What's new

September 11, 2026

Section titled “September 11, 2026”

OpenMA now serves two managed-agent API contracts. The Claude-compatible API continues to run on Node and Cloudflare; the Node server also accepts the official OpenAI SDK at /openai/v1.

OpenAI Agents API on Node

Section titled “OpenAI Agents API on Node”

Use openai@7.15.0 to create saved or inline agents, run durable sessions, stream live events, and query Turns and Items. Client function calls pause for your application’s result and continue the same turn, including after a server restart. Subagents have independent histories with creation, messaging, wait, interrupt, close, and resume controls; the current runtime delegates one level deep. Connected environments expose real sandbox files and publish completed turn outputs as immutable Artifacts.

Start with the OpenAI Agents guide, including its runtime limits. The endpoint is Node-only, and advanced environment, plugin, model, and MCP settings are not all executable yet.

Durable execution and recovery

Section titled “Durable execution and recovery”

Recent changes harden durable queues and execution leases so persisted work can be recovered and stale owners cannot finalize another execution’s state. OpenAI input retries reuse persisted identities, and session creation queues initial input durably. Turn and Item views are reconstructed from committed event order.

See Recovery & Idempotency and Managed Runtime Host for the underlying coordination and persistence contracts.

Sandboxed harnesses and managed resources

Section titled “Sandboxed harnesses and managed resources”

Pi can run the agent loop on the host, while ACP-compatible harnesses such as Claude Code and Codex can run inside the sandbox. Managed sessions resolve attached files, declared skills, and MCP access through the control plane. Credential egress is bound before warmup network work, and startup failures are reported through session events.

Use Concepts → Harness to choose an execution placement and Runtime Host → Credential egress to check provider enforcement. Provider adapters have separate offline and live certification lanes; an offline pass does not certify a vendor deployment.

File-based persistent memory

Section titled “File-based persistent memory”

Memory Stores are mounted files accessed with ordinary agent file tools. The Cloudflare managed runtime now synchronizes writable memory back through the control plane and detects concurrent edits. The current Node managed runner supports read-only mounts; read-write attachment is rejected until reverse synchronization is configured.

The Memory Stores guide covers mounts, access modes, version history, and conflicts. This supersedes earlier descriptions of a dedicated memory tool or a Vectorize-backed memory store.

Choose your next step

Section titled “Choose your next step”