[FEATURE]: Add opt-in Codex OAuth cost estimates #46320

Activity

1. gh-ppathi commented on Oct 14, 2026

   

   gh-ppathi

   on Oct 14, 2026

   More actions

   +1 — would love to see this prioritized, especially for OpenAI Enterprise credit accounts.

   While flat personal subscriptions don't have per-token charges, OpenAI Enterprise accounts consume from a shared enterprise credits pool when using Codex/OpenAI OAuth. In the Codex CLI/app, an estimated cost of the credits used is displayed for each session, whereas OpenCode currently zeroes out draft.cost = [] in packages/core/src/plugin/provider/openai.ts and always displays $0.00.

   Having estimated costs (either opt-in or enabled for Enterprise/credit-backed accounts) makes it much easier to track and manage credit consumption in OpenCode.
2. opencodejr commented on Oct 28, 2026

   

   opencodejrBot

   on Oct 28, 2026

   More actions

   Thanks for the request, and for the earlier PR!

   You'd like an opt-in providers.openai.oauth_cost_estimates setting. When it's enabled, ChatGPT/Codex OAuth sessions would show a local, API-equivalent cost estimate based on catalog prices. By default (or with false) the cost would stay at zero, and the estimate would never be presented as a ChatGPT subscription charge.

   For context: the zero cost is deliberate right now. The OpenAI provider clears the catalog cost for Codex models when you're signed in with a ChatGPT account, because the subscription covers that usage. So this would be a new option rather than a bug fix. Maintainers will consider it.

   Related issues:

   • [FEATURE]: show optional estimated Codex token costs #35133: your earlier request for the same opt-in estimate. It was closed automatically for inactivity, not rejected.
   • tui: optional catalog-price estimate for providers that report $0 session cost #59861: a broader request for an optional catalog-price estimate in the TUI for any provider that reports $0, such as OpenCode Go.
   • feat(openai): add OAuth cost estimates #46324: your implementation PR for this issue, which was closed by the automated cleanup of old PRs.
3. major

   closed this as completedon Oct 28, 2026