Skip to content

revert: restore 5-hour quota window (rollback safety net)#138

Draft
lidge-jun wants to merge 13 commits into
devfrom
codex/restore-five-hour-quota-window
Draft

revert: restore 5-hour quota window (rollback safety net)#138
lidge-jun wants to merge 13 commits into
devfrom
codex/restore-five-hour-quota-window

Conversation

@lidge-jun

Copy link
Copy Markdown
Owner

원복용 안전망 PR

GPT 요금제가 다시 5h 롤링 윈도우를 도입할 경우를 대비한 revert PR입니다.

언제 머지하나요?

  • OpenAI가 5h 한도를 다시 활성화했을 때
  • 그 전까지는 draft로 대기

무엇을 복원하나요?

  • StoredAccountQuotafiveHourPercent / fiveHourResetAt 필드
  • updateAccountQuota 시그니처에 fiveHour / fiveHourResetAt 파라미터
  • computeCodexUsageScore에서 fiveHourPercent 포함한 max 계산
  • x-codex-primary-used-percent 헤더 추출
  • WHAM primary_windowfiveHourPercent 매핑
  • GUI QuotaBars 5h 바 표시
  • i18n codexAuth.fiveHour
  • 관련 테스트 17개 파일

Reverts

  • 7fe556c7 refactor: remove 5-hour quota window from GPT plans (weekly-only)

lidge-jun added 13 commits July 16, 2026 14:38
…diff-level decade docs, 6-round audit synthesis (260716_grok_build_hardening)
…e Grok wire message with reasoning_content, signed ocxr1 siblings preserved separately, boundary clears (devlog 260716_grok_build_hardening/010)
…— re-read ~/.grok/auth.json before refresh, later-expiresAt adoption with zero IdP calls, detach to oauth on refresh (devlog 260716_grok_build_hardening/020)
…ck across IdP exchange, global store-write lock + async mutation funnel, generation-guarded persist, bounded token retry (devlog 260716_grok_build_hardening/030)
…quests — generation-checked singleflight refresh, fresh transport re-resolution, single replay (devlog 260716_grok_build_hardening/040)
…id, stable session/conv affinity, compatibility profile, executor-preserving header timeout (devlog 260716_grok_build_hardening/050)
All GPT plans have migrated from a 2-week 5-hour rolling window to
weekly-only rate limits. This removes the fiveHourPercent/fiveHourResetAt
fields from the quota data model, auto-switch scoring, header extraction,
GUI display, and all related tests.

The Anthropic/Claude provider retains its 5h window but now stores it as
a customWindow (label: "5h") instead of a top-level fiveHourPercent field.

Changes:
- StoredAccountQuota: drop fiveHourPercent, fiveHourResetAt
- updateAccountQuota: remove fiveHour/fiveHourResetAt params
- computeCodexUsageScore: score from weekly + monthly only
- responses.ts: stop reading x-codex-primary-used-percent header
- parseUsageQuota: ignore WHAM primary_window for GPT plans
- providers/quota.ts: Claude 5h → customWindow, drop fiveHour fields
- GUI: remove 5h bar from QuotaBars, i18n keys, AccountQuota type
- All 6 affected test suites updated (129 tests pass)
…d icon

- AddCodexAccountModal: remove window.open + popupRef (popup-blocked
  after await in Codex in-app browser, causing '링크 가기' prompt)
- AddProviderModal: remove redundant window.open (server already opens)
- auth-api: add server-side openUrl for /api/codex-auth/login (matches
  existing /api/oauth/login pattern in management-api.ts)
- Providers: fix unsized IconExternal in .link-btn (was rendering at
  browser-default SVG size), add copy-link button to OAuth login hint
- styles.css: add .link-btn svg size constraint (14×14)
- i18n: add prov.copyLink/prov.linkCopied in en/ko/de/zh
The upstream WHAM API and x-codex-primary headers still carry quota data
through primary_window, but it now represents the weekly limit (was 5h).
Prefer primary over secondary for weekly, with secondary as fallback.
…nly)"

This reverts commit 7fe556c, reversing
changes made to a85dd4b.
@lidge-jun
lidge-jun force-pushed the codex/restore-five-hour-quota-window branch from 86ddec2 to 7b8cae8 Compare July 16, 2026 12:30
Wibias added a commit to Wibias/opencodex that referenced this pull request Jul 16, 2026
Preserve five-hour quota UI pending lidge-jun#138; match Edit JSON actions to workspace link-style chrome.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant