DEDUPED Hot AI repos, turned into use cases Get 5 a day

How to locate failed and slow tool calls in past Codex runs with Codex Trajectory

Search and filter earlier task history to find failing or slow tool calls and inspect them.

Credentials. Choosing Load full details exposes bounded tool inputs and outputs to the active conversation, so confirm before sharing them.

Who it is forAn engineer debugging a Codex run that stalled or failed and who needs the exact event where it went wrong.

The problemA long task history mixes messages, tool calls, and compaction events, so the failing step is hard to find by reading the raw log.

The outcomeThe matching event selected in the event ledger, with its duration and execution status visible in the inspector.

What you need first

  • Codex installed on macOS, Linux, or Windows
  • uv installed (https://docs.astral.sh/uv/getting-started/installation/)
  • Local Codex task logs on the same device

Steps

  1. Run codex plugin marketplace add icesixgod/codex-trajectory
  2. Run codex plugin add codex-trajectory@icesixgod
  3. Open Codex Trajectory from the task's right panel.
  4. Click Load earlier records to browse history, including compressed and paginated logs.
  5. Use search and event filters to find the record, then select it to inspect it.

Prompt for your agent

Using the icesixgod/codex-trajectory repo, search the history of the Codex task <sessionId> for failed or slow tool calls and list the matching events with their durations and status. Verify that each listed event has a status and that zero and sub-millisecond durations are not reported as failures.

Caveat. Steps are approximate, and reasoning summaries appear only when they were saved in the log.

Share: X LinkedIn Hacker News Email Copy link

Disclaimer

Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page