Talk to Control Center from a GitHub PR
This guide shows you how to work with Control Center without leaving GitHub: request an AI review from the PR page, ask the bot a question in a comment, and keep the conversation going in its review threads.
Replies come through the workspace’s GitHub lane: your server’s own GitHub App, or Control Center’s shared App through Connect. Nothing new is registered, and nothing has to be reachable from the internet: the server discovers what was said on GitHub by polling, so a laptop behind NAT behaves exactly like a public deploy.
Prerequisites
Section titled “Prerequisites”- The workspace has a GitHub lane: the server’s own GitHub App or Connect, with the app installed on the account that owns the repository. An own app needs Pull requests and Issues read and write, which Create my GitHub App already grants
- The repository is linked to a workspace in Control Center
- You are signed in to GitHub on this server, and you can push to the repository
- No webhook URL, no tunnel, no callback — there is nothing to configure on the network side
Find your bot’s name
Section titled “Find your bot’s name”Mention @usectrl, the dedicated Control Center GitHub account. It is the
only trigger: mentioning the App’s own login does nothing. Your workspace’s
GitHub lane still handles the request and posts replies. You do not need credentials for the usectrl account.
Request a review from GitHub
Section titled “Request a review from GitHub”Two ways, both starting the same seeded pr_review pipeline the Ask AI
button starts:
- Add the
ai-reviewlabel to the PR. This is the closest thing GitHub offers to assigning the bot as a reviewer — app accounts cannot hold the native requested-reviewer slot. Your account reacts to the PR with 👀 and the review starts in Control Center; no comment is posted - Comment
@usectrl review(or just@usectrl) on the PR conversation. A 👀 appears on your comment, then a reply says the review has started (or that one is already running)
The reviewers work in the PR’s review space; read and publish the findings as in Use AI-powered review. Publishing back to GitHub stays a decision you make in Control Center — starting a review from GitHub does not publish anything to GitHub on its own.
The label fires once per PR: adding it is the ask, and it is not re-armed when removed and re-added. To run a review again — after a push, say — mention the bot.
Ask a question
Section titled “Ask a question”Comment on the PR conversation:
@usectrl why does the flaky test in runner_test.dart fail on CI but not locally?What happens, in order:
- A 👀 appears on your comment, from your own account, so you know the comment was seen
- The question is posted into the PR’s review space as you — same attribution as if you had typed it in Control Center
- An agent answers in the space, and the answer is posted back on the PR. Every
reply starts with
**Control Center** (for @your-login):
A question on a PR with no review yet wakes the workspace’s CEO agent; once a review has run, the agent that spoke last answers, so follow-ups land with whoever has the context.
Follow up in a review thread
Section titled “Follow up in a review thread”Reply inside an inline review thread the bot is part of — a diff comment it left, or an answer it posted in that thread. No mention is needed; the thread is the addressing:
> @usectrl the retry loop looks O(n²) to me
what would the complexity be with the bounded queue instead?Multi-turn works the same way: each reply is another question in the same conversation, with the review space as context, and the answer comes back in the thread.
A follow-up on the PR conversation timeline is a new top-level comment, so it still needs an @mention.
Who the bot talks to
Section titled “Who the bot talks to”The server resolves the author of a comment, or whoever added the ai-review
label, before doing anything:
- The GitHub account must be signed in on this server. The match is on GitHub’s numeric account id, never the login. Sign in from Settings → You → Profile → Code hosting
- They must be a member with a write role (
member,admin, orowner) in the workspace that links the repository - They must be able to push to the repository on GitHub. Replies use a token limited to that person’s access, so someone who can only read gets no reply
Anyone else is ignored silently: nothing is posted, and their words never enter the workspace. Comments from bots, and Control Center’s own replies, are never treated as questions.
Two servers, one PR
Section titled “Two servers, one PR”The 👀 is also how servers agree on who answers. It is added with the author’s own sign-in, and GitHub tells the server whether that reaction is new. If you are signed in on two Control Center servers that both link the repository, the first to react answers and the other stays silent. The same holds for the label.
What to expect
Section titled “What to expect”| Thing | Behaviour |
|---|---|
| Acknowledgement | 👀 from your account on the comment (or on the PR, for the label), within one sweep |
| Answers | Posted in the lane the question was asked in, starting **Control Center** (for @your-login):. Authored by the app’s bot. On the shared Connect app, a reply inside a review thread is authored by your own account, unless the Connect operator listed this installation |
| In-space attribution | The question is yours; the agent runs on your behalf, under the space’s autonomy settings |
| Reviews | Findings land in the review space; publishing to GitHub is manual |
A sweep runs every minute on an own app and checks up to 25 pull requests; through Connect it runs every two minutes and checks up to 10, because those calls share each member’s own GitHub quota. A workspace whose GitHub quota is below 15% is skipped until it recovers. The latency is the trade for needing no inbound network access at all. Nothing is lost while the server is offline — a comment that arrives during downtime is caught on the next sweep.
Troubleshooting
Section titled “Troubleshooting”Nothing happens for a comment that mentions the bot.
- Is the app installed on the account that owns the repo, and the repo linked to a workspace? An unlinked repo is skipped before anything is recorded, so linking it later still delivers
- Are you signed in to GitHub on this server, a member with a write role, and able to push to the repo? The server ignores anyone else without replying
- Still nothing? The server log names the sweep and the PR when something
fails; look for
pr_conversation:(the poller) andgithub_pr_conversation:(the bridge)
The label does not start a review.
It fires once per PR, and the person who added it passes the same checks as a
comment’s author. If a review already ran, or the label was added before the
server ever saw the PR (the first sweep records the backlog silently rather
than storming it), mention the bot instead — @usectrl review always starts
one unless a review is already in flight.
The bot’s answer never arrived on GitHub.
The answer itself is never lost — it is in the PR’s review space in Control Center. A posting failure (GitHub down, permissions changed) is logged and the reply is not retried; ask again in the thread if it matters.
Related guides
Section titled “Related guides”- Create the GitHub App: the registration the bot is born from
- Use AI-powered review: reading the findings a mention-started review produces
- Set up GitHub integration: linking your own GitHub account, which is what the bot resolves you by
- Use spaces: the room all of this lands in