Direct answer
Codextime can show Codex usage history from uploaded metadata, but it should not claim automatic access to private account limits, plan state, emails, or reset windows. Limit information needs explicit user-provided labels, supported snapshots, or visible metadata.
Uploaded vs never uploaded
| Token counts | Build usage totals, heatmaps, and token-burned views. |
|---|---|
| Model names | Show model mix and API-equivalent usage context. |
| Timestamps | Place usage on daily, weekly, and all-time timelines. |
| Optional account label | Separate seats or machines when the user chooses to label them. |
| Prompts | Conversation input is not needed for usage analytics. |
|---|---|
| Responses | Generated output text is not needed for token totals. |
| Source code | Project files stay on the user machine. |
| Secrets | Credentials and private environment data are outside the tracking scope. |
Tracker flow
- 1
Local usage metadata
Codex writes session usage metadata on the machine where the user runs Codex.
- 2
Tracker command
The user runs the Codextime npx command to scan usage metadata and skip already-synced rows.
- 3
Usage upload
Codextime receives token counts, model names, timestamps, and optional labels.
- 4
Dashboard and leaderboard
The app renders private usage views and optional public ranking from the uploaded metadata.
What this page can answer
- codex limits
- codex status
- codex plan
- can codextime detect accounts
What usage metadata can show
Usage metadata can show when Codex was used, which models appeared in sessions, and how token totals changed over time.
What limit snapshots require
Rate-limit or reset-window information should be treated as optional and explicit. If the tracker supports a limit snapshot flag, the UI should label it as captured data rather than inferred account access.
What Codextime should not claim
Codextime should not casually claim it reads a user account, email, subscription, or private limit state. Optional labels and snapshots must be presented as user-controlled metadata.
Privacy boundary
Usage metadata
Codextime uploads token counts, model names, timestamps, and optional labels used to build analytics views.
Never uploaded
Prompts, responses, source code, and secrets are not uploaded by the tracker.
FAQ
Can Codextime detect every Codex account I use?
Not reliably by itself. Multiple accounts should use explicit labels or supported snapshots so the dashboard can separate them safely.
Can Codextime show limit resets?
Only when limit reset information is explicitly captured or provided. The UI should not invent reset windows from token usage alone.
Can Codextime show Codex service status?
Codextime shows your uploaded usage history. It is not an official OpenAI service status page.
Source notes
- This page is based on Codextime product behavior and Google Trends query clusters saved under /Users/dodo/Downloads/ctime-queries.
- Codextime is independent and not affiliated with OpenAI.
- API-equivalent usage is educational context, not a bill or official OpenAI pricing statement.