openclaw - ✅(Solved) Fix MiniMax plugin manifest missing providerAuthAliases after provider auth aliases system update [2 pull requests, 2 comments, 3 participants]

openclaw2026-04-09 15:54:22

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.

GitHub issue URL

Helpful · Quick feedback

GitHub stats

openclaw/openclaw#63823•Fetched 2026-04-10 03:41:48

View on GitHub

Comments

Participants

Timeline

Reactions

Author

Participants

Timeline (top)

commented ×2cross-referenced ×1referenced ×1renamed ×1

Error Message

→ ❌ 401 authentication error 3. Observe MiniMax fails silently with 401 auth error

Root Cause

Root Cause Analysis

Fix Action

Solution

Add the missing providerAuthAliases field to extensions/minimax/openclaw.plugin.json:

{
  "id": "minimax",
  "providers": ["minimax", "minimax-portal"],
  "providerAuthEnvVars": { ... },
  "providerAuthAliases": {
    "minimax-cn": "minimax",
    "minimax-portal-cn": "minimax-portal"
  },
  "providerAuthChoices": [ ... ]
}

PR fix notes

PR #63898: fix(minimax): add provider auth aliases to manifest for new auth system

Repository: openclaw/openclaw
Author: kamusis
State: closed | merged: False
Link: https://github.com/openclaw/openclaw/pull/63898

Description (problem / solution / changelog)

Fixes #63823

Problem

OpenClaw's new Provider Auth Aliases system requires plugins to explicitly declare alias mappings in their manifest. MiniMax plugin was missing this, causing CN endpoint authentication to fail.

Solution

Added providerAuthAliases field to extensions/minimax/openclaw.plugin.json:

"providerAuthAliases": {
  "minimax-cn": "minimax",
  "minimax-portal-cn": "minimax-portal"
}

Verification

This fix has been tested locally and verified to resolve the authentication issue for MiniMax CN endpoints.

Changed files

extensions/minimax/openclaw.plugin.json (modified, +4/-0)
skills/line-weather-interactive/SKILL.md (added, +147/-0)
skills/telegram-weather-interactive/SKILL.md (added, +197/-0)

PR #67195: fix(minimax): add provider auth aliases to manifest (fixes #63823)

Repository: openclaw/openclaw
Author: kamusis
State: open | merged: False
Link: https://github.com/openclaw/openclaw/pull/67195

Description (problem / solution / changelog)

Problem

MiniMax CN endpoint authentication has been failing since OpenClaw's new Provider Auth Aliases system was introduced (commits 9e4f478f86 and 7fd6e2ec4c). This new system requires plugins to explicitly declare alias mappings in their manifest file via the providerAuthAliases field.

Issue: #63823

Root Cause

The MiniMax plugin was missing the providerAuthAliases declaration in its manifest, causing:

Auth resolution fails when minimax-cn alias is activated for CN endpoints
System cannot find matching auth profile (minimax:cn)
401 authentication error
Automatic fallback to other models (Google Gemini, xAI, etc.)

Every user who updates OpenClaw experiences this issue silently - they think they're using MiniMax but it's actually falling back to another model.

Solution

Added providerAuthAliases field to extensions/minimax/openclaw.plugin.json:

"providerAuthAliases": {
  "minimax-cn": "minimax",
  "minimax-portal-cn": "minimax-portal"
}

Also includes manifest assertion test (as recommended by Greptile) to prevent accidental desynchronization of aliases in future edits.

Verification

✅ Tested locally - MiniMax CN endpoint now authenticates successfully without fallback ✅ No more silent model switching ✅ Session logs confirm proper provider resolution

Impact

Severity: CRITICAL

Affects all users who configured MiniMax CN endpoint
Every openclaw update overwrites local patches, requiring manual re-patching
Silent fallback means users may not realize they're not using their configured model

Changes

Added providerAuthAliases to manifest
Added test assertion to verify manifest correctness
Follows established pattern from volcengine and byteplus extensions

Changed files

extensions/minimax/index.test.ts (modified, +15/-0)
extensions/minimax/openclaw.plugin.json (modified, +4/-0)

Code Example

// This field is missing from the manifest:
"providerAuthAliases": {
  "minimax-cn": "minimax",
  "minimax-portal-cn": "minimax-portal"
}

---

// extensions/minimax/provider-registration.ts:173
api.registerProvider({
  id: "minimax",
  hookAliases: ["minimax-cn"],  // ← Legacy mechanism, no longer recognized by new system
})

---

hookAliases: ["minimax-cn"]
  → Auth system directly recognizes alias
  → Looks up auth profile: minimax:cn
  → ✅ Success - finds and uses auth key

---

hookAliases: ["minimax-cn"] (only in code, not in manifest)
  → New auth aliases system checks manifest
  → manifest has no providerAuthAliases field
  → New system doesn't recognize this alias
  → Falls back to original provider ID "minimax"
  → Searches for auth profile: minimax (not minimax:cn)
  → ❌ 401 authentication error
  → Auto-fallback to next model (Google Gemini/xAI, etc)

---

{
  "id": "minimax",
  "providers": ["minimax", "minimax-portal"],
  "providerAuthEnvVars": { ... },
  "providerAuthAliases": {
    "minimax-cn": "minimax",
    "minimax-portal-cn": "minimax-portal"
  },
  "providerAuthChoices": [ ... ]
}

