Hey self-hosted folks! bufo yay Recently discovered OpenHands via GitHub. To learn how it works by getting my hands dirty, I spun up a self-hosted server using the docker image

<http://docker.openhands.dev/openhands/openhands:1.8|docker.openhands.dev/openhands/openhands:1.8>

. From there, a question popped up regarding GitHub integration: how do you guys usually integrate a self-hosted instance with GitHub? For instance, on the Cloud version, I can just mention

@openhands

and it works directly inside a GitHub issue. In this case, would the right path be creating my own GitHub App to communicate with my self-hosted OpenHands API, or is the common approach using the SDK to talk to my self-hosted instance? This is a bit confusing to me. I found the

openhands-resolver

, but it's archived, and some things in the official documentation page just don't work sadnod

Hey @square-shampoo-59293 Short version: self-hosted OpenHands (the docker.openhands.dev/openhands/openhands image) has no GitHub App / webhook support at all. The Cloud @openhands-in-an-issue experience is powered by All Hands' own hosted GitHub App and is Cloud-only (docs (docs.openhands.dev/openhands/usage/settings/integrations-settings.md)). The docs do point to a "GitHub Action" for label/mention-triggered fixes, but it's broken: it links to openhands/resolver/README.md in the main repo, which 404s, the resolver was folded in from the archived openhands-resolver repo and has since been removed entirely. The standalone openhands-github-action repo is also archived (Oct 2025). A real GitHub-App-based self-hosted flow does exist, but only in the paid Enterprise stack you create your own GitHub App and their Helm chart wires up GITHUB_APP_ID/SLUG/PRIVATE_KEY/WEBHOOK_SECRET for you. For plain OSS self-hosting, two real options: (1) Agent Canvas's "GitHub Repository Monitor" prebuilt automation — PAT + polling via the GitHub MCP server, no App needed, works self-hosted; or (2) a custom solution