Adar + AI agents

Your agents write the code. You stay in the loop.

Claude, Copilot, Codex or Cursor can write most of a change now. Deciding whether it is right is still yours. Adar is where you see what they did, review it, and keep up while they keep going.

Adar reviewing a pull request co-written by Claude: only the two commits pushed since the last review, a comment thread answered by the author, and the review panel on the right.
Since your review — only the new commitsClaude co-wrote itThreads on their linesYour review, sent in one go

The loop

Six steps, every day.

The same loop whether one agent is fixing a bug or three are building a feature each.

  1. One agent, one worktree

    Give each agent its own folder and branch, so none steps on another’s files. Make them in Adar or let your agent tool do it: each opens as a tab in the project’s group, side by side.

    New Worktree…
  2. Watch them work

    Every tab shows its branch growing and its uncommitted changes as a live node. Background fetch brings in what they push, and the commits an agent co-wrote carry its name from their Co-Authored-By line.

    // WIP
  3. Review what they pushed

    When an agent opens a pull request, review it in Adar: the files with GitHub’s Viewed marks, lockfiles folded away, comment threads on their lines. Comment, suggest a change, request changes. The agent reads your review where it always does, on GitHub.

    Review changes
  4. Only what’s new

    Second round? Since your review shows just the commits pushed after it, and says when the branch was rebased with the same changes or only had main merged in. No rereading a whole pull request to find the two lines that moved.

    Since your review
  5. Know when to look

    Reviews lists the pull requests waiting for you, the ones you follow and yours, across every open repository. A blue dot marks what changed since you looked, and a notification tells you while you’re doing something else.

    Reviews ⇧⌘R
  6. Merge, tidy up, take back

    Merge from Adar and the branch and its worktree go in one step. If an agent reset or force-pushed what it shouldn’t have, Adar finds the lost commits in the reflog, and Undo takes back the last git action.

    Recover Lost Commits…
Adar’s pull request inbox: one waiting for review, one followed with a reply and a new commit, two of the user’s own, one approved and ready to merge.
Everything waiting for you, in one place. The blue dot is what changed since you looked.

The agents get the work. You keep the keys.

Adar drives the git already on your machine, with the credentials you already use. It has no account, no servers and no telemetry, and talks to GitHub, GitLab, Bitbucket or Azure DevOps only when you turn pull requests on.

  • Your git and SSH keys
  • GitHub, GitHub Enterprise, GitLab, Bitbucket, Azure DevOps
  • Every agent tool: nothing to install in them
  • Free and open source · MIT

Growing next

What comes next, in the open.

next

Agents at work

Live activity of the worktrees your agents work in: files changing now, time since the last change, and a ping when one commits, pushes or goes quiet.

next

AI-authored commits in the graph

A mark on every commit an agent co-wrote, with a human / AI filter.

next

After a force push

The old and the new version of a branch an agent rewrote, side by side, and what a merge’s conflict resolution changed.

next

Every service

Reviewing on GitLab, Bitbucket and Azure DevOps too, as on GitHub today.

See the roadmap

Try it with your agents.

Free, open source, and on the git you already have.