openclaw - 💡(How to fix) Fix Feature request: supported route for ChatGPT Pro / Deep Research style agents [1 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#71888Fetched 2026-04-26 05:07:03
View on GitHub
Comments
0
Participants
1
Timeline
0
Reactions
1
Author
Participants
RAW_BUFFERClick to expand / collapse

It would be really useful to have a supported OpenClaw route for ChatGPT Pro style deep research / Research Pro workflows.

Right now I can use openai-codex/gpt-5.5 successfully through the Codex/OpenAI subscription path, but there does not seem to be a valid model route for a higher tier research mode. I tried configuring a dedicated research-pro agent with openai-codex/gpt-5.5-pro, but that model does not appear in openclaw models list, and the subagent runs completed with no usable output.

What I am looking for:

  • A documented way to expose a true ChatGPT Pro / Deep Research / Research Pro style model or workflow inside OpenClaw, if the upstream provider supports it
  • Clear model catalog naming so users do not guess routes like openai-codex/gpt-5.5-pro
  • A recommended agent config pattern for high-value research agents that should be read-only, cite sources, and avoid file/message mutations
  • If this is not currently possible through the Codex subscription/OAuth path, a note in the docs would help prevent confusion

Why this matters:

OpenClaw already makes it easy to create specialized agents. A dedicated research agent is one of the highest-value use cases, but it is hard to know whether the current limitation is model catalog support, provider access, subscription restrictions, or runtime behavior.

A good outcome would be either:

  1. A supported model ID / provider route for this kind of Pro research workflow, or
  2. Documentation saying it is not exposed yet, with the recommended fallback setup

Happy to test any suggested route or config.

extent analysis

TL;DR

Configure a dedicated research agent with a supported model ID and provider route, or await documentation on exposing ChatGPT Pro/Research Pro workflows in OpenClaw.

Guidance

  • Check the OpenClaw documentation for any updates on supported models and provider routes for ChatGPT Pro/Research Pro workflows.
  • Verify the availability of openai-codex/gpt-5.5-pro in the openclaw models list to ensure it's not a catalog naming issue.
  • Test alternative model IDs and provider routes to find a suitable replacement for high-value research agents.
  • Consider reaching out to the OpenClaw community or support for guidance on configuring read-only, source-citing research agents.

Example

No code snippet is provided as the issue is focused on configuration and model support rather than code implementation.

Notes

The solution may depend on the specific OpenClaw version, Codex subscription, and OAuth configuration being used. The issue highlights the need for clear documentation on supported models and provider routes.

Recommendation

Apply a workaround by testing alternative model IDs and provider routes until official support for ChatGPT Pro/Research Pro workflows is documented. This approach allows for exploration of possible solutions while awaiting official guidance.

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…

Still need to ship something?

×6

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

Back to top recommendations

TRENDING