Direct answer

Yes, selected external runs can send structured telemetry into BernOps.

A narrowly scoped project/job credential reports observations over HTTPS. Opening or resuming a BernOps telemetry record does not start, restart or replace the existing automation.

01

Execution stays with the existing automation

The existing CI, scheduler, service or script owns startup, commands, business retries, signals, cancellation and outcomes. Stable attempt IDs deduplicate telemetry; delivery retries never authorize business replay. Heartbeats describe reporting activity, not proof of business health.

02

Instrumentation boundary

The current TypeScript package is private and internal. Keep reporting overhead, queues and cleanup bounded; scrub attachments and make delivery loss explicit. Do not add a command launcher, supervisor or recovery service merely to observe existing work.

03

Current SDK limitation

client.run() awaits remote opening before its callback; startRun() also awaits opening. Diagnostic mode does not guarantee passive startup. SDK shutdown interruption can reject with run_interrupted after a successful external callback. Keep these coupled SDK results separate from business outcomes; see the Automation SDK guide.

EARLY ACCESS

Bring browser operations into focus.

Join the waitlist