Evidence record / openhands

A dated record of one change, kept so the writing that cites it can be checked. Compiled from the sources listed below by the research run, not written for reading. The judgment lives in the signals and issues that cite it, below.

2026-10-24-openhands-github-mentions-can-request-code-changes-under-a-repository-write-gate

GitHub mentions can request code changes under a repository-write gate. The monitor defaults to repository-write authorization and implement work mode, allowing authorized requests to lead to branch creation, commits, pushes and updates to existing pull requests. The polling script mechanically checks GitHub repository permissions for other authors, but explicit allowlists and the token owner bypass that check; anyone bypasses it generally. Work restrictions are agent instructions. The catalog fallback template expresses both its authorization check and work restrictions in the prompt. reply is the narrower work mode.

Channel: tagged-release. Half: both. Date: 2026-10-23 (extensions v0.35.0; Canvas v1.32.0).

Operator consequence: Audit the actual deployed monitor definition, bypass list, token scope and work mode before enabling it. Pairing anyone with implement lets arbitrary commenters request code changes using the automation’s token. This can replace manual request-to-branch coordination, but moves the critical human decision to who may start work. Do not infer migration of existing saved bundles or mechanical enforcement of prompt restrictions. No live repository monitor was exercised.

Receipt

Finding metadata

Run: 2026-10-24-weekly-digest-2026-10-13_2026-10-24-frontier-v0

Finding ID: 2026-10-24-openhands-github-mentions-can-request-code-changes-under-a-repository-write-gate

Profile citations

  • OpenHands / claim / github-monitor-authorization-and-implement
  • OpenHands / posture / governance

Source links

Primary links, including exact changelog lines when available.

Versioned source: run artifact