Issue Station
Sign In
Tools hereToolbox

openclaw - ✅(Solved) Fix configure wizard: minimax-portal OAuth configPatch missing api and auth fields (2026.4.10) [1 pull requests, 5 comments, 4 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#64794•Fetched 2026-04-12 13:26:45
View on GitHub
Comments
5
Participants
4
Timeline
9
Reactions
0
Author
kikibriankikibrian
Participants
kikibriankikibrianttomiczekttomiczekValkster70Valkster70YuZiHao666YuZiHao666
Timeline (top)
commented ×5referenced ×2closed ×1cross-referenced ×1

Root Cause

In provider-registration-DOd91Etq.js, createOAuthHandler() generates a configPatch that only includes baseUrl and models, but omits api and auth. The resolvePortalCatalog() function relies on these fields to determine the API protocol and auth mode, causing the provider to fail silently.

Fix Action

Workaround

Manually edit ~/.openclaw/openclaw.json to add:

"api": "anthropic-messages",
"auth": "oauth",

PR fix notes

PR #64964: fix(minimax): add missing api and authHeader to portal OAuth configPatch

Description (problem / solution / changelog)

Summary

  • Fix minimax-portal OAuth configPatch missing api and authHeader fields, causing provider auth resolution to fail after openclaw configure.

Fixes #64794

Test plan

  • Run openclaw configure with MiniMax OAuth and verify the resulting config includes api: "anthropic-messages" and authHeader: true under models.providers.minimax-portal
  • Verify model inference works after re-authentication

🤖 Generated with Claude Code

Changed files

  • CHANGELOG.md (modified, +1/-0)
  • extensions/minimax/index.test.ts (modified, +37/-0)
  • extensions/minimax/provider-registration.ts (modified, +2/-0)

Code Example

"minimax-portal": {
  "baseUrl": "https://api.minimaxi.com/anthropic",
  "api": "anthropic-messages",   // missing
  "auth": "oauth",              // missing
  "models": []
}

---

"api": "anthropic-messages",
"auth": "oauth",
RAW_BUFFERClick to expand / collapse

Bug Description

After upgrading to 2026.4.10 and running openclaw configure with MiniMax OAuth (CN), the resulting config for minimax-portal is missing the api and auth fields, causing all models to fail with 'no available auth profile'.

Steps to Reproduce

  1. Have a working minimax-portal config from a previous version (e.g. 2026.4.5)
  2. Upgrade to 2026.4.10
  3. Run openclaw configure and re-authenticate with MiniMax OAuth
  4. Observe that models.providers.minimax-portal has baseUrl and models: [] but is missing "api": "anthropic-messages" and "auth": "oauth"

Expected vs Actual Config

Missing fields that should be present:

"minimax-portal": {
  "baseUrl": "https://api.minimaxi.com/anthropic",
  "api": "anthropic-messages",   // missing
  "auth": "oauth",              // missing
  "models": []
}

Root Cause

In provider-registration-DOd91Etq.js, createOAuthHandler() generates a configPatch that only includes baseUrl and models, but omits api and auth. The resolvePortalCatalog() function relies on these fields to determine the API protocol and auth mode, causing the provider to fail silently.

Workaround

Manually edit ~/.openclaw/openclaw.json to add:

"api": "anthropic-messages",
"auth": "oauth",

Environment

  • OpenClaw: 2026.4.10
  • macOS: 12.7.6
  • Node: 22.22.2
  • Channel: minimax-cn-oauth

extent analysis

TL;DR

Manually adding the missing "api" and "auth" fields to the minimax-portal config in ~/.openclaw/openclaw.json may resolve the issue.

Guidance

  • Verify that the createOAuthHandler() function in provider-registration-DOd91Etq.js is correctly generating the configPatch with all necessary fields.
  • Check the resolvePortalCatalog() function to ensure it is handling the missing fields correctly and not failing silently.
  • Apply the provided workaround by manually editing ~/.openclaw/openclaw.json to add the missing fields, and then re-test the configuration.
  • Consider reviewing the changes made in the upgrade to 2026.4.10 to identify any potential causes for the missing fields.

Example

"minimax-portal": {
  "baseUrl": "https://api.minimaxi.com/anthropic",
  "api": "anthropic-messages",
  "auth": "oauth",
  "models": []
}

Notes

This solution assumes that the issue is specific to the MiniMax OAuth (CN) configuration and the 2026.4.10 version of OpenClaw. The workaround may not be applicable to other configurations or versions.

Recommendation

Apply the workaround by manually editing the config file, as it is a straightforward and temporary solution to resolve the issue until a more permanent fix is available.

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#batch processing#GPU compatibility#latency issue#model 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