codex - 💡(How to fix) Fix Add "service_tier" to JSONL token usage logs [1 participants]

TL;DR

Adding a service_tier field to the JSONL files, such as in the info object of the token_count event, would allow for accurate estimation of token usage and cost.

Guidance

• The current JSONL files lack a service_tier field, making it difficult to accurately estimate token usage and cost.
• Adding this field to the info object of the token_count event, as shown in the minimal useful shape example, would provide the necessary information.
• The service_tier information is already logged temporarily in other logs, but these logs are not stable enough to use.
• Community tools like ccusage and OpenUsage could benefit from this addition, as they currently provide inaccurate cost calculations due to the lack of service_tier information.

Example

{
  "type": "token_count",
  "info": {
    "last_token_usage": { "...": "..." },
    "total_token_usage": { "...": "..." },
    "service_tier": "priority"
  }
}

Notes

The exact implementation details of adding the service_tier field are not specified, and it is unclear what the possible values for this field would be (e.g., "priority", "normal", etc.).

Recommendation

Apply workaround: Add the service_tier field to the JSONL files to enable accurate estimation of token usage and cost. This would provide the necessary information for community tools to calculate costs accurately.