Show Copilot calendar-month pace under the premium row#690
Show Copilot calendar-month pace under the premium row#690coygeek wants to merge 2 commits intosteipete:mainfrom
Conversation
Derive Copilot reset windows from the existing assigned/reset dates so the shared pace UI can show whether chat usage is ahead or behind schedule. Co-authored-by: factory-droid[bot] <138933559+factory-droid[bot]@users.noreply.github.com>
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 5e8992b3a4
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| guard let assignedAt = Self.parseQuotaDate(self.assignedDate), | ||
| let resetsAt = Self.parseQuotaDate(self.quotaResetDate), |
There was a problem hiding this comment.
The new quotaWindow logic requires both assigned_date and quota_reset_date, so it returns nil whenever either key is missing. That breaks the new pace/reset support for responses that are still valid via the existing free-tier path (monthly_quotas + limited_user_quotas) but do not include those two fields, because CopilotUsageFetcher will keep emitting windows without resetsAt/windowMinutes. In that scenario the Copilot menu never shows pace or reset timing despite this feature being enabled for .copilot.
Useful? React with 👍 / 👎.
coygeek
changed the title
coygeek
changed the title
coygeek
changed the title
Derive Copilot premium-request pacing from the calendar month ending at quota_reset_date instead of the assigned_date window. Keep Copilot on a single visible row and add regression coverage for the corrected monthly reserve math.
1 participant
Summary
Premiumrow with pace text underneathquota_reset_dateassigned_date -> quota_reset_datefor premium-request pace calculationsin deficit/in reservewording for the Copilot pace lineCloses #689
Root cause
A live
/copilot_internal/userresponse returned:assigned_date:2026-03-22T16:03:34-07:00quota_reset_date:2026-05-01premium_interactions.entitlement:1500premium_interactions.remaining:1139premium_interactions.percent_remaining:75.9GitHub's premium-request analytics are calendar-month based, but CodexBar was previously interpreting that payload as a single Mar 22 -> May 1 quota window. That made Copilot reserve/deficit text too optimistic.
This change treats Copilot premium pacing as the current calendar month ending at
quota_reset_date, which matches GitHub's own analytics page.Validation
gh api -H "Accept: application/json" -H "Editor-Version: vscode/1.96.2" -H "Editor-Plugin-Version: copilot-chat/0.26.7" -H "User-Agent: GitHubCopilotChat/0.26.7" -H "X-Github-Api-Version: 2025-04-01" /copilot_internal/user --jq '{copilot_plan, assigned_date, quota_reset_date, monthly_quotas, limited_user_quotas, quota_snapshots}'swift test --filter CopilotUsageModelsTestsswift test --filter UsagePaceTextTestsswift test --filter CodexPresentationCharacterizationTestspnpm check./Scripts/compile_and_run.shNotes
24% usedand9% in reserve, which aligns with the calendar-month premium-request window.