Skip to content
Lesson 2 of 633% of the course

Read your Codex activity

Use the Me view of Usage Insights for Codex to see when you work with Codex, what it built (lines, commits, pull requests and patches you kept), your projects and your habits.

Usage Insights for Codex courseBeginner5 steps3 min
Open Usage Insights for Codex
Nothing loads from YouTube until you press play. Then Google receives your IP address and may set its own storage. Narrated with an AI-generated voice. Privacy

Prompts and tokens are what you put in. What matters is what came out: code you kept, commits and pull requests. The Me view of Usage Insights for Codex shows both. Load your sessions as in the first lesson, or press Sample, and read it from the heatmap down.

See when you work

Time-of-day pattern counts your prompts by weekday and hour, in your own time zone. Darker squares mean more prompts. A block in working hours is normal; late-night columns and weekend rows show up at once.

Darker means more prompts. Point at a square for the count.

Beside it, the Highlights card picks out a few lines for the range: your longest streak, your busiest day, your biggest session, your favourite skill and anything you used for the first time.

See what Codex built

What I produced turns activity into outcomes:

  • Lines of code: lines added and removed by Codex's patches.
  • Commits & PRs: git commit and gh pr create commands that exited without an error.
  • Edit acceptance rate: of the patches Codex proposed, how many were applied rather than declined.
  • Web searches: searches Codex ran for you.
  • Languages & file types: lines changed per language, from the files Codex patched.
Outcomes, not volume.

Look at projects and branches

Projects ranks the folders you worked in, with the git branches the sessions started on under it. Recent work lists your last ten sessions with their project, surface, prompts and tool calls.

The All projects menu in the bar above the view narrows every number on every view to one project. Use it to see what Codex did for one repository.

Read your habits

Habits & efficiency shows how you and Codex work together:

  • Tool calls per prompt and Longest run: how much Codex did on its own between two of your prompts.
  • Tokens per session and Tokens per commit: what a session and an outcome take.
  • Outside working hours: the share of prompts before 8:00, from 19:00 or at weekends.
  • Interruptions: how often you stopped Codex mid-turn.
Point at any label for how its number is worked out.

Lower down, Session length shows how long sessions ran and Codex versions which versions they ran on, handy when something changed after an update.

Copy your recap

At the bottom, Period recap puts the range in a few numbers. Copy recap copies a one-line summary with numbers only: no titles, projects or text. Share it if you want to.

Next: track your Codex usage limits, tokens and models, and how close you came to the 5-hour and weekly windows.

Your progress stays in this browser only.
Contact