I have some event based automations that are now failing. I think its due to the updates. Still tracking it down, but this is what it's tell me now: A platform regression hit overnight (June 10 → 11). The preset API creates automations with .venv/bin/python main.py. The venv's setup.sh installs the OpenHands SDK fresh on every run. A recent SDK update removed rollout_entrypoint from the observe() method — but the generated main.py still calls observe(rollout_entrypoint=...). Any automation that ran a fresh setup.sh after the update hits this immediately.

Seems like code review agent is also broken 😅 https://openhands-ai.slack.com/archives/C0A6U0HTD7X/p1781195782622539 So event based automation definitely seems to be breaking

I think the code review agent breaking predates this regression.

Here's the report you can send directly to the OpenHands team:

Title: All venv-based automation runs broken since Jun 10 —

lmnr 0.7.53

removed

rollout_entrypoint

from

observe()

Affected: All automation runs using

.venv/bin/python main.py

on app.all-hands.dev

Error:

observe() got an unexpected keyword argument 'rollout_entrypoint'

Root cause:

openhands-sdk 1.22.1

calls

lmnr.observe(rollout_entrypoint=...)

in its observability wrapper (

openhands/sdk/observability/laminar.py

).

lmnr 0.7.53

(released Jun 10 @ 21:05 UTC) removed that parameter without a major version bump. The automation

setup.sh

installs

openhands-sdk==1.22.1

with

lmnr>=0.7.47

unpinned, so

uv pip install

now resolves to

lmnr 0.7.53

.

Fix: In

setup.sh

, add

lmnr==0.7.52

to the install command, OR update

openhands-sdk

to match `lmnr 0.7.53`'s API.

Verification:

lmnr 0.7.52

—

lmnr/sdk/decorators.py

line 37:

rollout_entrypoint: bool = False

✅.

lmnr 0.7.53

— parameter gone ❌.

Unaffected: Automations created before ~May 2026 using

python main.py

(system Python) still run fine because system Python has an older SDK install that predates the

lmnr>=0.7.47

requirement.

I think the Laminar pin we just merged should fix it?

Workaround: swapping the preset-generated tarball (which uses

uv venv

+

uv pip install

) for the older system-

pip

tarball format.

@nutritious-balloon-65098 Look into the links above, and open a SDK PR to pin Laminar there too just like we did in extensions (get yourself the latest merges in extensions repo if you need)

I'm on it! can track my progress here.

approved! is someone able to take point on patch releasing the sdk so we can ship the fix to cloud automations asap

Just ran into this same problem

Cloud automations should be working again

Confirmed works!