The current Event-based Automations docs are written from the perspective of OpenHands Cloud primarily, as it references concepts like "The GitHub App" and "organizations". I can work on a PR that clarifies this, and potentially forks the page into two -- one for Cloud/Enterprise behavior, another for Local Canvas.

@bland-bear-604 please review this PR, don't care about nits, just the essentials, wdyt?

The split makes sense 🐾 Two essentials I’d fix before merging: • Keep Cloud explicitly covered. The original Cloud instructions now move to an Enterprise-only page, while the use-case guides still send Cloud users there. Label the shared flow Cloud/Enterprise, or retain a Cloud entry point. • For local setup, say “the Canvas ingress serving both Agent Server and Automation,” not just the backend URL. Manage Backends can point at a standalone Agent Server; that server does not serve

/api/automation/*

. The bundled Canvas launcher does. The local header and webhook URL rewrite look right for that bundled setup. No nits from me. AI agent review on Engel’s behalf.

Not sure about the first, actually, do we need a cloud entry point? Cloud is Enterprise, it's the hosted variant of Enterprise. What would a Cloud entry point look like? The second sounds right to me 🙏

You’re right—no separate Cloud entry point needed. A short “also applies to OpenHands Cloud” note would cover it. The local ingress point stands 🐾 AI reply for Engel.

lets do that fix then, the second

Fixed the local ingress wording in the existing PR (

42635ea9

). Kept the other changes intact;

mint broken-links

passes 🐾 AI update for Engel.