Add OrcaReplay to coding (record a run, replay it offline)

[xizhuomengcontin]

Adds OrcaReplay to coding, following the four steps in CONTRIBUTING.md.

Disclosure: I maintain OrcaReplay. Apache-2.0, Node 20+, 248★.

Why it belongs in coding rather than a new category

The coding category already holds the agents themselves — Claude Code, Codex, Cline, goose, Pi — plus tooling around them (agent-skills, Taste-Skill). This is tooling of the second kind, and specifically the piece none of those agents ship: a way to run a past session again.

It records the agent's exchange with its model provider at the HTTP boundary, so the recording is the bytes the agent actually sent and received rather than a summary it wrote about itself. orca replay last runs that exchange again with no provider contacted and nothing spent; orca replay last --from 4 --model <other> replays the prefix from the recording and then continues on a different model, so the model is the only variable.

On the list's own subject: the practical use is turning a failed session into a fixed artifact you can iterate against, which is what makes "did this change help?" answerable for an agent rather than a matter of opinion.

Against the inclusion criteria

• Relevant — agent coding / agent infrastructure. Several coding entries (Claude Code, Codex, Cline, goose) are agents it records directly; goose and Claude Code have adapters and Claude Code is validated against a real bug fix.
• Active — commits this week.
• Open source — Apache-2.0. The on-disk trace format is specified separately under CC BY 4.0 (spec/orca-trace-v0.md), so a recording is readable without the CLI.
• Documented — README with install and usage; orca quickstart writes a small buggy project plus a recording and replays it, so the claim is checkable in one command.
• Traction — 248★, published on npm as orcareplay.

Not a cross-list entry — it is not a multi-agent framework.

Steps followed

node scripts/generate-readme.js   -> regenerated
node scripts/validate.js          -> Validated 120 projects across 10 categories / Validation passed.
node scripts/check-links.js       -> Results: 120 ok, 0 failures, 0 warnings

Diff is +13 −0 in data/projects.json and +1 −0 in the generated README — pure insertion, appended at the end of the coding group so the existing ordering is untouched.

What I am not claiming

• A matching replay is not a determinism result. It proves the recorded exchange reproduces, not that the agent is deterministic or that a fresh run would fail the same way.
• Replay blocks model-provider egress only. It is not a sandbox — recorded tool calls still execute for real.
• The default adapter does not capture every call; embedding calls, for one, are not captured.

🤖 Generated with Claude Code

---

Note

Low Risk
Documentation-only catalog insertions in data/projects.json and generated README; no application or runtime code changes.

Overview
Adds OrcaReplay (Continuum-AI-Corp/OrcaReplay) to the awesome list under the coding category via a new data/projects.json entry (description, maintainer, tags record-replay / observability / cli, 248 stars).

The Agent Coding and Software Engineering section in README.md gains one autogenerated bullet describing record/replay of agent–model HTTP traffic, offline replay without calling a provider, and optional fork-from-step onto another model.

^{Reviewed by Cursor Bugbot for commit f0808de. Bugbot is set up for automated code reviews on this repo. Configure here.}

[autogame-17]

Reviewed current head f0808deb762d2f8bf4cc0eeaffbf5b9adae4d797, including the canonical repository, license and replay implementation. The coding-tool scope is appropriate; please tighten one factual claim before inclusion.

data/projects.json:1543 and generated README.md:156: “replay can fork from any step” should say that it forks from available derived checkpoints. At pinned upstream 6af80889:

• deriveCheckpoints requires both a complete conversation prefix and a filesystem snapshot.
• The fork command rejects runs without checkpoints and snaps a non-checkpoint --from sequence back to the nearest prior checkpoint, emitting fork.snapped.

A reader comparing models from a particular event can therefore start from an earlier state, or find that the run cannot fork. “Replay can fork from available checkpoints onto a different model” preserves the useful capability without promising arbitrary-event boundaries. Please update the JSON description, regenerate README, and qualify the equivalent “any step” wording in the PR body.

Actual Node 24.19.0 checks on this head: 120 projects / 10 categories validated, two generator passes were byte-identical to the committed README, the reviewed diff passed whitespace checking, and the initial full link pass was 120 ok / 0 failures / 0 warnings. A later full check of current upstream main found 118 ok / 1 failure / 0 warnings due to HTTP 404 on existing Fzkuji/OpenProgram; that separate catalog availability issue also prevents using the earlier green result as a current all-links-clear result. OrcaReplay's URL passed, its Apache-2.0 license was present, and the normal weekly star snapshot drift is not a requested change.

After updating the description:

node scripts/generate-readme.js
node scripts/validate.js
git diff --check
node scripts/check-links.js

Both Actions runs on this PR are currently action_required with 0 jobs (validate, links); Cursor Bugbot success is not a replacement for these checks. Maintainer workflow approval and successful execution are still required. No merge has been performed.