Issue Station
Sign In
Tools hereToolbox

openclaw - 💡(How to fix) Fix Custom models do not support OpenAI Responses API format [1 comments, 2 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
openclaw/openclaw#72725•Fetched 2026-04-28 06:32:55
View on GitHub
Comments
1
Participants
2
Timeline
2
Reactions
0
Author
misakiyro1314-cmykmisakiyro1314-cmyk
Participants
misakiyro1314-cmykmisakiyro1314-cmyksteipetesteipete
Timeline (top)
closed ×1commented ×1
RAW_BUFFERClick to expand / collapse

The Custom Models feature in the AutoClaw desktop client currently only supports openai-completions and anthropic-messages API formats. However, some third-party API providers only support the OpenAI Responses API (/v1/responses) and do not support the traditional Chat Completions endpoint (/v1/chat/completions).

The open-source OpenClaw already supports the Responses API through its built-in openai-codex provider (using the openai-codex-responses transport), but AutoClaw custom models cannot reuse this transport.

Expected behavior:

  • Add OpenAI Responses (openai-codex-responses) as an API format option in custom model configuration.
  • Or allow custom providers to specify the use of the built-in Responses API transport.

Environment: AutoClaw webchat v0.1.13, Windows 11 x64

extent analysis

TL;DR

Add support for OpenAI Responses API format in AutoClaw custom model configuration to enable compatibility with third-party API providers.

Guidance

  • Investigate modifying the custom model configuration to include OpenAI Responses API format as an option, similar to the open-source OpenClaw implementation.
  • Explore allowing custom providers to specify the use of the built-in Responses API transport, potentially through a configuration parameter or setting.
  • Review the openai-codex-responses transport implementation in OpenClaw to understand how it can be adapted for use in AutoClaw custom models.
  • Consider adding a feature request or issue to the AutoClaw project to formally track and prioritize this enhancement.

Notes

The solution may require updates to the AutoClaw custom model configuration UI, backend API, or both, to support the new API format.

Recommendation

Apply workaround: Modify the custom model configuration to use the openai-codex-responses transport, if possible, or wait for an official update to AutoClaw that includes support for OpenAI Responses API format.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…
#api#response parsing#generation error#database connection#vector store

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

openclaw - 💡(How to fix) Fix Custom models do not support OpenAI Responses API format [1 comments, 2 participants]