TURN / SYNCTurn timeline
Move across duration, cost, token, context, complexity, and code-diff graphs together.
GUIDE OpenAI Codex observability
Aether reads Codex's native local rollouts and turns them into synchronized graphs, action summaries, agent traces, and per-request input attribution. No hooks, API keys, or cloud dashboard are required.

01 The operational gap
Codex can search, patch, run tools, spawn agents, and compact context across a single task. Aether reconstructs that path from local rollouts, preserving provider titles and project identity while exposing the operational signals behind the result.
02 What becomes visible
TURN / SYNCMove across duration, cost, token, context, complexity, and code-diff graphs together.
MODEL / USDUse maintained model pricing and provider token totals for transparent API-equivalent estimates.
ACTION / RESULTSee successful searches, patches, commands, compactions, and file changes by turn.
ROOT / BRANCHBreak each request into user prompt, retained context, tools, agents, memory, and provider runtime.
03 Local pipeline
Aether finds Codex sessions already stored on the machine.
Rollout records become sessions, turns, tool events, agents, and usage.
Live tailing keeps the selected Codex session current while it runs.
04 Practical questions
No. Run aether watch and installed providers are discovered automatically.
No. They are transparent API-equivalent estimates based on emitted token usage and maintained model pricing.
Yes. It uses provider-native session metadata and keeps nested agent work inside the parent session.
05 Start observing
brew trust --formula connectchiragg/tap/aetherbrew install connectchiragg/tap/aetheraether watch