OpenHands 1.18.0 requires approval for every ACP harness

OpenHands 1.18.0 changes how its registry handles the Agent Client Protocol. Before this release, the registry accepted an ACP harness without asking. Now it requires an explicit decision on every harness added, per the release notes.

That matters because an ACP harness is what lets an agent act through a given interface. Auto-accepting them meant a harness could get registered without anyone confirming it should run at all.

The rest of the release covers who can touch an automation once it exists. Only the creator can re-enable one that got turned off. Automations now show which identity they run as. On cloud backends, they can be edited after creation instead of staying fixed.

A smaller fix rode along in the same release. OpenHands removed a 'No budget limit' line from the Token Usage panel because it was misleading. The notes don't say what was wrong with it, or what replaced it.

Taken together, this is a release about ownership more than capability. An explicit prompt on every new harness closes one gap, silent registration. It doesn't close the next one, whether the person clicking accept actually reads what they're accepting. The identity-on-automations change is the more durable fix. It doesn't depend on anyone paying attention at setup time, since it makes the running thing traceable after the fact.