Signals

2026-10-24 / OpenHands

OpenHands packages mention-to-code work and a factory setup recipe

Edited by Michael Ruescher

Extensions 0.35.0, bundled from Canvas 1.32.0 and retained in 1.33.0, lets permitted GitHub mentions request branches, commits, pushes and PR updates. Its monitor defaults to repository-write authorization and implement mode. Separately, shipped software-factory guidance assembles issue-to-PR, review and triage stations; guidance is enabled by default for new workspaces but does not start jobs on installation. Specialist operating procedure still has a job.

What this changes for operators

  • Repository automation owners: try one bounded repository on Canvas 1.33.0 with its extensions 0.35.0 and matched services. Review the factory’s proposed profiles, credentials and jobs before replacing manual request-to-branch coordination or custom onboarding.
  • Inspect the deployed monitor, token owner, allowlists and work mode. The poller checks other authors’ repository permissions, with explicit bypasses; the fallback template puts authorization and work restrictions in the prompt. Use reply mode for discussion, and avoid anyone plus implement when arbitrary commenters must not start code changes.
  • Exercise an authorized request, an unauthorized mention and a request outside the work policy; inspect the branch and token used. Those results and review minutes per accepted PR would establish the deployed benefit. Updating Canvas does not prove saved monitors migrated.

Signal metadata

Source findings

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

Schema: bitter.frontier_signals.v0 / ID: 2026-10-24-openhands-mentions-can-start-code-changing-work

Research evidence and publication history are open in the repository.