OpenAI advanced configuration

Direct API-key requests use SSE by default. Set params.transport when you want Responses WebSocket mode on an eligible official OpenAI endpoint.

Cached modes keep one eligible connection per session. When the prior request and response still match the current history, OpenClaw sends only the new input and references the prior response with previous_response_id. Otherwise it sends full history without that reference.

A setup or handshake failure before request dispatch falls back to SSE; it is not retried or reconnected first. After dispatch, failures with an unknown outcome remain replay-unsafe and fail closed. The explicit server rejections previous_response_not_found, websocket_connection_limit_reached, and the Zero Data Retention unsupported_parameter rejection of previous_response_id are safe exceptions: OpenClaw closes the failed socket and retries that turn once over SSE with full history and no rejected previous_response_id.

{
  agents: {
    defaults: {
      models: {
        "openai/gpt-5.5": {
          agentRuntime: { id: "openclaw" },
          params: { transport: "auto" },
        },
      },
    },
  },
}

ChatGPT Responses SSE turns may exceed 16 MiB in total. The parser bounds each buffered event to 16 MiB of bytes before decoding or parsing it, and cancels oversized events, including events without a closing delimiter.

For cached ChatGPT Responses WebSocket requests, an explicit "Rustponses cannot replay" rejection before any response event triggers one retry on a fresh connection with full input instead of the cached response reference. The retry preserves reasoning, compaction, and completed tool results; it does not rerun tools. Rejections of full input and failures after response events remain terminal.

Related OpenAI docs:

• Responses API WebSocket mode
• Streaming API responses (SSE)

