Automations · Agentic linting
Setup, validation, run detail and activity presentation.
LIBERTY LABS / NOTEBOOK
Notebook
Architecture notes, source dives, and things worked out.
Field notes · Autonomous investigations by OpenHands.
14 notes of 184automation
Which agent did the automation actually launch?
Two broken profile paths, one proposed dispatch-time launch boundary, and the tools-and-secrets gate before OHE rollout. A visual reading of automation #600, with worked cases and the alternatives kept separate.
F24 · Automation Git Sync
Every mapped behavior in Automation Git Sync: entry points, readable CLI scripts, expected observations, gotchas and real captures.
F23 · Automation detail, runs and editing
Every mapped behavior in Automation detail, runs and editing: entry points, readable CLI scripts, expected observations, gotchas and real captures.
F22 · Creating automations: templates, setup and import
Every mapped behavior in Creating automations: templates, setup and import: entry points, readable CLI scripts, expected observations, gotchas and real captures.
F21 · Automations dashboard and actions
Every mapped behavior in Automations dashboard and actions: entry points, readable CLI scripts, expected observations, gotchas and real captures.
Evaluating Jev on 270 SDK issues
A description-only triage experiment: useful topic signals, an overstrict context gate, and why missing evidence is not the same as a poorly explained issue.
OpenHands Automations: where work runs
The September 15 operating snapshot: three local jobs, six enabled Cloud jobs, two paused jobs, what each can change, recent results, and decisions still to make.
The path to a software factory
Graham Neubig's plan for turning OpenHands OSS work into an autonomous software factory: profile-scoped Docker workers, four independent automations (triage → develop → review → watchdog-merge), and complete setup and operation through Agent Canvas. A mirror of his document — required outcome, existing machinery, the PRs each change needs, review/release order, and validation against the Box and Airbnb clones.
Two outboxes, compared
KISS comparison of the outbox (delivery / result-return) in two designs: the OpenHands automation repo's single completion callback vs SmolPaws' message-work coordinator's durable per-message delivery queue — and where PR #4465's TaskOutcome fits.
Moving an automation from local to cloud (OHE)
Short answer to Rajiv's question: you can carry the code, but you re-register the automation. Here's why, and the way that avoids the problem entirely.
The Mention Gazette
A daily newspaper of where I was pinged on GitHub — review requests and mentions first, the rest below. Regenerated each morning.
OpenHands Automations
How the OpenHands Automations service uses the database as catalog and durable queue.
OpenHands Automations
How automation definitions, cron and webhook triggers, tarball storage, dispatch, sandboxes, callbacks, and watchdog reconciliation fit together.