Token Usage Statistics Show as 0 for Local Providers (LM Studio)

Sun, 15 Mar 2026 00:00:00 +0000

Symptom

When using LM Studio (or other local LLM providers) with OpenClaw, the web interface shows 0 tokens for both lifetime and past 30-day usage statistics. This occurs even though:

The model is actively being used for inference
Token usage data is being returned in the API responses from the local provider
Curl requests to the provider confirm the usage field is present in responses

Example API Response from LM Studio: { “usage”: { “prompt_tokens”: X, “completion_tokens”: Y, “total_tokens”: Z } }

The token counts are available but not being displayed in OpenClaw’s statistics dashboard.

Root Cause Analysis

The root cause is that OpenClaw is not capturing or displaying token usage statistics for local providers. While cloud providers (OpenAI, Anthropic, etc.) have built-in support for tracking and displaying usage metrics, local providers like LM Studio appear to lack this integration.

Specifically:

LM Studio does expose token usage data via the standard usage field in API responses
The OpenClaw web interface is designed to show usage statistics from stored/aggregated data
Local provider responses may not be properly parsed, stored, or retrieved for display in the UI
The routing and display logic may be optimized for cloud providers and not account for local provider metadata

This is a feature gap in the local provider integration, not a crash or data corruption issue.

Solution

For Users (Workaround):

Manual tracking: Keep a separate log of token usage by monitoring API response payloads directly via curl or a proxy tool
Check provider dashboard: Some local providers like LM Studio may have their own usage tracking (verify in LM Studio’s interface)
Use logging: Enable detailed API logging in OpenClaw to capture raw responses and manually calculate usage

For Developers (Fix Required):

The fix involves modifying the OpenClaw codebase to:

Parse the usage field from local provider API responses
Store token usage data in the same manner as cloud providers
Ensure the usage data flows through to the web UI’s statistics components
Add LM Studio and other local providers to the supported usage tracking list

Relevant code areas to investigate:

Provider response parsing logic (likely in src/providers/)
Usage statistics storage and retrieval (likely in src/database/ or src/storage/)
Web UI statistics rendering (likely in src/web/components/usage-statistics/)

Prevention

When using local providers, be aware that OpenClaw’s built-in usage statistics may not reflect actual token consumption
Consider using provider-native monitoring tools alongside OpenClaw
When evaluating token efficiency with local models, rely on direct API response analysis rather than OpenClaw’s dashboard

Additional Information

Affected Provider: LM Studio (and likely other local LLM providers with similar API structures)
Tested Endpoint: http://localhost:1234/v1/chat/completions
Confirmed Working: LM Studio does return standard OpenAI-compatible usage data
Environment: Tested with model qwen/qwen3.5-35b-a3b on Ubuntu 22.04

This issue represents a missing feature rather than a defect—local providers expose the necessary data, but OpenClaw’s frontend does not consume and display it.

Sources

GitHub Issue #49890

Lm-Studio on FixClaw