Skip to content

Introduction

repo-ai is a command-line tool that runs on your machine, inside a Git repository. It has three parts, and each works without the ones after it.

Part What it does Needs an agent? Runs your code?
Context Indexes the repository offline and answers “where should I start for this task?”, “what can this change reach?” and “why was this file ranked?” No No
Evidence repo-ai verify lists what a change touched and which tests can show a break; verify --run runs them sandboxed in a disposable copy and separates new failures from ones already present at the base commit No Only with --run, sandboxed
Agents (optional, experimental) repo-ai do plans a task offline and, only with explicit consent, asks a coding agent for a candidate in an isolated worktree, checks it against frozen tests, and leaves applying it to you Only for live runs Only with --run, sandboxed
  • Developers who want a quick, explainable answer to “which files and tests matter for this change?”
  • Anyone who wants to run the relevant tests before pushing without letting those tests touch the working tree.
  • People experimenting with coding agents who want the agent’s output treated as an untrusted candidate, not as a finished change.
  • Not a proof of correctness. A PASS means the frozen tests observed a pass. It does not mean the task is correct: the tests may not state the requirement that matters. See Requirement coverage.
  • Not a hosted service. There is no daemon, no account and no telemetry. Nothing goes over the network unless you pass a flag that asks for it (listed on Security & privacy).
  • Not shown to make agents better. Whether repo-ai improves a coding agent’s results over using the agent alone is NOT_YET_DEMONSTRATED. The studies so far are on Evaluation & methodology.
  1. Install — Python 3.10–3.14, macOS, Linux or Windows.
  2. Quickstart — index a repository and verify a change, no agent needed.
  3. Verify a change — the plan, the sandboxed run and the evidence it keeps.
  4. Status matrix — what is stable, experimental or unsupported, and why.

If you want agents in the loop, read Missions with agents and Providers before running anything live.