Weekly quota display is ambiguous in VS Code extension
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 65/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Quiet
- Tech stack
- vscode
- Domain
- developer-experience, frontend
Research direction
Start in the VS Code extension's Work Locally menu and inspect the Usage Remaining UI and its tooltip. Reproduce the display with the reported Pro-plan context, identify what 10:37 represents, and verify that the percentage and time are explicitly labeled in both places.
Written by the indexing model from the issue text.
Description
What version of the IDE extension are you using?
26.527.31454
What subscription do you have?
Pro
Which IDE are you using?
VS Code
What platform is your computer?
Darwin 24.6.0 arm64 arm
What issue are you seeing?
What issue are you seeing?
The Usage Remaining UI shows:
Weekly 13% 10:37
There is no label or explanation for what 10:37 means.
Why this is confusing
It is unclear whether 10:37 represents:
- a countdown
- time remaining until reset
- a reset time of day
- a duration
- a local time or UTC time
The tooltip repeats the same values and does not provide clarification.
Observed behavior
- The percentage changes over time.
- The
10:37value remained unchanged for more than 15 hours. - I am on the Pro plan.
- Latest VS Code extension version.
What steps can reproduce the bug?
Open the Usage Remaining menu item in the Work Locally menu
What is the expected behavior?
The UI should explicitly state something like:
- "13% remaining — resets at 10:37 AM NZST"
- "13% remaining — 10h 37m until reset"
or otherwise explain the meaning of the time value.
Additional information
No response
- Dominant language
- Rust
- Stars
- 125k
- Forks
- 19.5k
- Avg merge
- 1m
- Merged PRs (30d)
- 1k
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from openai/codex
-
enhancement remote
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
bug CLI windows-os
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
macOS sandbox blocks hw.optional.arm64 sysctl, causing Flutter to misdetect Apple Silicon as x64 Openbug CLI sandbox
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
bug CLI TUI
Difficulty 2/5 1-3 hours Newbie friendliness 90/100
-
CLI config enhancement skills
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Eynzof/Hermes-CN-Desktop#610 ·
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
gitbutlerapp/gitbutler#15998 · 1 comment ·
-
bug triage:deciding
Difficulty 1/5 Under an hour Newbie friendliness 88/100
open-telemetry/otel-arrow#4132 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100