Real hardware. Measured results.
Give an AI agent eyes and hands on a machine.
When software access stops, the machine is still there. Bootscry gives an agent a way to see and act through physical interfaces, including before the operating system starts.
Working now: Bootscry has been used on nine machines in one lab, from a NAS boot loop to a BIOS change on a Windows mini PC to bringing up two ARM boards. Every use, failures included, is on the usage page. The BIOS key timing was measured on one machine, and exact typing and mouse placement on running Linux. A Debian install and a rescue-card boot are recorded sessions. A second KVM, the Sipeed NanoKVM, has had first runs, and a Dell iDRAC9 screenshot driver has run on one server. Serial, camera, and more are on the roadmap.
Second machine
The same rescue card on another machine
Both videos on this page are made from recorded sessions with the bootscry video tool. Near-duplicate frames are folded into one held frame, shown for at most 1.6 seconds. LAN addresses and host names are painted out.
estate-diag and mount-estate-disks, then back to the installed system.Record and limits ↗One recorded run on one machine. It includes no pass count from a verify script.What we have measured
The proof you can inspect
One physical Comet test bench. Results have methods and limits attached; they are not claims for every device.
A shared interface
Several ways in. One honest status for each.
Video KVM
Comet supplied frames and timed keys in BIOS. Exact typing and mouse placement were measured on running Linux. A NanoKVM has had first runs; other KVMs await drivers or physical tests.
Serial console
Exact console text from prepared machines, with no OCR in the path.
Camera and audio
See a screen, indicator, or rack from the outside; listen or speak when hardware allows.
Input and management
HID-only input paired with feedback, and server management interfaces. A read-only iDRAC9 screenshot driver has run on one server.
MCP tier gates, approval and audit controls are implemented and mock-tested; the read tier has also run on the real Comet. Every input returns a fresh look at the screen. Physical input, media, and power validation through MCP remains pending. Read the safety design.
Who it is for
A machine can fail before your software can help.
For systems engineers, operators, and agent developers, Bootscry grew out of a NAS recovery that raised a practical question: could an agent use the same physical clues and controls a human operator would use when the operating system is unavailable?
The operator account explains the incident and its attribution limits. The Comet results above are separate, measured experiments.
See how Bootscry works ↗Applied AI research
Agents that observe, install, and recover physical machines
Bootscry studies how agents use screen observations and bounded controls when an operating system is unavailable. The evidence includes ODROID-M1S ARM board bring-up and rescue tests, older x86 PC installation and recovery, and an operator-reported NAS recovery. These are individual records with failures and manual interventions, not an autonomous success rate.
The operator also confirmed a Libre Computer Le Potato setup. Its card was prepared and verified on another host; the Bootscry payload-delivery path was not used. Read Cisco Caceres's research agenda and planned controlled studies.
Try it with us
Have a machine, a KVM, or a hard recovery problem?
The Comet reference implementation is private while we complete its safety and release review. Tell us about a machine you control and we can discuss an assisted pilot or hardware evaluation.