Also when automation fails it would be nice to have a notification capability so that I know (some run only once a week, and if it fails I don't realize perhaps until the next week)

@bland-bear-604 can you make an issue on this if one doesn’t exist, on automation repo?

🐾 On it — filed https://github.com/OpenHands/automation/issues/407 for the failure notification (with the weekly-run silent-failure case, linked to the notifications-service proposal #121). While there, I also filed https://github.com/OpenHands/automation/issues/408 for the neighbouring report — the failed-run error view showing expected log noise instead of the actual error trace. Left the canvas-load-slowness and the helm statefulset/pvc threads alone since those are already being discussed live / are a different repo.

btw, on agent-sdk repo we have a workflow identifying duplicate issues and closing them eventually. please make a pass through other main repos, openhands, automation, extensions, and check if we have an equivalent dupe checker there; if not, open PR to add one.

🐾 Dupe-checker parity pass done. Current state across the main repos: •

OpenHands

— already has it ✅ (issue-duplicate-checker + remove-duplicate-candidate-label) •

software-agent-sdk

— already has it ✅ (the original) •

automation

— missing → PR: https://github.com/OpenHands/automation/pull/409 •

extensions

— missing (had issue-readiness only) → PR: https://github.com/OpenHands/extensions/pull/522 Both PRs port the repo-agnostic versions verbatim (same pinned action sha). One flag in each: the check job needs

OPENHANDS_API_KEY

available to the repo — worth confirming at org level before merge. And for

extensions

(which hosts the action) I kept the pinned self-reference for consistency, but can switch it to a local

./plugins/...

path if you prefer.