Show user-side timing metrics between Codex turns

Open 💬 1 comment Opened May 23, 2026 by ferious68

What variant of Codex are you using?

Codex desktop app on Windows

What feature would you like to see?

Codex currently shows assistant/agent execution time, which is useful.

Feature request:
Add user-side timing metrics for each turn, such as:

  • Elapsed time from assistant completion to the user sending the next prompt
  • Active composing time from prompt-box focus / first edit to Send
  • Optional session summary comparing user wait/compose time vs agent execution time
  • Cumulative time spent composing follow-up or steering messages while Codex is still executing the previous request

Why:
-This would help users understand the rhythm of a Codex session, identify where time is spent, and make long collaborative coding sessions feel more measurable
-Helps users understand real project build time: total elapsed time, Codex execution time, and the user’s active prompting/steering time.

Privacy note:
Because typing/focus timing can feel sensitive, this should probably be local-only, opt-in, or clearly disclosed.

Additional information

_No response_

View original on GitHub ↗

This issue has 1 comment on GitHub. Read the full discussion on GitHub ↗