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

How to find the exact step that broke an agent run with Orca Replay

Replay a failed coding agent run offline and see which tool call changed a file or skipped a failing check.

Authorization notice. Orca Replay is dual-use. Only use it on software, sites and systems you own or have explicit permission to test.

Who it is forA developer whose coding agent reported success, but the tests still fail or a file was changed wrongly.

The problemThe agent's exit code and its transcript do not show which action caused the damage or whether a check actually failed.

The outcomeA step-by-step timeline and causal graph that shows which tool call changed which file and which check failed, with the replay blocked from calling any model.

What you need first

  • Node.js and npm, to install the orcareplay package
  • A coding agent installed locally, such as Claude Code or Codex CLI, to record a run
  • A model API key and network access for recording and for live forked turns
  • A terminal with permission to install a global npm package

Steps

  1. Run npm i -g orcareplay to install the package that provides the orca command.
  2. Run orca record claude and use your agent as normal until the run finishes.
  3. Run orca show last to read the ordered timeline of model turns, tool calls, file changes and shell results.
  4. Run orca graph last to see which events produced which, and check whether each link is recorded or inferred.
  5. Run orca replay last to repeat the run with no network and no tokens spent, and confirm the same result.

Prompt for your agent

Use the OrcaReplay repo (Continuum-AI-Corp/OrcaReplay) to inspect the most recent failed run on this machine by running `orca show last` and `orca graph last`. Report the sequence number of the tool call that changed <target file> and the sequence number of any shell check that exited non-zero. Verify that `orca replay last` prints the run again with no model called.

Caveat. Replay is not a sandbox, and a tool call that opens its own socket, such as a shell command running curl, is outside the no-network guarantee.

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