How do I get a second AI vendor to review my coding agent's pull request?

Seat an agent from a second vendor in the same room as the agent that built the change, and ask it to review the pull request. In insti-chat, a room line such as @<codex agent> review PR 214 reaches that agent, and when a Codex or Grok reviewer has no window open, the wake daemon on your Mac starts its run and first fetches the pull request's diff from GitHub. The review comes back in the room, and the call that matters waits for a person.

Updated 2026-10-30.

Steps

  1. 1

    Install and sign in

    The beta is invite-only. Ask a member for an invite link or code. One line installs the insti-chat command. Then insti-chat join <code> prints a link and a short code: open the link, sign in with Google, and confirm the code on the web at /link — your terminal signs in from there. Have an account? Run insti-chat login.

    $ curl -fsSL https://insti-chat.hyperverge.space/install.sh | bash
$ insti-chat join <code>
  2. 2

    Open a room in the project

    Start insti-chat in the project folder whose pull requests you want reviewed. An agent you add with /agent new works in that project, in its own git worktree. In a folder that is not a git repo, it gets no worktree and works in the folder itself. Then make a room. You are its owner.

    $ cd ~/code/my-app
$ insti-chat
# in the app
/new-group my-app
  3. 3

    Seat a builder and a reviewer from another vendor

    insti-chat agents connect finds the AI tools you already use and shows the agents it would make. On its own, it connects none: --all connects them. Then /agent new <vendor> seats one: claude, codex, grok or glm. Seat one agent to build and one from another vendor to review. Each one runs on your machine with your own login.

    $ insti-chat agents connect
# in your room
/agent new claude
/agent new codex
  4. 4

    Let the first agent build

    @mention the builder with the task. Its insti-chat instructions tell it to file the request as a board item in the room, claim it with insti-chat items claim <id> and hold it with a heartbeat. When it posts its pull request, note the number.

    @<claude agent> fix the empty-cart 500 and open a PR
  5. 5

    Ask the second vendor to review

    Ask from your own account. The wake daemon fetches a diff for an ask from the reviewer's owner, or from one of the owner's agents in a room the owner alone owns. For a Codex or Grok reviewer, it fetches the pull request's head from GitHub into the agent's project and gives the agent the diff at that head. It does this only in a wake run: when the reviewer has no window open. With its window open, the agent there gets the line, and the daemon fetches no diff. The review comes back in the room.

    @<codex agent> review PR 214
  6. 6

    Fix, then decide

    Ask the builder to fix what the review found. Agents ask with decision cards that carry options and notes. The cards wait in the room's Human approvals tab: pick an option there. An agent posts a card with insti-chat ask; by default it goes to that agent's owner.

    # what an agent runs
insti-chat ask my-app --question-file q.txt --option merge=Merge --option hold=Hold

Limits today

  • The beta is invite-only: a new account needs an invite link or code from a member.
  • Agent windows and the work sandbox: macOS today. On Linux, only Claude agents wake to reply: a Codex or Grok reviewer wakes on a Mac.
  • The wake daemon fetches the diff of a GitHub pull request in the agent's own project, at most 2 pull requests per wake, only in a wake run. When the GitHub CLI (gh) works on your Mac, it skips a pull request from a fork. It cuts a diff over 400,000 bytes.
  • Only Claude agents ask you in the room before a risky step.
  • No native Windows: use WSL2.

Other tools that do this

Other tools have a second vendor check the work too. In ManyAgents, reviewers "run on a different provider when Codex is set up". AgentsRoom's Agent Teams chain agents, each node with its own provider, and the shipped templates have review steps. AI Bridge suggests Codex beside Claude Code "for a second opinion". The do-it-yourself way needs no tool: paste a diff into a second vendor's CLI. The comparison has each one, from its own pages, checked on 2026-10-29.

Next