Skip to content

Requests show zero duration/no first-output timing. Codex session usage

Quick fix

This issue remains open, with no confirmed user-side fix; missing request timing should remain unknown rather than display as 0.

Error output
Requests show zero duration/no first-output timing.

During local Codex rollout import in macOS CC Switch 3.20.4, `token_usage_record` may contain token counts while request duration and first-output time are `0` or `NULL`. This causes requests with unmeasured duration to display as `0.0s` in Usage Statistics, and includes requests with unknown durations in the Provider average denominator.

The issue also notes that Fast or GPT requests with input over 272K may still use Standard short-context pricing. TPS may also use the full request duration when the first-output window is unknown. The proposed handling is to restore timing only when local request-start telemetry can be matched clearly with rollout-completion events; unknown data and retries should remain unknown. The issue is still open, and a fix is being prepared.

  1. There is currently no issue-confirmed user-side action to fix this import metric problem; wait for a fix for the Codex session importer.

ToolCodex
Version3.20.4(受影响版本)
PlatformsmacOS

(No FAQ yet)

This is an unofficial community wiki with no affiliation to the cc-switch authors or the project itself. Its content is compiled from the project's public GitHub issues. This site distributes no software.