Codex Trajectory plugin
A Codex plugin that turns local task logs into a timeline with token counts, tool timing and estimated cost for every step.
- 253 ★ on the repository
- Last commit
- MIT
Extended access
Why this level
- The plugin reads local Codex task logs that can contain tool inputs and outputs.
- Full details return through Codex and may enter the conversation; safe summary mode limits this.
Install
- Works in
Manual install
codex plugin marketplace add icesixgod/codex-trajectoryThe first command of the Install section. Then `codex plugin add codex-trajectory@icesixgod`; `uv` is required.
Access and checks
How we reviewExtended accessThe tool runs code or makes network calls and only reads external data.
- The plugin reads local Codex task logs that can contain tool inputs and outputs.
- Full details return through Codex and may enter the conversation; safe summary mode limits this.
This is third-party code. Review the repository files before installing.
What it does
Codex Trajectory, a plugin for Codex desktop, reads local task logs and builds a searchable event timeline. The viewer shows messages, saved reasoning summaries, tool calls, failures, subagent activity and context compaction. The plugin counts tool durations and estimated model time, tokens, cache usage and estimated cost including all subagents. Logs are read locally and stay unchanged. Safe summary mode hides tool inputs and outputs, and full details open after confirmation.
Who it is for. Codex desktop developers breaking down where time and tokens went in a long task.
Good fit when
- A long Codex task ran slower than expected and the slowest tool must be found.
- Token and cache usage for a task is checked together with its subagents.
- An agent failed and events with errors are reviewed step by step.
- New task events are followed in a live window.
Not a fit when
- You need sessions from Claude Code or other agents: the plugin reads Codex logs only.
- You need exact subscription cost: estimates use bundled API prices.
- The log exceeds 512 MiB and raising the read limit is unwanted.
Example request
Show the safe trajectory summary for this Codex task and name the slowest tool.Limitations
Codex desktop and `uv` are required. Cost is an estimate rather than a subscription charge, and local quota samples may lag. A log above 512 MiB is read after the limit is raised in the error panel. After updating, fully quit and reopen Codex. Data returned through Codex may enter the active conversation. The plugin supports macOS, Linux and Windows; the viewer does not control the task and only shows its data.
How to disable. Remove the plugin from Codex and refresh the marketplace. Clean the private derived task index the plugin keeps separately.
FAQ
Which MCP tools are available?
The documentation describes four user-facing tools. The main ones are `show_codex_trajectory`, `list_codex_sessions` and `get_codex_project_timing`.
How do I open the viewer?
In the task's right panel choose "+", then "More tools…", "Plugins and MCPs" and "Codex Trajectory". Or ask Codex to call `show_codex_trajectory`.
What if a log is too large?
Raise "Read limit (GB)" in the error panel and click "Enable and retry". The limit applies only to that task in the current panel.
Does the plugin change source logs?
No. Logs are read locally and stay unchanged; `list_codex_sessions` updates only a private derived index.
Is a separate server needed?
No. The plugin launches the MCP server through `uv`, and the viewer runs inside Codex desktop.
Discussion
No questions or reviews yet.
Related
PluginsCodex Trace reads local Codex CLI logs and shows turns, tool calls and token usage in a desktop window or in the browser.
A Codex plugin for measured experiments in a repo: a baseline metric, tested small changes, and a patch with evidence
Codex Settings skills
Codex CLI Skills & Profiles
A Codex CLI plugin with twelve skills: deep research, pull request review, image generation and session handoff
OpenAI's official plugin: Codex reviews of your changes and task delegation to Codex from inside a Claude Code session
A Codex plugin: 55 explicitly invoked skills and 23 poteto-mode playbooks for code tracing, TDD and review.
A Codex plugin adds development discipline, 29 skills, 31 hooks and multi-model subagents in one package.
Comparison with similar tools
Cards that share the main search query, and how they differ.
| Tool | Official | Repository stars | Main difference |
|---|---|---|---|
| Codex Trajectory (this card) | no | 253 | |
| claude-replay | no | 859 | replays Claude Code sessions; Codex Trajectory analyses Codex tasks by timing and tokens |
| ccusage | no | 19,425 | summarises token usage in reports; the plugin shows the events of a single task |
README in short
Timing excludes gaps between turns and counts overlapping tools once. Model time includes network and queueing waits.