Fix Codex token usage summing for multiple chat requests #39
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Problem
Codex reports token usage on each chat request with entries like
[2025-08-13T04:38:03] tokens used: 32169and[2025-08-13T04:38:06] tokens used: 28828. The current logs parsing logic only kept the maximum value (32169) instead of summing them to get the total usage (60997).This resulted in underreported token usage for Codex workflows with multiple interactions.
Solution
Updated the
parseLogFilefunction inpkg/cli/logs.goto properly handle multiple Codex token usage entries by:extractCodexTokenUsage()to identify "tokens used: X" patternsExample
Before:
After:
Testing
TestParseLogFileWithMultipleCodexTokenEntriesto validate the summing behaviorThe fix is surgical and minimal, only affecting the specific case of multiple Codex "tokens used" entries while preserving all existing functionality.
Warning
Firewall rules blocked me from connecting to one or more addresses
I tried to connect to the following addresses, but was blocked by firewall rules:
api.contoso.com/tmp/go-build2654920358/b256/cli.test -test.testlogfile=/tmp/go-build2654920358/b256/testlog.txt -test.paniconexit0 -test.timeout=10m0s -test.v=true(dns block)/tmp/go-build217373110/b001/cli.test -test.testlogfile=/tmp/go-build217373110/b001/testlog.txt -test.paniconexit0 -test.timeout=10m0s -test.v=true(dns block)/tmp/go-build3082135891/b001/cli.test -test.testlogfile=/tmp/go-build3082135891/b001/testlog.txt -test.paniconexit0 -test.timeout=10m0s -test.v=true(dns block)If you need me to access, download, or install something from one of these locations, you can either:
💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.