Continuum-AI-Corp / OrcaReplay
OrcaReplay — Time travel for AI agents. Record, replay, fork, and debug any agent run with any model. Built by the OrcaRouter.ai team.
- Stars
- 467 stars
- Forks
- 94 forks
- Language
- TypeScript
- License
- APACHE-2.0
- Created
- Aug 29, 2026
- Last push
- Oct 1, 2026
- Updated
- Nov 9, 2026
Why these Tags: an agent read the README and quoted it
- LLM observability from the readme:
each request, each streamed response, every tool call the model emitted, and every tool result the harness produced.
- LLM evaluation from the readme:
forked at checkpoint 4 onto two models and graded by `npx tsc --noEmit`.
An agent gave these Tags from the fixed Tag list in the AwesomeRepos source code. A code check kept each Tag only when its quote is in the text. A wrong Tag? Report an error with the form at the end of this page.
Admitted to the Repository Index on Nov 8, 2026: +107 stars in 7 days.
Star History
71 days recorded, Aug 31, 2026 – Nov 9, 2026 (UTC). Net change +478 stars.
The star count of each day is the latest count minus the net stars of the later days.
Add this Star History to a README
The images follow the light or dark theme of the page that shows them, and update every hour.
Add ?theme=light or ?theme=dark
to the chart address to keep one theme.
Star History chart
[](https://awesomerepos.com/Continuum-AI-Corp/OrcaReplay) Badge
[](https://awesomerepos.com/Continuum-AI-Corp/OrcaReplay) Timeline
It gained stars on 55 of the 71 days recorded since Aug 31, 2026.
Its largest 7 days were Nov 3, 2026 to Nov 9, 2026: 185 stars.
In the 30 days to Nov 9, 2026 it got 206 stars, 207% more than in the 30 days before.
- Created on the Repository Host
- Largest star day recorded: +43 stars
- Reached 100 stars, 7 days after it was created
- +39 stars in one day
- Latest push
- Entered the Repository Index: +107 stars in 7 days
- +38 stars in one day
The timeline comes from the creation date and the releases on the Repository Host, the Admission, the Star History, and the Observations. Star milestones show only when the Star History records the day. The list shows up to 5 stable releases from the latest 10 releases recorded. When none of them is stable, one item counts the pre-releases. On the chart of net stars each day, a solid line marks each recorded release.
Forks and pushes
From 2 Observations, Nov 9, 2026 – Nov 10, 2026. Forks +6. AwesomeRepos saw a new push on 0 of 1 days.
- Nov 10, 2026: no new push
A filled day: the last push time changed since the Observation before it.
Health facts
Measured facts in four separate dimensions, each with a date and a source. AwesomeRepos does not add them into one score. AwesomeRepos last read these facts from GitHub on Nov 10, 2026. How AwesomeRepos defines each check
Copies a prompt for a coding agent. It has 2 tasks for the maintainers of Continuum-AI-Corp/OrcaReplay.
Improve the Health Facts of the GitHub repository Continuum-AI-Corp/OrcaReplay. AwesomeRepos measures facts about how a repository is maintained, released, secured, and documented. Its page for this repository is https://awesomerepos.com/Continuum-AI-Corp/OrcaReplay. A change to the repository can improve each of the 2 items below. Each item gives the measured fact or score, and a task. 1. A release in the last 365 days Fact: No GitHub release (read on 2026-11-09). Rule: The newest published GitHub release (a pre-release counts; a draft does not) is 365 days old or less. A repository that publishes only tags, or only to a package registry, has no GitHub release. The release refresh reads the 10 newest releases after each push to the repository, and at least each 30 days. The index refresh reads the date of the last push each day. Task: Prepare a release, but do not publish it. Find the changes since the newest release, propose the next semantic version and the release notes, and ask me to publish the GitHub release. If nothing changed since the newest release, skip this item. If the project publishes only to a package registry, add a CI step that also makes a GitHub release for each version tag. 2. A changelog file at the root Fact: No changelog file at the root (GitHub, 2026-11-10). Rule: The root of the default branch has a file named CHANGELOG, CHANGES, HISTORY, NEWS, RELEASE, or RELEASES, with no extension or with .md, .markdown, .rst, .txt, or .adoc. Release notes on GitHub releases do not count. Task: Add CHANGELOG.md at the root of the default branch. Write one section for each published release, newest first, from the GitHub releases, the Git tags, and the commit history. Do not invent changes. If the project uses a release tool (for example Changesets, release-please, or semantic-release), configure it to update this file for each release. Rules for this work: - Each file must be true for this project. Do not copy text that does not apply to it. - Do not choose a licence, a contact, or a release version for me. Ask me. - Do not publish a release, change a repository setting, or push to the default branch. Make the changes on a new branch. - Keep each change small, and run the checks of this repository before you finish. - At the end, list each item as DONE, SKIPPED (with the reason), or NEEDS A DECISION (with the question). AwesomeRepos reads these facts again in its next scan. The definitions of the checks: https://awesomerepos.com/health-facts
Maintenance
3 of 4 checks-
Yes: Not archived
GitHub does not mark the repository as archived. Source
-
Yes: A push in the last 90 days
Last push on 2026-10-01, 40 days ago. Source
-
Yes: Commits in the last 13 weeks
265 commits on the default branch in the last 13 weeks (GitHub, 2026-11-10). Source
-
No: Commits in 26 or more of the last 52 weeks
Commits in 6 of the last 52 weeks (GitHub, 2026-11-10). Source
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 121
- 54
- 36
- 32
- 17
- 5
- 0
- 0
- 0
- 0
- 0
Releases
0 of 3 checks (1 without data)-
No: A release in the last 365 days
No GitHub release (read on 2026-11-09). Source
-
No data: The newest release tag is a semantic version
No data: no release.
-
No: A changelog file at the root
No changelog file at the root (GitHub, 2026-11-10).
Security practice
1 of 1 check-
Yes: A security policy
GitHub finds a security policy (GitHub, 2026-11-10). Source
OpenSSF Scorecard has no result for this repository from the last 90 days.
Community files
3 of 3 checksDependencies in the index
This section shows the packages that connect this repository to other repositories in the index.
GitHub has no dependency graph for this repository (scanned on Nov 10, 2026).
No scanned repository names a package from this repository.
Uses (in the index) · 0
None.
Used by (in the index) · 0
None.
Sources: the GitHub dependency graph of each repository, and deps.dev for the source repository of each package . A dependency graph also names development packages. deps.dev takes most source repositories from package metadata. How the dependency graph is made
Observations
Latest Observation, Nov 10, 2026: 467 stars, 94 forks, last push Oct 1, 2026, not archived. One of 2 Observations since Nov 9, 2026.