Codex
Record OpenAI Codex sessions from every endpoint.
What it records. Every conversation a person has with the Codex CLI on the endpoint: prompts, replies, the model used, tool calls, and token counts.
How. The extension registers with Codex’s system requirements file so Codex calls it after each turn. It reads the turn from Codex’s session file and passes it to the scanner.
Before you begin
- You have the Admin role.
- Codex is installed on at least one enrolled endpoint, so you can confirm a session arrives.
Check it is running
It is on when your organization is created, so there is nothing to switch on.
Open Hub
Click Hub at the bottom of the left menu. Under AI Tools, the Codex card reads Enabled.
Check
The next Codex conversation appears on the Sessions page with Codex as the source, within 15 minutes of the endpoint’s next scan.
On the endpoint
sudo surface extension list shows codex as installed. sudo surface logs --extension codex shows its activity.
Turn it off
Click the Codex card in Hub and turn Enabled off. You see “Codex disabled” and endpoints remove the hook on their next scan. Turn it back on to record Codex once more.
Next steps
- Session Trace to open a Session Trace or Conversation
- AI Usage for cost and top adopters
- Claude Code to record another tool