Pull requests

From the agent's branch
to a reviewed pull request

Your agent has finished. Before, you left for GitHub to open the pull request, came back to read the review, and pasted each comment into the agent's terminal.

AgentsRoom does those steps where the agent works. Create PR sits next to Push in the Changes tab: the AI drafts the title and the description, you edit them, and the badge then follows the state and the review. When reviewers comment, one click sends the unresolved comments to the agent.

Changes

fix/checkout-total

PushCI passed#42 Open

Changes requested

3 unresolved comments

Send the comments to the agent

Agent

Review comments on pull request #42, branch fix/checkout-total:

  • cart.ts, line 48
  • total.test.ts, line 12

Fix them and push to the same branch. Do not merge.

An agent CLI can open a pull request itself if you ask it and the GitHub CLI is installed. What remains is everything around it: checking that the branch is pushed, writing a description that a reviewer can read, watching for the review, and getting the comments back to the agent that wrote the code.

With several agents on one project, each in its own worktree, that loop runs several times a day. The comments live on GitHub or GitLab, the agent lives in your terminal, and you are the one who copies from one to the other.

AgentsRoom puts the pull request in the Changes tab, next to Push and the CI badge, on the same account you connected to import your repositories. It works the same whatever CLI the agent runs: Claude Code, Codex, GitHub Copilot CLI, Cursor or another one.

What you get

One button to open it, one badge to follow it, one message to fix it.

Create PR next to Push

In the Changes tab, on a row of the Worktrees view, or in an agent's right-click menu. If the branch was never pushed, the button says Push and create PR and does both.

Title and description drafted for you

The AI writes them from the branch diff, its commits and the linked ticket. You edit them, change the base branch, tick Open as a draft, then send. Nothing is sent before you click.

State and review on a badge

Draft, open, merged or closed, the verdict (approved, changes requested) and the number of unresolved comments, next to the CI badge. Click it to open the pull request on the host.

Review comments back to the agent

Send the comments to the agent lists the unresolved threads with their file, line, author and code excerpt. Untick what the agent should leave alone, and it gets them in one message.

Told when the review arrives

A notification on the desktop, and on your phone when you are away, when a review or a comment lands on a pull request you created from AgentsRoom.

On your phone and on the ticket

The Worktrees screen of the mobile app shows the pull request of each checkout, creates it and sends its comments, the desktop doing the work. The linked backlog ticket shows the number, the state and the verdict.

How it works

Connect your host once, then the loop stays in the Changes tab.

  1. 1

    Connect GitHub or GitLab once

    Use the account you connected to import repositories, or the grey PR badge. On GitHub, a classic token with the repo scope or a fine-grained one with Pull requests: write. On GitLab, a token with the api scope to create merge requests.

  2. 2

    Click Create PR

    The mascot thinks while the AI drafts the title and the description from the branch. Read them, edit them, check the base branch (for a fork, upstream is proposed), tick Open as a draft if needed, then Create PR.

  3. 3

    Follow the badge

    The badge next to the CI badge shows the state, the review verdict and the unresolved comments. The card of an agent working in its own worktree and the linked ticket show it too.

  4. 4

    Send the comments to the agent

    Click the comment count, untick what should stay as it is, pick the agent of that checkout or a new agent in it, and send. The agent fixes, commits and pushes to the same branch, and the pull request updates.

Why it matters with several agents

When one agent opens one pull request a week, doing it by hand costs nothing. When four agents finish their branches on the same afternoon, the slow part is no longer the code: it is opening each pull request, describing it well enough to be reviewed, and carrying the review back to the right agent.

Keeping the review and the agent in the same place also keeps the fix on the right branch. The message tells the agent which pull request and which branch the comments belong to, and asks it to push there without merging and without opening another pull request.

Limits

  • GitHub.com and GitLab (gitlab.com or the self-hosted instance you connected). Bitbucket and Azure DevOps open their own new pull request page in your browser. GitHub Enterprise is not supported.
  • Merging, approving and resolving a thread stay on GitHub or GitLab.
  • Review notifications cover the pull requests created from AgentsRoom on this computer, checked every 3 minutes while the app runs.
  • The state is refreshed while a badge is on screen; agent cards and tickets show the last state seen.
  • Agents that work in the project folder share its branch, so their cards show no pull request: the folder's pull request is on the Changes tab.
  • Without the AI (offline, local mode, or when the draft fails), the form still opens, filled from the commits, and says so.

Frequently asked questions

Ask us something else
Can Claude Code or Codex create a pull request from AgentsRoom?
Yes. When an agent has finished on its branch, click Create PR next to Push in the Changes tab, on its row of the Worktrees view, or in its right-click menu. AgentsRoom pushes the branch if needed and opens the pull request on GitHub or the merge request on GitLab, whatever CLI the agent runs: Claude Code, Codex or another one.
How does AgentsRoom write the pull request title and description?
The AI drafts them from the branch diff since its base, its commits and the linked ticket, and AgentsRoom adds the ticket line itself (and Closes with the key for a ticket imported from a tracker). You read and edit both before anything is sent. If the AI is not available, the form is filled from the commits.
How do I get an agent to fix the review comments?
Click the number of unresolved comments on the pull request badge, then Send the comments to the agent. Every unresolved thread is ticked, with its file, line, author and code excerpt; untick the ones to leave alone, pick the agent of that checkout or a new agent in it, and send. The agent receives them in one message, fixes them and pushes to the same branch.
Does it work with GitLab merge requests, Bitbucket or Azure DevOps?
GitLab is supported, on gitlab.com or the self-hosted instance you connected, with a token that has the api scope to create merge requests. Bitbucket and Azure DevOps have no connection in AgentsRoom: Create PR opens their own new pull request page in your browser. GitHub Enterprise is not supported.
Can I create and follow the pull request from my phone?
Yes. In the mobile app, the Worktrees screen of the project shows the pull request of each checkout with its state, its verdict and its unresolved comments, and offers Create PR and Send the comments to the agent. The desktop does the work, so it must be running. A tap on a review notification opens that screen.
Can AgentsRoom merge or approve the pull request?
No. Merging, approving and resolving a thread stay on GitHub or GitLab, on purpose: the message sent to the agent even asks it not to merge and not to open another pull request. AgentsRoom creates, follows and feeds the review back.

You may also like

Your agents write the branch. The pull request follows.

AgentsRoom runs on macOS, Windows and Linux, with the mobile app to follow the review from your phone.

Download AgentsRoomFree

Companion app: monitor your agents on the go

Bring your own: Claude, Codex, Antigravity CLI, or other AI provider.

Push bugs and requests straight to your public backlog.