Codex

OAK reads Codex native hooks and rollout logs into the shared edit store. Conversation, review and usage readers use the same evidence in the terminal and both editors.

Setup

oak init --codex
oak doctor --fix
oak agent start --kind codex

Hook installation pre-trusts OAK’s exact hook commands. herdr owns the terminal; use its client to answer permissions, select models and resume conversations. Ordinary setup does not start a model turn.

Capture evidence

• Paired hooks record before/after file content and native tool identity when available.
• Rollout parsing supplies prompts, replies, reasoning, tool activity and usage.
• Snapshots reconcile disk changes over an interval without proving which process caused each write.
• Unknown before-state remains review-only. Undo refuses to invent prior content.

oak integrity --session <id> --json reports capture gaps and unsafe historical records. Completed native records remain readable after the terminal closes.

Conversation and usage

Observatory’s conversation detail and the editors’ Feed tab read the selected transcript. Explicit replies and review comments target a live herdr pane; unavailable or blocked targets preserve the draft. Permission prompts stay in the agent terminal.

Selected-session usage comes from that conversation. Account usage is measured on each machine for itself (SECURITY.md lists the account reads); missing quota or pricing remains unavailable. See Codex support for capture limits and historical validation evidence.