Time and token tracking for Codex

Codex keeps every session on your machine, in ~/.codex/sessions. Inlinr reads them and turns them into time, lines written and token counts per project, next to your editor time and Claude Code.

Get it on GitHub

Set it up

1
Already use the Inlinr plugin for Claude Code? Nothing to install: it reads Codex sessions on the same machine. Otherwise, with Node 18 or later, download the script:
Terminal
```
curl -fsSL https://github.com/inlinrhq/inlinr-claude-code/raw/main/dist/index.js -o inlinr.js
```
2
Connect this machine, then open the link and approve with GitHub:
Terminal
```
node inlinr.js activate --editor codex
```
3
Have Codex send its sessions after each turn:
Terminal
```
node inlinr.js setup codex
```

What gets recorded

Time spent in each session, per project and branch
Files edited and lines added or removed by Codex
Input, output and cached tokens, and the model

Good to know

· Never your prompts, the assistant's replies or file contents.
· Tracking starts when you activate; past sessions are not uploaded.
· setup adds notify to ~/.codex/config.toml. Codex takes one notify program: if you have one, setup prints the command to call from it.
· No cost figure yet for OpenAI and Google models: Inlinr shows a cost only for prices it has checked.

Never file contents, prompts or replies. The full list of what is sent · Tracking Claude Code: terminal, desktop, IDE and cloud

Start tracking Codex

Free for solo use. Sign in with GitHub, install, and your first session shows up on the dashboard.

Install in VS Code

No card to start · no source code leaves your machine