OpenClaw exposes a shared fast-mode toggle for openai/*:

• Chat/UI: /fast status|auto|on|off|ultrafast|default
• Config: agents.defaults.models["<provider>/<model>"].params.fastMode

Valid params.fastMode / params.fast_mode values and valid cutoff keys are typed runtime controls. They do not count as authored provider request params and do not select OpenClaw or Codex. The example below pins embedded OpenClaw because it describes a direct provider request.

When enabled on the embedded runtime, OpenClaw maps fast mode to OpenAI API Fast mode (formerly Priority processing) and sends service_tier = "priority". Explicit /fast ultrafast or params.fastMode: "ultrafast" sends service_tier = "ultrafast" instead. The selected account and model must support that tier; the provider can reject it or return a different effective tier. Fast mode does not rewrite reasoning or text.verbosity. fastMode: "auto" starts new model calls fast until the auto cutoff, then starts later retry, fallback, tool-result, or continuation calls without fast mode. The cutoff defaults to 60 seconds; set params.fastAutoOnSeconds on the active model to change it.

For the embedded OpenClaw runtime, the Control UI uses provider model and route limits when offering Standard, Fast, and Ultrafast. This works for auth profiles, environment keys, and provider config (including SecretRefs). Models limited to Standard or Fast keep those restrictions. Custom endpoints and ChatGPT account catalogs retain their own tier policy.

If a response to an Ultrafast request echoes a different service_tier, OpenClaw records a temporary observation for that credential, model, and route. Ultrafast stays selectable, and the composer's Speed tooltip shows the requested and served tiers. Later calls keep requesting the selected tier. A response honoring it clears the hint immediately; otherwise the observation expires five minutes after its latest occurrence.

If the native OpenAI API explicitly rejects service_tier before output, tool activity, or active-response steering, OpenClaw automatically retries that request at a slower tier: Ultrafast → Fast → Standard. The hint records that recovery without changing saved preferences or later requests. It does not retry tier errors after cancellation or an ambiguous connection failure. Explicit low-level tier overrides are still sent as configured.

Observations also clear on credential replacement, profile discovery refresh, or retirement of the prepared runtime, and are not persisted across restarts. ChatGPT-account availability remains based on authenticated account catalog discovery.

{
  agents: {
    defaults: {
      models: {
        "openai/gpt-5.5": {
          agentRuntime: { id: "openclaw" },
          params: { fastMode: "auto", fastAutoOnSeconds: 30 },
        },
      },
    },
  },
}

Fast mode is premium-priced and model-specific. GPT-5.6 Sol API Fast mode currently costs 2× Standard token pricing, with long-context multipliers stacking as described in context window defaults and long-context opt-in. ChatGPT/Codex-credit Fast mode is a separate billing system: GPT-5.6 and GPT-5.5 currently consume 2.5× Standard credits, while API-key Codex runs use API token pricing. See Fast mode, API pricing, and Codex speed.

OpenAI now calls this API product Fast mode; it was formerly Priority processing. OpenClaw sends the wire value service_tier = "priority". Set an explicit tier per model on the embedded OpenClaw runtime:

{
  agents: {
    defaults: {
      models: {
        "openai/gpt-5.5": {
          agentRuntime: { id: "openclaw" },
          params: { serviceTier: "priority" },
        },
      },
    },
  },
}

Supported values: auto, default, flex, priority, ultrafast. Availability depends on the selected provider route, account, and model.

For store-capable direct OpenAI Responses models (openai/* resolved to api.openai.com), the OpenAI plugin's OpenClaw stream wrapper auto-enables server-side compaction:

• Forces store: true (unless model compat sets supportsStore: false)
• Injects context_management: [{ type: "compaction", compact_threshold: ... }]
• Default compact_threshold: 70% of contextWindow (or 80000 when unavailable)

The same resolved route and effective threshold gate the client preflight, so OpenClaw does not delay local compaction unless the transport will inject context_management. ChatGPT OAuth, custom proxies, and routes with compat.supportsStore: false are not store-capable and therefore ignore these server-compaction controls. This applies to the built-in OpenClaw runtime path and to OpenAI provider hooks used by embedded runs. The native Codex app-server harness manages its own context through Codex and is not affected by this setting.

OpenAI emits the compacted state as an encrypted compaction output item. Keep that item opaque. For stateless continuation, carry the newest item forward and drop the earlier input prefix it replaces. OpenClaw does this automatically: it persists and replays the item only for the matching route, session, and auth identity, preserves it across worker transcript commits, and filters it from user-visible history and diagnostics. Never display or log the encrypted content.

Enable explicitly

Useful for store-capable endpoints like Azure OpenAI Responses. Setting this to true does not override endpoint or supportsStore capability:

{
  agents: {
    defaults: {
      models: {
        "azure-openai-responses/gpt-5.5": {
          params: { responsesServerCompaction: true },
        },
      },
    },
  },
}

Custom threshold

{
  agents: {
    defaults: {
      models: {
        "openai/gpt-5.5": {
          params: {
            responsesServerCompaction: true,
            responsesCompactThreshold: 120000,
          },
        },
      },
    },
  },
}

Disable

{
  agents: {
    defaults: {
      models: {
        "openai/gpt-5.5": {
          params: { responsesServerCompaction: false },
        },
      },
    },
  },
}

For openai provider GPT-5-family models run through OpenClaw's embedded runtime, OpenClaw already defaults to a stricter execution contract called strict-agentic. It auto-activates whenever the resolved provider is openai and the model id matches the GPT-5 family, unless config explicitly opts back out:

{
  agents: {
    defaults: {
      embeddedAgent: { executionContract: "default" },
    },
  },
}

Setting "strict-agentic" explicitly is a no-op on a supported lane (it is already the default) and inert on unsupported provider/model pairs.

With strict-agentic active, OpenClaw:

• Makes progress_card available for substantial work unless tools.updatePlan disables it
• Retries structurally empty or reasoning-only turns with a visible-answer continuation
• Uses explicit harness plan events when the selected harness provides them

OpenClaw does not classify assistant prose to decide whether a turn is a plan, progress update, or final answer.

OpenClaw treats direct OpenAI, Codex, and Azure OpenAI endpoints differently from generic OpenAI-compatible /v1 proxies:

Native routes (openai/*, Azure OpenAI):

• Keep reasoning: { effort: "none" } only for models that support the OpenAI none effort
• Omit disabled reasoning for models or proxies that reject reasoning.effort: "none"
• Default tool schemas to strict mode
• Attach hidden attribution headers on verified native hosts only (Azure OpenAI does not get these headers, even though it is a native route)
• Keep OpenAI-only request shaping (service_tier, store, reasoning-compat, prompt-cache hints)
• Send tool-bearing turns for reasoning models configured with openai-completions on api.openai.com to /v1/responses, because Chat Completions rejects function tools with reasoning for current GPT models. Credentials, endpoint host, and proxy routes are unchanged.

Proxy/compatible routes:

• Use looser compat behavior
• Strip Completions store from non-native openai-completions payloads
• Accept advanced params.extra_body/params.extraBody pass-through JSON for OpenAI-compatible Completions proxies
• Accept params.chat_template_kwargs for OpenAI-compatible Completions proxies such as vLLM
• Do not force strict tool schemas or native-only headers

If a usable tool schema is incompatible with requested strict mode, the request uses strict: false. Debug logs report the downgrade under openai-transport, with a bounded sample of incompatible tools. Built-in and managed Responses requests share duplicate suppression for the same model and schemas. Compatibility checks inspect schema constraints, not literal names in schema maps or annotation data such as examples and defaults.