docs: explain Windows Codex quota network diagnostics

[lidge-jun]

Summary

• Explain the existing main-account quotaRefresh diagnostic, its fixed status vocabulary, optional HTTP code and omitted-field meaning.
• Show a PowerShell projection that prints only diagnostic fields, and distinguish the running service's proxy environment from the interactive shell.
• Document startup-only Windows static proxy discovery and add concise guidance in seven translated pages with a canonical English reference.
• [Bug]: Healthy ChatGPT Plus Codex login reports plan: null / quota: null and hides 5h/weekly usage #3644 remains FIELD_VALIDATION_PENDING: the latest reporter evidence is from 2.43.0 without the new diagnostic. This documentation does not claim to fix the underlying network incident or change retry, credentials, quota admission or proxy policy.
• Stack: depends on fix(responses): repair sparse terminal output for Grok Build #3756; merge bottom-up after final-head checks.

Verification

• Current head 72f20e4b0be5c27b9a65885b2e3a4dbd5b52539a includes the stored Pool recovery boundary repair and is awaiting its own hosted CI. Earlier green runs do not verify this head. No local tests, typecheck or build were run.

• Checked the current main-account fetch/snapshot/projector, proxy setup and actual account-list command against the documentation. Independent plan audit passed; final documentation review is in progress.

• Runtime and tests are unchanged. Hosted documentation CI runs asynchronously; existing quota/CLI/proxy coverage is retained for release verification.

• No local test suite, typecheck, build, live account probe or user-configuration change was performed.

Checklist

• Scope stays focused and avoids unrelated cleanup.
• Docs or release notes were updated when needed.
• Security-sensitive changes were reviewed for secrets, auth, and unsafe defaults.

Native stack #3759 was dissolved at the owner's explicit request. The PR head is preserved; integration continues bottom-up with ordinary PRs and admin merge after current-head CI.

Summary by CodeRabbit

• Documentation
  • Added Codex quota network diagnostics guidance to the server configuration reference.
  • Documented quotaRefresh statuses, optional HTTP status details, and null or omitted quota results.
  • Clarified proxy behavior, including service environment usage, Windows auto-detection limits, PAC/WPAD and SOCKS limitations, and runtime changes.
  • Added translated guidance in French, Japanese, Korean, Russian, Turkish, Simplified Chinese, and Traditional Chinese.

[github-actions]

✅ Deterministic PR hygiene checks passed.

[coderabbitai]

Caution

Review failed

The pull request is closed.

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: ASSERTIVE

Plan: Team

Run ID: 84dfc652-690f-45c6-9d96-3ef5b60dc1ae

📥 Commits

Reviewing files that changed from the base of the PR and between a4451e8 and 72f20e4.

📒 Files selected for processing (10)

• devlog/_plan/260906_release_244_followups/070_quota_proxy.md
• devlog/_plan/260906_release_244_followups/071_quota_proxy_outcome.md
• docs-site/src/content/docs/fr/reference/configuration/server.md
• docs-site/src/content/docs/ja/reference/configuration/server.md
• docs-site/src/content/docs/ko/reference/configuration/server.md
• docs-site/src/content/docs/reference/configuration/server.md
• docs-site/src/content/docs/ru/reference/configuration/server.md
• docs-site/src/content/docs/tr/reference/configuration/server.md
• docs-site/src/content/docs/zh-cn/reference/configuration/server.md
• docs-site/src/content/docs/zh-tw/reference/configuration/server.md

---

📝 Walkthrough

Walkthrough

This change documents Codex quota retrieval diagnostics and proxy behavior in the English server reference and seven translated references. It also records the Windows investigation outcome and confirms that no runtime behavior changes.

Changes

Codex quota network diagnostics

Layer / File(s)	Summary
Investigation outcome and documentation scope devlog/_plan/260906_release_244_followups/070_quota_proxy.md:18-46, devlog/_plan/260906_release_244_followups/071_quota_proxy_outcome.md:1-20	The plan records quotaRefresh semantics, the ocx account list openai --quota --refresh --json declaration, proxy behavior, unsupported transport cases, the open FIELD_VALIDATION_PENDING status, and the documentation-only test scope.
Canonical quota diagnostics reference docs-site/src/content/docs/reference/configuration/server.md:53-102	The English reference documents the optional quotaRefresh field, seven status values, httpStatus handling, the refresh command, service environment behavior, proxy resolution, and the Windows static WinINET limitation.
Translated quota diagnostics references docs-site/src/content/docs/fr/reference/configuration/server.md:261-264, docs-site/src/content/docs/ja/reference/configuration/server.md:170-173, docs-site/src/content/docs/ko/reference/configuration/server.md:170-173, docs-site/src/content/docs/ru/reference/configuration/server.md:218-221, docs-site/src/content/docs/tr/reference/configuration/server.md:291-294, docs-site/src/content/docs/zh-cn/reference/configuration/server.md:184-187, docs-site/src/content/docs/zh-tw/reference/configuration/server.md:204-207	Seven localized references add quota retrieval and proxy guidance. They describe service-environment use, "auto" startup behavior, unsupported PAC/WPAD and SOCKS-only cases, runtime proxy changes, and TUN diagnostic limits.

