Restore rate limit info to --json format
Resolved 💬 5 comments Opened Oct 3, 2025 by dimfeld Closed Dec 18, 2025
💡 Likely answer: A maintainer (github-actions[bot], contributor)
responded on this thread — see the highlighted reply below.
What feature would you like to see?
The old JSON format printed out rate limit information periodically, but the new format does not. It would be great to have this back.
It looks like the new format also only prints the token usage at the end; would be nice to have it more often.
Are you interested in implementing this feature?
_No response_
Additional information
_No response_
5 Comments
Potential duplicates detected:
Powered by Codex Action
Can you describe your use case for periodic token usage?
Nothing particular, just nice to see it as the task runs. I'm not actually depending on it at all.
I have a use case. I am doing some modeling/testing to try to be more token-efficient (well, make codex be..) and actually just started some work using the json output + token outputs to find where the hot spots are and such. Plus it's just nice to see/know while going deep on this journey.
I for one would like to see it back. Perhaps allow a customized json shape so folks can adjust the returned data to include/exclude some properties or something?
This feature request hasn't received any upvotes or additional posts in over two months, so I'm going to close it out.