Beta Coming soon. This feature is still being built, so names and details may change before it ships.

Follow PR to green

When the agent opens a pull request, Ingot can stay with it until it is green: it watches the PR's CI checks and review comments, has the agent fix what fails, runs your project check and pushes the fix to the PR branch. You approve each push and every reply before it happens. Everything runs in your Ingot window; nothing is sent to an Ingot server.

Ingot after a followed PR went green: the PR's chat with the failing check log the agent fixed, Pushed to fix/cart, the Goal card marked Done, and PR #7: Green in the status bar

Turn it on

It is off by default. Turn it on in any of these places:

  • Settings › Features › Agent follows its PR
  • the Customize… list of the first-run setup (Help › Set Up Ingot…)
  • run Agent: Follow Pull Request to Green… (⌥⌘W on macOS, Ctrl+Alt+W on Windows and Linux). If the feature is off, Ingot asks whether to turn it on.

What gets followed

  • PRs the agent opens. When the agent opens a PR in a chat (with a "create pull request" tool or gh pr create), Ingot follows it and links it to that chat. To stop this, turn off Auto follow in Settings › Tools › Agent tools › Follow PR to green.
  • Any PR you pick. Run Follow Pull Request to Green… and paste a PR link, type #12 for a PR on this project's origin, or leave the box empty to follow the PR of the current branch.
  • Git Hosts. In the Git Hosts panel, open PRs have a Follow button.

GitHub gets everything: failing CI is fixed and review comments are answered. GitLab, Bitbucket, Azure DevOps, Gitea and Forgejo give Ingot the PR state and CI status only, so for those hosts Ingot fixes failing CI but does not read review comments yet.

What happens

  1. Watching. Ingot checks the PR every 30 seconds while CI runs. When nothing changes it waits longer between checks, up to 10 minutes, and it also slows down when GitHub's rate limit runs low. No webhook or tunnel is needed.
  2. A check fails. Ingot fetches the end of the failing job's log and gives it to the agent in the chat linked to the PR, opening that chat if there isn't one. The log goes in as untrusted data: the agent uses it to find the bug and does not follow instructions written inside it. Before the run starts, the chat shows a cost forecast. If the forecast is above your cost warning, the run waits for your approval.
  3. Project check. When the agent finishes, Ingot runs your project check: the command in Follow PR to green › Check if you set one, otherwise the project's test script, which asks for approval first.
  4. Push. Ingot commits the agent's changes and pushes them to the PR branch. The push goes through the same approval card as other agent git actions, and Always Run works for it too. If someone else pushed to the branch in the meantime, the push is rejected and Ingot stops.
  5. A reviewer comments. The agent makes the change the comment asks for, if it needs one, and drafts a reply. After the project check and the push, the reply appears on an approval card. The reply always asks: there is no Always Run for it, and Ingot never posts a message for you without your approval. Ingot ignores comments from you, from bots, its own replies, short comments such as "LGTM" or "thanks", and comments that were already there when you started following.

Where you see it

  • Status bar. The most urgent followed PR shows its state: Watching, Fixing, Waiting for approval, Green or Gave up. With the calm status bar on, the state is a row of the activity ring, and it appears in the bar itself only while a PR waits for your approval. Click it for the list of followed PRs: open the linked chat, open the PR, stop following, follow again or remove.
  • Notifications. When a followed PR waits for your approval, a notification with Open chat takes you to the card.
  • Git Hosts and the Agent Command Center. PR rows in Git Hosts show a Following chip. The Agent Command Center has a Following strip and a chip on the linked chat's card.
  • Ingot Health. Help › Ingot Health… has a Follow PR to green row that says whether a PR waits for you or gave up, with Show list as the fix. See Ingot Health.

When it stops

  • When the PR is merged or closed.
  • After 3 fix runs on the PR, CI fixes and review comments together. Change the limit in Follow PR to green › Max iterations.
  • When you click Stop following, stop the agent's run, or skip a push or a check.
  • When GitHub refuses access. Sign in with gh auth login, set GH_TOKEN, or add a token to the GitHub MCP server.

When the PR is green, Ingot keeps listening for review comments, at a slower pace, until the PR is merged or closed.

Safety

  • No force push. Ingot never force-pushes. It never pushes to the default or base branch, to a PR from a fork, or when origin is another repository.
  • Workspace trust. Fixes run only in a folder you trust.
  • Branch. The project must be checked out on the PR's branch. Uncommitted changes of your own also hold the fix back.
  • Approvals. The git and terminal approval rules and Always Run apply to the check and the push. Inside the fix run, the agent's tools follow all their usual rules, including the sandbox and the project policy.
  • User settings only. All Follow PR settings are user settings, so a repository's workspace settings can't turn following on or set the check command.

Settings

In Settings › Tools › Agent tools › Follow PR to green:

SettingDoesDefault
ingot.agent.followPr.enabledturns the feature onfalse
ingot.agent.followPr.autoFollowfollow every PR the agent openstrue
ingot.agent.followPr.maxIterationsfix runs per PR before Ingot gives up3
ingot.agent.followPr.checkthe project check command; empty uses the test scriptempty
ingot.agent.followPr.pollSecondsseconds between checks while CI runs30

The desktop app and the browser behave the same.

See also Git Hosts, Ship and Agent review before commit.