Estimated code review effort: 2 (Simple) | ~10 minutes

Suggested reviewers: luvs01

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch codex/release-244-quota-proxy-07c0

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[lidge-jun]

리뷰 · 우선순위 60 / 80

이 PR은 release-244 플랜의 070_quota_proxy 칸입니다. 런타임 수정이 아니라 문서만 바꿉니다. 베이스는 dev가 아니라 아직 draft인 #3756 브랜치 codex/release-244-grok-terminal-07c0입니다. 이슈 #3644는 ChatGPT Plus Codex 로그인이 plan: null / quota: null로 보이는 Windows 네트워크 경로 버그인데, 리포터 최신 증거는 여전히 2.43.0이고 #3693 진단이 들어간 빌드의 분류 A/B가 없습니다. 그래서 이 유닛은 사고를 “고쳤다”고 말하지 않고, 이미 dev에 있는 quotaRefresh 진단 계약과 서비스 프록시/proxy: "auto" 동작을 사용자 가이드로 풀어 씁니다. outcome 노트 071_quota_proxy_outcome.md도 FIELD_VALIDATION_PENDING과 #3644 open을 그대로 유지합니다.

영문 기준은 docs-site/src/content/docs/reference/configuration/server.md의 Codex quota network diagnostics 절입니다. 상태 일곱 개(ok / not_reported / http_error / timeout / network_error / invalid_response / internal_error)와 httpStatus는 http_error에만 붙는다는 설명이 현재 src/codex/quota-refresh-outcome.ts 타입·projectCodexQuotaRefreshOutcome과 맞습니다. CLI 예시도 실제 명령 ocx account list openai --quota --refresh --json이고, JSON 모양의 accounts 배열(src/cli/account.ts)과도 맞습니다. PowerShell은 quotaRefresh가 있는 행만 골라서 전체 계정 덤프를 공유하지 않게 합니다. 프록시 절은 “돌아가는 서비스 환경 ≠ 지금 터미널”, unset은 상속 유지, "auto"는 시작 시 Windows WinINET 정적 프록시만(src/lib/windows-system-proxy.ts / src/config.ts) 읽고 PAC/WPAD/SOCKS-only/핫체인지는 안 된다는 점을 짧게 말합니다. TUN 성공만으로 HTTP 프록시 경로를 증명하지 말라는 경고도 #3644 맥락에 맞습니다.

ko/ja/fr/ru/tr/zh-cn/zh-tw는 짧은 요약 + 영문 앵커 링크만 추가합니다. 런타임·재시도·자격증명·quota admission·프록시 기본값은 건드리지 않습니다. 호스트 docs CI는 비동기로 두고, 많은 런타임 잡은 skipping으로 보이며 본문은 기존 quota/CLI/proxy 회귀로 충분하다고 합니다. types/config 대분할과 무관합니다. 스택상 #3756 다음이라, 부모가 안 올라가면 이 docs PR만 dev에 단독 착지시키면 안 됩니다(내용은 docs-only라 충돌 위험은 낮지만 train 순서를 깨면 안 됩니다).

우선순위 60인 이유다. release-244 조사 칸을 닫아 운영자가 #3693 진단을 쓰게 만드는 데 필요하지만, #3644 자체를 고치지 않고 증거도 여전히 pending입니다. 코드 칸(#3756 72)보다 낮고, train 안에서는 다음 문서 칸으로 타당합니다.

경로 - docs-site/.../reference/configuration/server.md Codex quota network diagnostics(영문 기준)
경로 - docs-site ko|ja|fr|ru|tr|zh-cn|zh-tw/.../server.md 요약 링크
경로 - devlog/_plan/.../070_quota_proxy.md · 071_quota_proxy_outcome.md
경로/심볼 - 소스 대조 src/codex/quota-refresh-outcome.ts · src/codex/auth-api.ts · src/cli/account.ts · src/lib/windows-system-proxy.ts
경로/심볼 - 이슈 #3644 open / 진단 #3693 이미 머지 / 부모 #3756 draft 스택

메인테이너의 판단이 필요한 지점

• #3756 Ready·머지 직후에만 이 PR을 Ready/머지할지, 아니면 docs-only라 dev 직행으로 베이스를 바꿀지
• #3644를 이 docs 랜딩 후에도 open+FIELD_VALIDATION_PENDING으로 둘지(권장: 유지)
• 리포터에게 2.44/#3693 빌드로 TUN vs system-proxy 분류 비교를 다시 요청할 메시지 타이밍
• 번역 페이지를 영문 링크만으로 둘지, 표·PowerShell까지 로케일 복제할지

너의 추천
#3756이 랜딩한 뒤 이 PR을 Ready로 바꾸고 docs CI 초록이면 머지하세요. #3644는 닫지 마세요. 새 런타임 수정·라이브 계정 프로브 금지. 리포터 재요청은 #3693 포함 빌드(이상적으로 2.44) 기준으로만. types/config 이슈 아님. 다음 칸은 usage-source(080).

이 댓글은 grok-bot이 작성했습니다

[chatgpt-codex-connector]

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review	Status	Commit	Review trigger
📝 Code Review	✅ Completed 2026-09-06T10:12:57.768667Z	72f20e4	Draft marked ready

ℹ️ 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" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.