Skip to main content
READMEs drift: a flag gets renamed, an install step stops working, an example uses an old function. This agent reads a snapshot of your repository, checks each claim in the README against the code, and proposes a corrected README. Your program shows you the diff and asks before it writes the file. If you say no, you tell the agent why and it tries again in the same session. You will use: a managed sandbox, uploaded files, and artifacts.
A managed sandbox uses machine time while it runs and needs your plan’s minimum balance of Orca credit in your wallet.

How it works

The agent works on a copy in its sandbox and cannot touch your machine. The only way its edit reaches your files is through your program, after you approve it. The rule that matters most is “with the file and line that proves it”. It makes the agent check claims instead of rewriting prose it likes better, and it gives you something to verify.

The program

Examples on this page assume the settings from the shared setup. Run it from the root of a Git repository. It packs the committed files with git archive, so uncommitted changes and ignored files stay on your machine. Orca stages at most 16 MiB from one file, so the program stops if the compressed snapshot is bigger. For a large repository, archive only what the agent needs, for example git archive --format=tar.gz HEAD README.md src.
Each turn’s outputs become new artifacts and the old ones stay as they were, so newest() picks the latest copy by its creation time.

Make it yours

  • Include more docs. Name other files in the prompt, for example “also check docs/install.md and CONTRIBUTING.md”, and have the agent save each one under /workspace/outputs.
  • Run it in CI. Without the prompt, the same program can fail a build when the agent proposes any change, and attach changes.md to the job.
  • Open a pull request instead. Write the proposal to a branch and open a pull request from your program, so the review happens where your team already reviews code.
  • Keep secrets out. git archive only packs committed files. If secrets are committed, rotate them; do not send that snapshot.