Did the reset reach your account?
A public reset announcement and a private account change are related, but they are not the same observation. ResetPulse keeps both visible so a useful signal does not become a false guarantee.
Open the live event-level form, choose what your own Codex surface showed, and share only a fixed-choice anonymous result. No login or account identifier is required.
Report your outcome now -> · Compare plan and limit-window reports · Parse a private snapshot locally
Read the public signal
Start with the latest confirmed event, its source time, first-observed time, scope, and evidence receipt. A public event tells you what was observed in the published scope.
Check your own surface
Compare the exact limit label, plan or workspace context, remaining allowance, and expiry label in your Codex UI or CLI. Do not treat another person's screenshot as your account state.
Report against the event
Use the fixed-choice community form on the live timeline. Each new report is tied to the latest public signal and accepts only a UTC time, surface, scope, and result; reports stay unverified, appear only as an aggregate after the minimum sample, and can produce a copyable English summary.
Keep mismatches visible
A reset-leaning public signal and a not-reset account report can both be true during eligibility, rollout, caching, or banked-reset differences. The correct label is mixed or unknown until the evidence supports more.
What the community sample means
The live timeline and each evidence receipt can show thresholded counts for anonymous fixed-choice reports tied to that public event. The Rollout Lens can additionally group reports by broad plan/workspace type and limit window, but only segments with at least three reports are shown. Those counts are account or plan observations, not independent confirmation of the public event. A report can be useful for detecting rollout mismatches, but it cannot identify a person, prove eligibility, or replace the account's own usage surface.
Why this is a product feature
Many trackers answer only “did a public signal appear?” ResetPulse adds the second question: “what did users actually observe?” It exposes the boundary, preserves UTC timing, and keeps unverified outcomes separate from the confirmed public timeline.
Use the live evidence
Open the live timeline to see the current public signal, read the data-source boundaries, or inspect the aggregate observation API. ResetPulse never asks for a Codex password, session, or private usage credential.