feat(cli): show Codex usage - #11612
Closed
lambertjosh wants to merge 36 commits into
Closed
Conversation
…o feat/codex-usage-visibility
Contributor
Author
|
Codex on team plan: Note was not able to test an individual plan yet, since I don't have one. |
…ility # Conflicts: # packages/kilo-docs/public/img/screenshot-tests/kilo-vscode/visual-regression/profile/logged-in-chromium-linux.png # packages/kilo-docs/public/img/screenshot-tests/kilo-vscode/visual-regression/profile/logged-in-personal-chromium-linux.png # packages/opencode/src/kilocode/provider-usage/index.ts
…ility # Conflicts: # packages/kilo-docs/public/img/screenshot-tests/kilo-vscode/visual-regression/profile/empty-usage-chromium-linux.png # packages/kilo-docs/public/img/screenshot-tests/kilo-vscode/visual-regression/profile/organization-context-chromium-linux.png # packages/kilo-docs/public/img/screenshot-tests/kilo-vscode/visual-regression/profile/stale-and-unavailable-chromium-linux.png
…o feat/codex-usage-visibility
…ility # Conflicts: # packages/kilo-docs/public/img/screenshot-tests/kilo-vscode/visual-regression/profile/stale-and-unavailable-chromium-linux.png
…ility # Conflicts: # packages/kilo-docs/public/img/screenshot-tests/kilo-vscode/visual-regression/profile/empty-usage-chromium-linux.png # packages/kilo-docs/public/img/screenshot-tests/kilo-vscode/visual-regression/profile/logged-in-chromium-linux.png # packages/kilo-docs/public/img/screenshot-tests/kilo-vscode/visual-regression/profile/logged-in-personal-chromium-linux.png # packages/kilo-docs/public/img/screenshot-tests/kilo-vscode/visual-regression/profile/scrollable-usage-chromium-linux.png # packages/kilo-docs/public/img/screenshot-tests/kilo-vscode/visual-regression/profile/stale-and-unavailable-chromium-linux.png
Contributor
|
To stay organized pull requests are automatically closed after 30 days of inactivity. If the pull request is still relevant please reopen it or create a fresh new one. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What changed
Add a Codex adapter to the Provider Usage Center using the already-resolved ChatGPT OAuth transport from the OpenAI provider. It queries the ChatGPT usage backend, decodes quota windows lossily so malformed siblings do not hide valid data, and normalizes five-hour, weekly, named additional, purchased-credit, and spend-control state into the shared contract.
ChatGPT plans that authenticate successfully but do not report detailed usage windows render an explicit empty-details message instead of implying an error. ChatGPT OAuth is labeled DIRECT because the credential is used by the local provider integration; the plan subtitle continues to identify ChatGPT Team or the returned plan type. The CLI binary smoke-test environment is isolated from local home-directory Kilo config so packaging remains deterministic.
Why
Codex users should see current ChatGPT quota and credit state alongside Kilo and MiniMax sources without duplicating OAuth handling or exposing access tokens and account identifiers. Some plans may return plan identity without detailed quota fields.
Stack
This draft is stacked on #11611 and should be reviewed after the base Provider Usage Center PR.