openclaw - ✅(Solved) Fix [Bug]: Agent-specific MiniMax auth resolves from main agent auth-profiles.json [1 pull requests, 1 comments, 2 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#64274Fetched 2026-04-11 06:15:34
View on GitHub
Comments
1
Participants
2
Timeline
4
Reactions
0
Author
Participants
Timeline (top)
labeled ×2commented ×1cross-referenced ×1

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

Root Cause

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

Fix Action

Fixed

PR fix notes

PR #64320: fix(auth-profiles): key runtime snapshots by original agentDir to prevent path collision

Description (problem / solution / changelog)

Summary

Fixes #64274 — runtimeAuthStoreSnapshots Map was keyed by resolved auth-store path, causing path collision when OPENCLAW_AGENT_DIR env-var pointed at a sub-agent directory: both main and the pointed-at agent snapshot resolved to the same path, resulting in one overwriting the other.

Changes

src/agents/auth-profiles/store.ts

  • Removed resolveRuntimeStoreKey() helper (which called resolveAuthStorePath())
  • Changed runtimeAuthStoreSnapshots Map key type from string to string | undefined
  • replaceRuntimeAuthProfileStoreSnapshots: now uses raw agentDir (undefined | path string) as key
  • resolveRuntimeAuthProfileStore: uses raw agentDir as lookup key; undefined key = main agent
  • saveAuthProfileStore: uses raw agentDir as runtime key

src/agents/auth-profiles.ensureauthprofilestore.test.ts

  • Added regression test keeps main and agent runtime snapshots distinct when OPENCLAW_AGENT_DIR points at the agent (#64274) covering the collision scenario

Verification

pnpm vitest run src/agents/auth-profiles.ensureauthprofilestore.test.ts — all 21 tests pass (including the new regression test).

Changed files

  • extensions/ollama/openclaw.plugin.json (modified, +2/-1)
  • src/agents/auth-profiles.ensureauthprofilestore.test.ts (modified, +132/-0)
  • src/agents/auth-profiles/store.ts (modified, +16/-21)
  • src/gateway/server-close.test.ts (modified, +64/-0)
  • src/gateway/server-close.ts (modified, +61/-57)
RAW_BUFFERClick to expand / collapse

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

extent analysis

TL;DR

The issue can likely be resolved by ensuring that the kate agent is correctly configured to use its own auth-profiles.json file.

Guidance

  • Verify that the ~/.openclaw/agents/kate/agent/auth-profiles.json file is correctly formatted and contains the expected auth profiles, including minimax-portal:default.
  • Check the OpenClaw configuration to ensure that the kate agent is properly set up to use its own auth-profiles.json file, rather than falling back to the main agent's file.
  • Investigate the "auth profile failure state updated" and "embedded run failover decision" log messages to determine if there are any additional issues with the auth profile configuration.
  • Consider running the openclaw command with increased verbosity or debugging output to gain more insight into the authentication process.

Example

No code example is provided, as the issue appears to be related to configuration rather than code.

Notes

The issue may be related to a misconfiguration of the kate agent or the auth-profiles.json file. Further investigation is needed to determine the root cause of the problem.

Recommendation

Apply workaround: Verify and correct the kate agent configuration to ensure it is using the correct auth-profiles.json file. This may involve updating the OpenClaw configuration or the auth-profiles.json file itself.

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

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

Still need to ship something?

×6

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

Back to top recommendations

TRENDING