# Codex reset-time proof reproduction

Environment: Linux web dev client, Chromium, 1440 by 1000 CSS pixels, dark theme, UTC; real Codex CLI 0.169.0 with a local synthetic Responses upstream. Each commit runs in a separate checkout with its own fresh T3 home. No production data or provider credentials are used.

1. Place stub.py beside deadline.json containing {"reset": FUTURE_UNIX_SECONDS}. Start python3 stub.py and keep its terminal running. It returns HTTP 429 usage_limit_reached without allowance snapshots until the deadline, then a successful Responses SSE reply.
2. Run prepare.py CHECKOUT CODEX_HOME before starting each app. For an explicit fresh T3 home, put the generated userdata/settings.json in that home's userdata directory and pass --home-dir HOME to the dev runner and --base-dir HOME to the CLI below.
3. Start each checkout using T3CODE_DEV_SEED=0 T3CODE_AUTO_BOOTSTRAP_PROJECT_FROM_CWD=0 TZ=UTC vp run dev. Add its synthetic project using node apps/server/src/bin.ts project add ./evidence-workspace --title 'Usage limit demo' --base-dir .t3 (or the explicit fresh home). Pair its web client using that server's startup pairing URL.
4. Set dark theme and 1440 by 1000 viewport. Close Thread details to keep host details out of captures. In the new GPT-6-Astra thread, send 'Say hello.'. Capture the stopped turn. Base displays Reset time unavailable; retry manually. Head displays the deadline, Resume at reset, and Snooze until reset. Codex's printed minute is rounded to the following minute by the fix.
5. On head, click Resume at reset, Snooze until reset, Wake now, then Cancel auto-resume. These controls are absent from the base's usage-limit banner.
6. On both sides, open Settings > Threads; enable Resume after usage limits and Snooze until limits reset. Open a new thread, close its details panel, and send the same 'Say hello.'. Do not send anything else. Base stays limited and unscheduled. Head automatically schedules recovery and snoozes the thread until its deadline.
7. Keep recording both clients through the reset. Head wakes itself and sends Continue where you left off, then renders Hello! The usage limit has reset. Base remains limited. Inspect failure payloads read-only; base resetAt is null, head resetAt is the future UTC deadline.

Final capture pass: API reset 2026-11-15 04:25:28 UTC; Codex text try again at 4:25 AM.; head resetAt 2026-11-15T04:26:00.000Z. Both databases started empty with the same synthetic project, then one manual-controls thread and one automatic-recovery thread. Every still was checked against a second screenshot more than 500 ms later; images were resized uniformly from 2x device pixels to 1440 by 1000 for sharing.

The scenario runner was not used because its replay provider bypasses Codex-specific parsing and cannot create a usage-limit stopped run (documented scenario exclusions).
