/goal completion should show token usage breakdown, not only combined usage

Open 💬 0 comments Opened Jun 13, 2026 by nelsonjchen

What variant of Codex are you using?

Codex CLI and Codex Desktop/App, using Goal mode (/goal)

What feature would you like to see?

Summary

/goal currently reports combined usage when a goal completes. I would like the goal completion message to also show a token usage breakdown.

For example, instead of only showing an effective/combined total, the completion receipt could include:

  • input tokens
  • cached input tokens
  • output tokens
  • reasoning output tokens
  • effective/combined usage

Why this matters

Goal mode is often used for long-running autonomous work. When a goal finishes, a single combined usage number is not enough to understand where the usage went.

A breakdown would help users tell whether a goal was expensive because of:

  • large input/context
  • poor prompt-cache reuse
  • high reasoning output
  • large final/output responses
  • repeated continuation turns
  • compaction or retry overhead

This would make /goal completion receipts much more useful for debugging unexpected usage and comparing long-running goal sessions.

Expected behavior

When a goal completes, Codex should show something like:

Goal complete

Usage:
- Effective usage: 1,234,567
- Input tokens: 900,000
- Cached input tokens: 7,500,000
- Output tokens: 120,000
- Reasoning output tokens: 45,000

Additional information

I searched for existing issues and found adjacent reports about usage visibility and goal token behavior, but not this exact request.

Related but not duplicate:

  • #25320: goal sessions can pin cached_input_tokens
  • #23794: Codex Desktop no longer shows visible context/token usage indicator
  • #14593: broader token burn / usage reporting discussion

This request is specifically about the /goal completion receipt showing a usage breakdown rather than only combined usage.

View original on GitHub ↗