Problem
The review prompt tells the agent to post one review with a verdict, a body, and inline comments. gh CLI has no command for that, so agents build the REST calls by hand: create a pending review, add each comment, submit. A recent codex review run spent most of its wall time reconstructing this flow from web docs before it could post.
The GitHub MCP server has typed tools for exactly this (create pending review, add comment to pending review, submit pending review). But review runs do not receive it: ReviewWorkspace declares no required MCP servers. BuildWorkspace already shows the pattern — it delivers the GitHub MCP authenticated with the review actor's secret.
Proposal
Give ReviewWorkspace the same required GitHub MCP server as BuildWorkspace, authenticated with the review actor token. The run then has gh and the MCP tools under one identity, and the review posts as the review actor through either path.
An alternative or complement: name the one-shot endpoint in the review prompt (POST /repos/{owner}/{repo}/pulls/{n}/reviews with a comments array posts everything in one call), so a harness without MCP support does not have to rediscover the API.
Problem
The review prompt tells the agent to post one review with a verdict, a body, and inline comments.
ghCLI has no command for that, so agents build the REST calls by hand: create a pending review, add each comment, submit. A recent codex review run spent most of its wall time reconstructing this flow from web docs before it could post.The GitHub MCP server has typed tools for exactly this (create pending review, add comment to pending review, submit pending review). But review runs do not receive it:
ReviewWorkspacedeclares no required MCP servers.BuildWorkspacealready shows the pattern — it delivers the GitHub MCP authenticated with the review actor's secret.Proposal
Give
ReviewWorkspacethe same required GitHub MCP server asBuildWorkspace, authenticated with the review actor token. The run then hasghand the MCP tools under one identity, and the review posts as the review actor through either path.An alternative or complement: name the one-shot endpoint in the review prompt (
POST /repos/{owner}/{repo}/pulls/{n}/reviewswith acommentsarray posts everything in one call), so a harness without MCP support does not have to rediscover the API.