Dependency updates, merged without you.

Ensemble takes Dependabot and Renovate pull requests from opened to merged: it approves them, fixes red CI and merge conflicts, and merges when the checks pass. It runs on your machine, under your GitHub account.

  • On by default, in every workspace. Switch any part off in Settings → Dependencies.
  • Dependabot and Renovate are trusted by default. Any other bot you trust by hand.
  • It acts only in repositories you can push to.

One teammate handles each update. Nobody has to open it.

What happens to an update

Each step is its own switch. Each one claims the pull request on GitHub before it writes anything.

  1. Bot

    An update arrives

    Dependabot or Renovate opens a pull request in one of your repositories.

  2. Ensemble

    It claims the pull request

    A status line on the commit says you are handling it. Your teammates’ copies read it and step aside.

  3. Ensemble

    Approve

    When the checks pass, it approves under your account. Only for a bot you trust.

  4. Agent

    Fix

    Red CI or merge conflicts: your Claude or Codex fixes them in a sandbox, and the fix is pushed.

  5. Ensemble

    Merge when ready

    It lands when every check passes. If anyone pushes in the meantime, it stops.

Approve them automatically

Once the pull request’s checks pass, Ensemble approves it under your account. It does this only when the update comes from a bot you trust, so a look-alike account never gets an approval.

Merge them automatically

It arms Merge when ready, which lands the pull request when every check passes, through GitHub’s merge queue where a repository uses one. Arming pins the commit: if anyone pushes, it stops. Merging needs no trust, because it waits for every check.

Fix them with AI

When CI is red, your Claude or Codex reads the failure and fixes it in a sandbox on your machine, and the fix is pushed to the update’s branch. That commit is merged only once its own CI is green. At most two AI runs per pull request a day.

Resolve their conflicts

It first asks the bot to rebase, and waits 30 minutes. If the conflicts are still there, your agent merges in a sandbox and resolves them. Only a merge that checks out is pushed.

Once per team.

Every teammate runs Ensemble on their own machine, and there is no server between you. GitHub keeps the score, the same way it does for reviews.

Claim, then act

Before any write, Ensemble posts a status line on the commit: you are handling it. It reads the lines again, and the earliest claim wins. A teammate’s copy that sees your line steps aside.

A claim never sticks

A claim lasts while its machine is working on it. If a laptop closes mid-fix, the claim runs out and a teammate’s copy takes over. When the work ends, the line says what was done, or that it is free.

Not CI

These lines sit beside your checks on GitHub, but Ensemble never counts them as CI, and they never block a merge.

What keeps it in bounds

Which updates

Choose the largest update it handles (patch, minor or major), security fixes only, and which ecosystems. Every switch follows these.

Your AI budget

Every AI run asks your spend budget first. Over it, the run is skipped, not queued. With no container runtime, the AI steps are skipped and the log says so.

You win

Cancel it on a pull request and it stays cancelled for that update. Pending → Dependencies lists what it did in the last two weeks, one entry per pull request.

Let the bots finish their own work.

Run it on your machine, sign in to GitHub with gh and to Claude Code or Codex.

npx ensemble-review