Skip to content

MiniMax token usage always returns zeros in 2026.3.8 #43490

Description

@GiPPe

Summary

After upgrading from 2026.3.2 to 2026.3.8, MiniMax-M2.5 lastCallUsage always returns zeros for all token fields. This was working correctly in 2026.3.2.

Reproduction

openclaw agent --agent main --message "ping" --json

result.meta.agentMeta.lastCallUsage:

{
  "input": 0,
  "output": 0,
  "cacheRead": 0,
  "cacheWrite": 0,
  "total": 0
}

Evidence

Prometheus openclaw_tokens_total metric shows MiniMax tokens were being recorded correctly under 2026.3.2 up until the upgrade point. After upgrading to 2026.3.8, MiniMax series stopped emitting while OpenRouter/Gemini continues to report normally.

Metric Last MiniMax data Last Gemini data
openclaw_tokens_total{openclaw_model="MiniMax-M2.5"} 2026-03-11T20:30Z (pre-upgrade) Ongoing
openclaw_tokens_total{openclaw_model="google/gemini-2.5-flash-lite"} N/A 2026-03-11T21:43Z (current)

Environment

  • OpenClaw: 2026.3.8 (3caab92)
  • Model: minimax/MiniMax-M2.5 (via https://api.minimax.io)
  • Platform: Raspberry Pi (aarch64), Node v22.18.0
  • OTEL: diagnostics-otel plugin → Prometheus OTLP receiver (working for other metrics)

Expected

lastCallUsage should contain non-zero token counts as it did in 2026.3.2.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Fields

    Priority

    None yet

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions