Skip to content

Add orcareplay to Other - #52

Open
xizhuomengcontin wants to merge 1 commit into
linsa-io:masterfrom
xizhuomengcontin:orcareplay-other
Open

xizhuomengcontin wants to merge 1 commit into
linsa-io:masterfrom
xizhuomengcontin:orcareplay-other

Conversation

@xizhuomengcontin

Copy link
Copy Markdown

Adds orcareplay to Other.

It records an AI coding agent's session from outside the process and can then serve that recording
back, so the same run happens again with no model called and no key needed:

$ orca record codex -- codex exec "fix the failing test"
info recorded run=run_8f21c3 events=41 exit=0

$ orca replay last
info replay.done reused=6/6 exact=6 divergences=0 exit=0

Checked against your guidelines:

  • Searched the list first — no record/replay tool for agents is in it.
  • Format [name](link) - Description., description starts with a capital, ends with a full stop,
    and does not begin with "A"/"An".
  • Link goes to the GitHub repo. Apache-2.0, Node 20+, installed with npm i -g orcareplay.
  • Category: Other, alongside watchexec and grcov — general developer CLIs that are not tied
    to one language. Your guidelines say new categories are welcome, and an "AI" category would
    arguably fit better, but adding a heading for a single entry seemed presumptuous; happy to move it
    if you would rather have one.

One thing I would rather say than have you discover: replay blocks the model provider, not the
network. The recorded tool calls still execute for real, so a step that ran curl runs it again.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant