Skip to main content

Kimi CLI

The kimi_cli provider reads local session logs from Kimi CLI and Kimi Code CLI. It aggregates sessions and per-model input, output, cache-read, and cache-write tokens. Local session tracking works offline. When Kimi Code CLI credentials are available, it also reads subscription quota through a read-only API call. It is separate from the Moonshot API provider.

Detection and paths​

OpenUsage detects the kimi binary, a config file, or a sessions directory in either location:

ClientSessionsConfig
Kimi CLI~/.kimi/sessions/<group>/<uuid>/wire.jsonl~/.kimi/config.json
Kimi Code CLI~/.kimi-code/sessions/<group>/<uuid>/agents/<agent>/wire.jsonl~/.kimi-code/config.json

When both session directories exist, ~/.kimi/sessions takes priority. The default config is selected from the same client directory as the selected sessions. If only a config exists, it can still trigger detection.

Manual configuration​

Use provider_paths for provider-specific overrides. JSON paths must be absolute; a literal ~ is not expanded.

{
  "accounts": [
    {
      "id": "kimi_cli",
      "provider": "kimi_cli",
      "provider_paths": {
        "sessions_dir": "/home/you/.kimi-code/sessions",
        "config_path": "/home/you/.kimi-code/config.json"
      }
    }
  ]
}

sessions_dir selects a sessions directory. config_path selects the model fallback config. Either override can be omitted; without config_path, OpenUsage looks beside the selected sessions directory.

Metrics​

The provider walks the selected sessions directory for wire.jsonl files. Kimi CLI records contain message.type = StatusUpdate and snake_case token_usage fields. Kimi Code CLI records contain type = usage.record, camelCase usage fields, and an epoch-millisecond time. Only records with nonzero token usage count.

MetricSource fields
total_input_tokensinput_other or inputOther
total_output_tokensoutput
total_cache_readinput_cache_read or inputCacheRead
total_cache_writeinput_cache_creation or inputCacheCreation

The model comes from the record, then the selected config.json, then kimi-for-coding. Session IDs include both group and UUID, even when Kimi Code stores agent logs deeper. Each record's timestamp is converted to UTC for daily series and for sessions_today and sessions_7d.

The logs do not contain USD prices. Configure the Moonshot API provider separately for its API balance and quota.

Kimi Code subscription quota​

OpenUsage reads the existing access token from the newest JSON file in ~/.kimi-code/credentials/ and calls GET https://api.kimi.com/coding/v1/usages. The response supplies usage_five_hour, usage_monthly, and usage_monthly_code percentage gauges and reset times. Short-term request-rate limits are ignored because they are not subscription quota.

The credential file is read-only to OpenUsage. It never sends the refresh token, refreshes OAuth, or writes Kimi Code credentials. When the access token expires, quota disappears until Kimi Code refreshes its own token; local session stats continue working. Successful and failed quota reads are cached per account for one minute, and the daemon checks again after cache expiry when it next polls the provider.

Optional provider_paths overrides:

{
  "accounts": [
    {
      "id": "kimi_cli",
      "provider": "kimi_cli",
      "provider_paths": {
        "credentials_path": "/home/you/.kimi-code/credentials/account.json",
        "usage_api_base_url": "https://api.kimi.com/coding/v1"
      }
    }
  ]
}

credentials_path selects one Kimi Code credential file. A missing explicit path does not fall back to another account. usage_api_base_url overrides the coding API root, including its /coding/v1 prefix. There is no oauth_host setting because OpenUsage never refreshes tokens.

Troubleshooting​

  • No sessions: run a CLI session and check openusage detect. If both clients are installed, set sessions_dir explicitly to select Kimi Code.
  • Unexpected model name: check the record's model and the matching client's config.json; kimi-for-coding is the fallback.
  • No quota gauges: check the quota / quota_error diagnostics. An expired access token hides quota until Kimi Code refreshes it.
  • Missing tokens: malformed JSON lines are skipped. A single line larger than 1 MiB stops scanning that file.