RAW_BUFFERClick to expand / collapse

Problem Description

OpenClaw's official update on 2026-04-08/09 introduced a new Provider Auth Aliases system (commits 9e4f478f86 and 7fd6e2ec4c) that fundamentally changed how auth profiles are resolved, causing MiniMax CN endpoint authentication to fail.

Root Cause Analysis

System Architecture Change

Commit 9e4f478f86 (2026-04-08 19:01:42) - Introduced new provider auth aliases system

New system requires plugins to declare alias mappings via providerAuthAliases field in manifest
Legacy code-level hookAliases declarations are no longer recognized by the new system

Commit 7fd6e2ec4c (2026-04-09 00:42:35) - Implemented auth alias security filtering

Only aliases explicitly declared in manifest are recognized
Prevents untrusted workspace plugins from hijacking provider auth

MiniMax Plugin Issue

The MiniMax plugin's extensions/minimax/openclaw.plugin.json is missing the providerAuthAliases field:

// This field is missing from the manifest:
"providerAuthAliases": {
  "minimax-cn": "minimax",
  "minimax-portal-cn": "minimax-portal"
}

But the code still declares the legacy mechanism:

// extensions/minimax/provider-registration.ts:173
api.registerProvider({
  id: "minimax",
  hookAliases: ["minimax-cn"],  // ← Legacy mechanism, no longer recognized by new system
})

Auth Failure Flow

Before Yesterday (✅ Working):

hookAliases: ["minimax-cn"]
  → Auth system directly recognizes alias
  → Looks up auth profile: minimax:cn
  → ✅ Success - finds and uses auth key

After Yesterday's Update (❌ Fails):

hookAliases: ["minimax-cn"] (only in code, not in manifest)
  → New auth aliases system checks manifest
  → manifest has no providerAuthAliases field
  → New system doesn't recognize this alias
  → Falls back to original provider ID "minimax"
  → Searches for auth profile: minimax (not minimax:cn)
  → ❌ 401 authentication error
  → Auto-fallback to next model (Google Gemini/xAI, etc)

Reproduction Steps

Update OpenClaw to 2026-04-09 or later
Use MiniMax as primary model with CN endpoint configured
Observe MiniMax fails silently with 401 auth error
Model auto-switches to Google or xAI

Affected Users

All users who configured MiniMax CN endpoint
All users who updated OpenClaw after 2026-04-09

Solution

Add the missing providerAuthAliases field to extensions/minimax/openclaw.plugin.json:

{
  "id": "minimax",
  "providers": ["minimax", "minimax-portal"],
  "providerAuthEnvVars": { ... },
  "providerAuthAliases": {
    "minimax-cn": "minimax",
    "minimax-portal-cn": "minimax-portal"
  },
  "providerAuthChoices": [ ... ]
}

Related Code Locations

New auth aliases system: src/agents/provider-auth-aliases.ts
MiniMax plugin manifest: extensions/minimax/openclaw.plugin.json
Auth alias resolution: src/agents/provider-auth-aliases.ts lines 1-70
MiniMax provider registration: extensions/minimax/provider-registration.ts line 173

extent analysis

TL;DR

Add the missing providerAuthAliases field to the MiniMax plugin's manifest file to resolve the authentication issue.

Guidance

Update the extensions/minimax/openclaw.plugin.json file to include the providerAuthAliases field with the required mappings.
Verify that the providerAuthAliases field is correctly formatted and includes all necessary aliases.
Remove or update the legacy hookAliases declarations in the code to ensure compatibility with the new auth aliases system.
Test the MiniMax plugin with the updated manifest file to confirm that authentication is successful.

Example

"providerAuthAliases": {
  "minimax-cn": "minimax",
  "minimax-portal-cn": "minimax-portal"
}

Notes

The solution assumes that the providerAuthAliases field is the only missing component required for authentication to work. If issues persist after updating the manifest file, further investigation into the auth alias resolution and provider registration code may be necessary.

Recommendation

Apply the workaround by adding the providerAuthAliases field to the MiniMax plugin's manifest file, as this is the most direct solution to resolve the authentication issue caused by the introduction of the new Provider Auth Aliases system.

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?

#api #generation error #database connection #vector store #embedding generation

Still need to ship something?

×6

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

openclaw - ✅(Solved) Fix MiniMax plugin manifest missing providerAuthAliases after provider auth aliases system update [2 pull requests, 2 comments, 3 participants]

Recommended Tools

GitHub issue graph ai analysis

Error Message

Root Cause

Root Cause Analysis

Fix Action

Solution

PR fix notes

PR #63898: fix(minimax): add provider auth aliases to manifest for new auth system

Description (problem / solution / changelog)

Problem

Solution

Verification

Changed files

PR #67195: fix(minimax): add provider auth aliases to manifest (fixes #63823)

Description (problem / solution / changelog)

Problem

Root Cause

Solution

Verification

Impact

Changes

Changed files

Code Example

Problem Description

Root Cause Analysis

System Architecture Change

MiniMax Plugin Issue

Auth Failure Flow

Reproduction Steps

Affected Users

Solution

Related Code Locations

extent analysis

TL;DR

Guidance

Example

Notes

Recommendation

Still need to ship something?

RELATED_DISCOVERY

TRENDING