Skip to main content
OpenAI Agents SDK apps usually integrate with Nullspace in one of two ways:

Wrap Nullspace As A Tool

Use this pattern when an Agents SDK app should create a machine, run a bounded command, and return a concise result to the agent. Your application process stays in control of credentials, retries, cleanup, tracing, handoffs, and approval state.

Deploy An Agents SDK Job

Use Agent Deployments when the whole Agents SDK app should run as a managed process instead of calling a machine from your local process.
See the OpenAI Agents SDK job example for a complete project.

Deploy An Agents SDK Service

Use mode = "service" when your Agents SDK app exposes an HTTP API, chat backend, or internal coordinator.

State Boundary

Nullspace owns deployment runs, service instances, backing machines, logs, outputs, URLs, and cleanup. OpenAI Agents SDK tracing, handoffs, and approval state stay owned by the Agents SDK app. Store framework run persistence in your database, a volume, or app-managed storage. The generic process-level deployment path is the supported path today. A future native Nullspace machine client adapter can make Nullspace machines feel like an Agents SDK machine backend, but it should not own the model loop, tracing, handoffs, approval state, or framework run persistence.