openclaw - 💡(How to fix) Fix doctor: model ref warning should check auth profile before suggesting openai-codex/* → openai/* rewrite [2 comments, 3 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#78533Fetched 2026-05-07 03:35:46
View on GitHub
Comments
2
Participants
3
Timeline
3
Reactions
3
Timeline (top)
commented ×2subscribed ×1

Root Cause

regardless of the user authentication method. Users who use OpenAI Codex OAuth (mode=oauth in auth.profiles) intentionally use the openai-codex/ prefix because their models are routed through the Codex app-server harness, not the PI OpenAI path.

Code Example

openai-codex/gpt-5.4 should become openai/gpt-5.4
openai-codex/gpt-5.4-mini should become openai/gpt-5.4-mini
RAW_BUFFERClick to expand / collapse

Problem

openclaw doctor always prints:

openai-codex/gpt-5.4 should become openai/gpt-5.4
openai-codex/gpt-5.4-mini should become openai/gpt-5.4-mini

regardless of the user authentication method. Users who use OpenAI Codex OAuth (mode=oauth in auth.profiles) intentionally use the openai-codex/ prefix because their models are routed through the Codex app-server harness, not the PI OpenAI path.

The doctor --fix mode already checks whether Codex is installed and has usable OAuth before rewriting refs (it selects agentRuntime.id: "codex" when applicable). But the read-only warning emitted during openclaw doctor (without --fix) does not perform this pre-check. This creates confusion:

  1. Users see a scary warning and think their config is broken.
  2. Users who run doctor --fix expecting a fix may get an unnecessary migration on a working setup.
  3. New OAuth users get misled about whether their config is correct.

Expected behavior

The read-only warning should check the user auth profiles before emitting:

  • If auth.profiles contains an openai-codex entry with mode=oauth and the Codex harness is available → suppress the "should become" warning (the config is correct as-is), or emit a more nuanced message like: "openai-codex/ refs are valid for your Codex OAuth setup. Run doctor --fix to migrate to canonical openai/* refs with codex runtime if desired."*
  • If no Codex OAuth is configured → keep the current warning (legacy refs that should be migrated).

Suggested approach

In the Codex route repair check doctor warning pass, read auth.profiles and check for a usable openai-codex OAuth profile before emitting the "should become" suggestion. The same auth-profile awareness that --fix already has should be applied to the read-only warning path.

Why it matters

New OpenClaw users setting up Codex OAuth get an unnecessary false alarm on their first openclaw doctor run. Experienced users who rely on Codex OAuth keep seeing warning noise on every health check, eroding trust in doctor diagnostic output.

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…

FAQ

Expected behavior

The read-only warning should check the user auth profiles before emitting:

  • If auth.profiles contains an openai-codex entry with mode=oauth and the Codex harness is available → suppress the "should become" warning (the config is correct as-is), or emit a more nuanced message like: "openai-codex/ refs are valid for your Codex OAuth setup. Run doctor --fix to migrate to canonical openai/* refs with codex runtime if desired."*
  • If no Codex OAuth is configured → keep the current warning (legacy refs that should be migrated).

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 doctor: model ref warning should check auth profile before suggesting openai-codex/* → openai/* rewrite [2 comments, 3 participants]