Skip to content

[Bug]: Agent-specific MiniMax auth resolves from main agent auth-profiles.json #64274

@blaspat

Description

@blaspat

Bug type

Regression (worked before, now fails)

Beta release blocker

No

Summary

OpenClaw version:
2026.4.9 (0512059)

Extra confirmation:

  • ~/.openclaw/agents/kate/agent/auth-profiles.json does contain:
    • minimax-portal:default
    • provider: minimax-portal

Symptom:

  • dashboard chat, /new, and /reset return:
    • ⚠️ API rate limit reached. Please try again later.
  • logs mention:
    • auth profile failure state updated
    • embedded run failover decision

Steps to reproduce

What I did:

  • configured MiniMax OAuth
  • dashboard session uses agent kate
  • /model status shows:
    • Current: minimax-portal/MiniMax-M2.7
    • Agent: kate
    • Auth file: ~/.openclaw/agents/kate/agent/auth-profiles.json

Expected behavior

  • kate should resolve MiniMax auth from ~/.openclaw/agents/kate/agent/auth-profiles.json

Actual behavior

  • openclaw models status --agent kate shows:
    • Auth store: ~/.openclaw/agents/kate/agent/auth-profiles.json
    • but effective MiniMax auth resolves from:
      ~/.openclaw/agents/main/agent/auth-profiles.json

OpenClaw version

2026.4.9 (0512059)

Operating system

Ubuntu 24.04

Install method

No response

Model

minimax-portal/MiniMax-M2.7

Provider / routing chain

minimax

Additional provider/model setup details

No response

Logs, screenshots, and evidence

Impact and severity

No response

Additional information

No response

Metadata

Metadata

Assignees

Labels

P1High-priority user-facing bug, regression, or broken workflow.bugSomething isn't workingclawsweeper:linked-pr-openClawSweeper found an open linked pull request for this issue.clawsweeper:needs-security-reviewClawSweeper marked this issue as needing security-sensitive review.clawsweeper:no-new-fix-prClawSweeper does not recommend queueing a new automated fix PR for this issue.clawsweeper:source-reproClawSweeper found a high-confidence source-level issue reproduction.impact:auth-providerAuth, provider routing, model choice, or SecretRef resolution may break.impact:securitySecurity boundary, credential, authz, sandbox, or sensitive-data risk.issue-rating: 🦞 diamond lobsterVery strong issue quality with high-confidence source-level or clear reproduction.regressionBehavior that previously worked and now failsstaleMarked as stale due to inactivity

Type

No type
No fields configured for issues without a type.

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions