Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

[Bug]: Using a reset credit from the pooled usage bar shows no progress while it runs

Open Beginner friendly
  • Is something wrong?
#17,449 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
72/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Active
Tech stack
react, typescript
Domain
frontend

Research direction

Start in UsageLimitsPooled.tsx at RedeemableSegmentPopup, where onRedeem calls closePopover() before the confirm dialog opens, then in UsageLimits.tsx at useResetCredit().redeem, where the dialog closes before consumeResetCredit is awaited. The status span outside the popover renders only redeem.status. Done means a pending line such as "Using reset credit…" shows in that slot while redeem.busy is true, and it clears when the result arrives.

Written by the indexing model from the issue text.

Description

[!NOTE]
Drafted by Claude Opus 5.5 in Claude Code (via T3 Code); reviewed and posted by @jieyuexing.

Before submitting
  • I searched existing issues and did not find a duplicate.
  • I included enough detail to reproduce or investigate the problem.
Area

apps/web

Steps to reproduce
  1. Have a Codex account with a reset credit available.
  2. Open Usage → Limits and click the redeemable segment of the pooled bar.
  3. Click the reset action in the popover, then confirm in the dialog.
Expected behavior

Something on screen shows the reset is in progress until the result appears, like the spinning refresh button on the same page.

Actual behavior

Nothing changes for several seconds. Then the result text appears.

RedeemableSegmentPopup closes the popover before opening the confirm dialog (UsageLimitsPooled.tsx, onRedeem → closePopover()), and useResetCredit().redeem closes the dialog before awaiting consumeResetCredit (UsageLimits.tsx). The only pending state, the disabled "Using…" button, lives inside the popover that is already closed. The status span outside the popover renders only redeem.status, which is set after the request settles, so busy is never visible on this path.

The wait itself is expected: for Codex the server spawns an app-server to consume the credit, then runs a full snapshot.refresh (another app-server, account/skills/models/rate limits) before replying. That makes the missing feedback noticeable.

Impact

Minor bug or occasional failure

Version or commit

v0.0.46-nightly.20261008.2833 (same code on main as of 2026-10-09)

Environment

macOS desktop app, Codex provider

Workaround

None. Wait for the result text.

Possible fix

Render a pending line in the same status slot outside the popover while redeem.busy is true (for example the account name plus "Using reset credit…"), so the pooled path shows the same feedback the per-account card already has.

Dominant language
TypeScript
Stars
24.8k
Forks
6.4k
Avg merge
10h 41m
Merged PRs (30d)
352

Getting set up

Open in Codespaces

Starts the project's dev container in your browser, under your own GitHub account.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from pingdotgg/t3code

All issues in pingdotgg/t3code

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.