Skip to content
oscillatingworksPublic

About

Review rounds between two coding agents: one sandboxed reviewer session per review, on any git project, with any agent and model.

Resources

Stars

0 stars

Watchers

0 watching

Forks

Repository files navigation

rounds: an 8-bit tennis racket and ball

rounds

Personal code reviews between two coding agents, on your machine.

One agent writes, another reviews, round after round, until the reviewer accepts or asks you to decide. The reviewer runs in a sandbox: it reads your code and runs your checks, but it cannot change a file of your project.

It is for you, not for your team. Nothing is committed, nothing is pushed, nothing reaches a pull request: the reviews live in .review/ of your checkout, which git ignores. Use it as a second opinion before you share your work. The one exception is a review you post yourself (below).

How it works

Compatible with all agents and models. How rounds works, as a tennis match. The writer starts the reviewer and serves round 1, the request, across a net of threads in .review. The sandboxed reviewer returns a response: changes, with two findings. The writer plays round 2, a request with the fixes. The reviewer responds accept: game, and it stops. A human verdict stops play, and you, the human, decide.

Your agent (Claude Code by default) starts a reviewer (Codex by default) for the review and serves round 1: the request. The reviewer reads the change, runs your checks, and returns a response with a verdict. The rally goes on until the reviewer accepts, and then the reviewer stops. When a decision is yours, play stops until you make it.

Each review thread is one match, with its own reviewer session. The two agents talk only through plain files, so every review is a record you can read: what was asked, what was found, what was fixed.

Install

Tell your agent, from inside your project:

Set up rounds in this project: https://github.com/oscillatingworks/rounds

Or by hand:

curl -fsSL https://raw.githubusercontent.com/oscillatingworks/rounds/main/install.sh | sh

Use

Ask your agent for a review when a change is ready: "get this reviewed". It opens a thread, a reviewer starts beside it (a tab in Herdr, a window in tmux, or a background process), and your agent answers the findings until the reviewer accepts. The first time, Codex asks in its tab whether to trust your project: answer it there, once. .review/bin/review status lists the threads, newest first; review open <thread> prints where a thread's files are (git ignores .review, so editors hide it).

Any agent and any model can take either role. Claude Code writes and Codex reviews by default; reviewer in .review/config.json changes the reviewer.

Independent, not adversarial

By default the reviewer is independent, not adversarial. It is another agent, in its own session, that sees only your request and the code, runs the real checks, and cannot change a file. But it reviews with an open mind: it looks for what is wrong, says what it checked and found fine, and accepts when nothing blocking remains. That keeps the loop short for everyday changes.

For a risky change, ask for a skeptic. The reviewer then assumes the change is wrong, tries to break every claim, and gives each finding a concrete failure:

.review/bin/review start <thread> --stance adversarial < ask.md   # one thread

Or tell your agent "get an adversarial review". To make every thread adversarial, set "stance": "adversarial" in .review/config.json. For a review that looks for what an attacker can do, tell your agent "get a security review" (--focus security); both together make an adversarial security review.

Review a pull request

Tell your agent "review PR 42". You read the comment first; it is posted only when you say so, from your account, signed "reviewed by 🎾rounds".

Remove

.review/bin/review uninstall           # keeps the threads
.review/bin/review uninstall --purge   # removes them too

More

AGENTS.md has the details: requirements, agents and models, the sandbox, where the reviewer runs, and how to work on rounds. docs/method.md says why the method works this way.

License

MIT. See LICENSE.

About

Review rounds between two coding agents: one sandboxed reviewer session per review, on any git project, with any agent and model.

Resources

Stars

0 stars

Watchers

0 watching

Forks

Releases

Contributors

Languages