Choose the source for your question.
| Source | What it answers | Where to start |
|---|---|---|
| Remaining allowance | What is available in a current window, with its reset time. | Account dashboard or /status |
| Official analytics | The history and breakdowns provided for the eligible plan, workspace and client. Organization access and personal desktop analytics have their own prerequisites. | Official analytics instructions |
| Local session logs | A local tool can summarize the logs it can read. Coverage depends on the computer, files and client; price-based cost estimates do not prove your subscription charge. | Inspect that tool’s source and collection requirements. |
| TokenVive history | Account-supplied daily tokens and message data on your devices. These are separate fields, not a reconstruction from remaining percent. | Read the field table below |
Daily tokens and model messages are separate.
| Field | Available meaning | Boundary |
|---|---|---|
| Daily tokens | A daily total across all models from the available account response. | No per-model token split or input/output/cache/reasoning split is supplied by this Codex history view. |
| Daily messages | Message counts for returned dates; available model counts can be shown separately. | A missing or incomplete model breakdown stays incomplete; it is not evidence that an unlisted model had zero use. |
| 7 / 30-day view | The selected date range for the chart. | Selecting 30 days does not guarantee 30 complete days of provider history. Recent days or one field can still be pending. |
| Update state | Read the successful update and the availability state for the field you are viewing. | A newer allowance query does not prove tokens or messages refreshed at the same moment. |
Check history in TokenVive.
- Connect Codex in Settings on iPhone. Complete the intended account’s official sign-in flow.
- Open AI data analysis and select the account. Choose the token or message view and the available date range. Keep the all-model token total distinct from the model-message selection.
- Read availability with the chart. Note returned dates, pending/incomplete states and the field’s successful update. Compare the same workspace and dates in another source.
Connections and refreshes require active TokenVive membership or remaining trial access. iOS 17 or later is required; paired Watch features require watchOS 10 or later. Sign-in and reconnection are completed on iPhone.
Why can two histories disagree?
- Coverage: account history, organization analytics and files on one computer may include different activity.
- Dates: compare the source’s date labels, time zone and whether the current day is complete.
- Units: a message is not a fixed number of tokens. Model-message counts cannot reconstruct model-token totals.
- Freshness: token and message responses can arrive independently. An unavailable date or failed refresh is not measured zero.
TokenVive’s Codex history does not provide a per-task/session ledger or prove a real subscription bill. For API charges, use the OpenAI Platform billing account. For official organization analytics, use the eligible workspace and its documented access.
Keep current allowance close to its reset.
Use the limits guide when deciding whether another task can run. A past token total cannot tell you exactly how many prompts remain. For a glanceable phone view, choose a supported account and window in a widget; the widget follows system update scheduling.
Sources and scope
Official history guidance was read November 12, 2026; related source comparisons were read through November 15. Account eligibility, returned dates and field availability determine the history you can see. TokenVive is an independent app.