Direct answer
A Codex usage dashboard shows tokens burned, active days, model usage, and activity history from local Codex session metadata. Codextime uploads token counts, model names, timestamps, and optional labels. It does not upload prompts, responses, source code, or secrets.
npx codextime-tracker@latest <userId>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 usage dashboard
- codex usage
- codex usage check
- what data does codextime upload
What the dashboard shows
Codextime focuses on usage signals that help repeat Codex users understand their own activity without turning the product into a billing system.
- Total tokens burned
- Daily and weekly activity
- Model usage mix
- Activity heatmap
- Public leaderboard position when enabled
How usage reaches the dashboard
Run the tracker from the machine where Codex stores local session logs. The command reads usage metadata, filters already-uploaded rows, and sends the new token totals to Codextime.
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 show my Codex usage history?
Yes. Codextime can show usage history after the tracker uploads token counts, model names, and timestamps from local Codex sessions.
Does Codextime upload prompt or response text?
No. Codextime is designed around usage metadata. Prompts, responses, source code, and secrets are never uploaded.
Can I use Codextime without public ranking?
Yes. Leaderboard visibility is separate from private usage tracking, so the dashboard can remain a personal usage view.
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.