Codex keeps only your own history, on your own computer. A team lead who wants adoption numbers needs everyone's, without anyone's prompts. Usage Insights for Codex does it with files people export themselves and share inside the team. This lesson exports yours, builds the team view and saves a report.
Export your events
Load your sessions in Usage Insights for Codex and press Export in the bar. Fill in two fields first:
- Your pseudonymous id: any id, never your email or name.
- Team id: the team you belong to, such as
team_platform.
Then press Events. It saves a .jsonl file of events in the unified schema, for the range and project you chose: counts and times, and the names of models, tools, skills and project folders. No prompt, no answer and no thread name. If a folder name says more than you want to share, export one project at a time with the All projects menu.
Share the file inside your team however you already share files. It never passes through BENIBIX: the page has no server to send it to.
Load everyone's
One person presses Load data and picks every .jsonl at once. The person menu in the bar, which reads Me with one person's data, now lists the pseudonymous ids, and the Team view has everyone in it.
No files yet? Sample loads a made-up team of 26 people, enough for every chart.
Read the Team view
Team answers three questions:
- Are people using it? DAU / WAU / MAU against seats, Depth of use (light, regular, power), New & returning users and Adoption by team.
- Do they keep using it? Retention cohorts: people who started in the same week, and the share still active each week after.
- What comes out? Engineering output (lines, commits and pull requests, edit acceptance), Org skills & plugins and Connector coverage.
A team smaller than five people is hidden in the team charts, so no one can be singled out.
Read the catalog
Catalog is the definition of every number on every view: what it means, where Codex records it and the widget that shows it, then the Unified event schema with an example, the Event names and the Privacy rules. Use it when someone asks how a number was worked out, or to send events from another source in the same shape.
Save a report
Back in Export:
- Full report (.html): every view in one file that opens in any browser, offline.
- Full report (PDF): every view on landscape pages; choose Save as PDF in the print window.
- Summary: every number on every view, as
.json. - Daily table: date, prompts, sessions and tokens per day, as
.csvfor a spreadsheet or a BI tool.
The two full reports show your thread names under Recent work, so look through one before you pass it on.
That was the last lesson. You can now read every number the dashboard shows, explain where it comes from and build a team view without collecting anyone's prompts.