Mirrors/openclaw
1
0
Fork 0
mirror of https://github.com/openclaw/openclaw.git synced 2026-04-06 17:33:55 +02:00
Code Issues Packages Projects Releases Wiki Activity

docs: fix minimax usage docs merge markers

Browse Source
This commit is contained in:
Peter Steinberger
2026-04-04 12:43:44 +01:00
parent a375635a9a
commit 9da0feeecf
2 changed files with 13 additions and 5 deletions
Download Patch File Download Diff File Expand all files Collapse all files

17
docs/concepts/usage-tracking.md
View File

@@ -37,10 +37,19 @@ title: "Usage Tracking"
- JSON usage falls back to `stats`; `stats.cached` is normalized into
`cacheRead`.
- **OpenAI Codex**: OAuth tokens in auth profiles (accountId used when present).
<<<<<<< HEAD
- **MiniMax**: API key or MiniMax OAuth auth profile. OpenClaw treats `minimax`, `minimax-cn`, and `minimax-portal` as the same MiniMax quota surface, prefers stored MiniMax OAuth when present, and otherwise falls back to `MINIMAX_CODE_PLAN_KEY`, `MINIMAX_CODING_API_KEY`, or `MINIMAX_API_KEY`. MiniMax's raw `usage_percent` / `usagePercent` fields mean **remaining** quota, so OpenClaw inverts them before display; count-based fields win when present.
- Coding-plan window labels come from provider hours/minutes fields when present, then fall back to the `start_time` / `end_time` span.
- If the coding-plan endpoint returns `model_remains`, OpenClaw prefers the chat-model entry, derives the window label from timestamps when explicit `window_hours` / `window_minutes` fields are absent, and includes the model name in the plan label.
- **MiniMax**: API key or MiniMax OAuth auth profile. OpenClaw treats
`minimax`, `minimax-cn`, and `minimax-portal` as the same MiniMax quota
surface, prefers stored MiniMax OAuth when present, and otherwise falls back
to `MINIMAX_CODE_PLAN_KEY`, `MINIMAX_CODING_API_KEY`, or `MINIMAX_API_KEY`.
MiniMax's raw `usage_percent` / `usagePercent` fields mean **remaining**
quota, so OpenClaw inverts them before display; count-based fields win when
present.
- Coding-plan window labels come from provider hours/minutes fields when
present, then fall back to the `start_time` / `end_time` span.
- If the coding-plan endpoint returns `model_remains`, OpenClaw prefers the
chat-model entry, derives the window label from timestamps when explicit
`window_hours` / `window_minutes` fields are absent, and includes the model
name in the plan label.
- **Xiaomi MiMo**: API key via env/config/auth store (`XIAOMI_API_KEY`).
- **z.ai**: API key via env/config/auth store.

1
docs/providers/minimax.md
View File

@@ -237,7 +237,6 @@ Current MiniMax auth choices in the wizard/CLI:
- OpenClaw normalizes MiniMax coding-plan usage to the same `% left` display
used by other providers. MiniMax's raw `usage_percent` / `usagePercent`
fields are remaining quota, not consumed quota, so OpenClaw inverts them.
<<<<<<< HEAD
Count-based fields win when present. When the API returns `model_remains`,
OpenClaw prefers the chat-model entry, derives the window label from
`start_time` / `end_time` when needed, and includes the selected model name