Tools
OpenHands 1.18.0 forces an explicit decision on every ACP harness its registry adds
The 2026-09-11 release includes PR #17228, which stops the registry from silently accepting an ACP (Agent Client Protocol) harness and requires an explicit decision for each one. The rest of the release is automation ownership: only the creator can turn an automation back on, automations show which identity they run as, and they can be edited on cloud backends. A misleading "No budget limit" line was removed from the Token Usage panel.
Source
↳ Follow the thread