Add OrcaReplay to Productivity Tools - #553
Open
xizhuomengcontin wants to merge 1 commit into
Open
xizhuomengcontin wants to merge 1 commit into
xizhuomengcontin wants to merge 1 commit into
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds OrcaReplay to Productivity Tools, at the end of that section.
The section blurb is "tools, services which increase productivity, developer velocity and developer experience", and the neighbours are general developer CLIs —
tenv,pyenv,kubefwd,Telert,claws. This is one of those: a CLI you put in front of an agent or a service so its runs stop being unrepeatable.The second command re-runs the session with no provider called and no API key needed — the model's answers come from the recording while your own code and tool calls run for real. Nothing is installed into the agent: it launches the process with the provider origin redirected for that process only.
Where the velocity comes from: a session that went wrong becomes something a colleague can reproduce without your credentials and without spending tokens, and the same recording is a zero-cost regression test in CI — which is otherwise impractical for anything with an LLM in the path.
Two limits worth stating rather than leaving in the footnotes:
egress=blockedmeans model-provider egress, not network isolation. The recorded tool calls still execute for real, so it is not a sandbox.Apache-2.0, Node 20+,
npm i -g orcareplay. Disclosure: I maintain it.