Did my request for the bot trigger both? (two runs, or is it a run with two comments?)

🤖 On it! View progress here: oss-agent-canvas.ngrok.dev/conversations/…

@fresh-machine-37269 this was on openhands/agent-sdk repo

✅ Done! Requesting a review from

all-hands-bot

on a PR triggers OpenHands to spin up a run on that pull request. It reads the PR's diff and description, then works through the changes — reviewing, leaving comments, and/or making fixes as appropriate. It's essentially the same entry point as the

@openhands

mention or

/openhands

comment; a review request is just another way to kick off a run. As for your earlier question about "two runs vs. one run with two comments": a single review request triggers one run. If you see multiple comments, they're typically multiple messages from that same run (e.g., a review comment plus a summary comment), not two separate runs. Two separate runs would only happen if you triggered the bot twice (e.g., two review requests, or a review request plus an

@openhands

mention). Want me to check the actual run history on a specific PR to confirm what got triggered?

check actually the openhands/extensions/ repo, pr 463

✅ Done! I checked PR #4440 on

openhands/agent-sdk

— here's what actually happened. Two separate runs, on two different commits (not one run with two comments): 1. Run 1 — review started at 22:48 on commit

796e093

, review posted at 23:00 2. Run 2 — review started at 23:02 on commit

ca5a84f

, review posted at 23:09 Your review request to

all-hands-bot

triggered one of these — the first one. The

review_requested

event is what kicks off an OpenHands run (and importantly, as the bot's own comment noted, requesting the bot as a reviewer lets it review even when CI is failing). The second run happened because a new commit (

ca5a84f

) was pushed after the first review — each new push to the PR re-triggers a run. So: one review request = one run. The second run was from the push, not from your review request. Each run posts an "OpenHands is reviewing this PR" comment (with a conversation link) plus a separate review when it's done — so you see two comments per run, but they belong to the same run.

^^ if this is accurate, we can maybe strengthen the check for what reviews already exist; because at 23:02 there should have been one already with no commit