Bring back /cost command
Open 💬 3 comments Opened Apr 28, 2026 by maxencefrenette
💡 Likely answer: A maintainer (github-actions[bot], contributor)
responded on this thread — see the highlighted reply below.
What variant of Codex are you using?
App
What feature would you like to see?
With the switch to usage-based pricing for business plans and the release of 5.5, I find myself spending enough money that I have to start worrying a little bit about cost control. It is currently very hard to even know which threads I'm spending the most money on. Adding back the /cost command would be the easiest way to do so. Alternatively, the /status command could display credit usage of the current thread.
Additional information
_No response_
3 Comments
Potential duplicates detected. Please review them and close your issue if it is a duplicate.
Powered by Codex Action
This is different from #19869 , I want to be able to audit incurred cost in existing threads. The thing I am specifically running into is that with GPT-5.5, there is basically no limit in sight on the amount of useful work I can get it to do. However, I still need to evaluate wether this work was worth doing at all and do a rough cost/benefit gut-check, especially with the ability to spend double-digit dollars of usage in a single thread or even in a single turn sometimes.
/costis most useful if it can answer both "what did this thread cost?" and "why did it cost that much?"Minimum useful breakdown: per-thread total, per-turn rows, model, input/output/cache/reasoning tokens, tool-output size, subtask/background origin, pricing source, and whether the number is provider-reported or estimated. That makes high-cost GPT-5.5 threads auditable instead of just expensive in aggregate.
Generated with ax - https://github.com/Necmttn/ax