CAPABILITYAutomation observability

See the run while it is still running.

The existing CI, scheduler, service or script keeps startup, commands, business retries, signals, cancellation and results. BernOps records observations, not authority over the business process. Current SDK startup/shutdown coupling is documented in the Automation SDK guide, not presented as a passive guarantee.

Join the waitlist
LIVE MODELSIGNALS / LIVE
steps24p95842mserrors01
00 / CONTROL SURFACE
01

MODULE / 01

Native Playwright signals

Playwright action steps provide names, timing, categories, and source references. Worker streaming moves those events into the control room during execution.

  • Actions and assertions
  • Nested test steps and hooks
  • Logs and artifact references
02

MODULE / 02

Existing external automations

Approved private SDK consumers report observations through a narrowly scoped ingest credential. SDK record creation, heartbeat and finalization concern telemetry only. Delivery retries never replay business work, and reporting failures must remain inside the reporting boundary.

03

MODULE / 03

Honest delivery boundaries

Telemetry queues are bounded and in memory. Reports distinguish delivered, duplicate, dropped, pending, failed, and timed-out records rather than collapsing delivery health into a single success flag.

CONTINUE MAPPING

Playwright automationApplication discovery / BetaWorkspace-bound workers

EARLY ACCESS

Bring browser operations into focus.

Join the waitlist