export interface AutomationExecuteOptions {
    apiUrl?: string;
    workerId?: string;
    jobFile?: string;
    defaultAgentKind?: string;
    context?: string;
    debug?: boolean;
}
/**
 * `lobu automation execute` — run one already-claimed device Automation.
 *
 * The device daemon (`lobu daemon`) claims and executes in one process. A
 * native bridge cannot: the Owletto Mac app must keep its own poll loop for the
 * platform connectors only it can serve, and a poll claims whatever the server
 * returns — including Automation runs pinned to that device. Rather than a
 * second poller racing the first on the same device row, the bridge stays the
 * only claimer and pipes the run here.
 *
 * Exit status IS the handoff contract, because both sides can otherwise report
 * the same run:
 *   - 0  → this command owns the outcome. It posted the exit report, or
 *          deliberately left an undeliverable one to the server's heartbeat
 *          sweep. The caller must not report.
 *   - !0 → nothing was reported and the run is untouched. The caller still owns
 *          it and must post its own failure, or the run sits `running`.
 * An older CLI without this command exits non-zero too ("unknown command"), so
 * a version-skewed caller falls into the safe half of the contract.
 */
export declare function automationExecuteCommand(options: AutomationExecuteOptions): Promise<void>;
//# sourceMappingURL=automation.d.ts.map