Adom Bridge
Public Made by Adomby adom
Adom Bridge unleashes your AI onto your full PC: full power, full safety. The AI breaks out of the container it runs in and onto your real machine, managing and running your entire laptop as you: launch apps, move files, drive any window, control KiCad, Fusion 360 or your real signed-in browser. Works with any AI, cloud or local (Claude Desktop, Claude Code, Codex), no Hydrogen required. Bridge and its bridges are an operating system for AI, with managed Node and Python runtimes, and a human-onl
desktop_record_start ignores keep and never reports kept (recordings cleanup can delete a long take)
What happens
desktop_record_start accepts no keep option, and its answer has no kept field. Hydrogen 1.0.659+ sends keep: true on every native screen take so ab's recordings cleanup (3 GB / 2 days) cannot delete a long take before Hydrogen collects it (adom/hydrogen#128: a 32-minute take was deleted). Hydrogen's code assumed ab 2.1.175+ honours keep, but no ab version does: on ab 2.1.184 (ConfRoomROG, 2026-10-21) the start answers only data {path, recordingId, width, height, kind}.
Repro (any box with ab 2.1.184):
adom-bridge desktop_record_start '{"monitor":"primary","fps":30,"audio":false,"maxDurationMs":20000,"keep":true,"reason":"keep test"}'
The answer has no kept, and the take is not exempt from the cleanup.
Asking for
desktop_record_start {keep: true}(anddesktop_record_window_start): exempt that take's file from the recordings cleanup untildesktop_record_stopreturns, or until it is deleted by the caller.- Answer
kept: truewhen it is honoured, so a caller can tell an ab that supports it from one that ignores it.
Hydrogen's promotion gate check native-recording-keep-relaunch requires kept: true and stays blocked until this lands. Hydrogen side is already wired: it sends keep and reports ab's kept as is.