1. Tools screen-recording-start — start capturing the screen of a booted device to a video file. Frames come from the same simulator-server backend that screenshot and the interaction tools already use, and are encoded live to h264 mp4 (constant 30 fps, device-native resolution). screen-recording-stop — stop the capture, finalize the container, and retrieve the video as a downloadable artifact ( video.hostPath for co-located clients). One recording per device at a time; different devices can record concurrently. Recording does not disturb anything else reading the device — a preview window can stay open on the same screen.
2. Critical: never leave a recording running A recording does not stop itself before its timeLimitSeconds cap, so a forgotten one keeps capturing until the cap fires — holding the recording session, wasting disk, and delaying the video you are waiting on (and with trimStatic: false it comes back padded with dead air). Two safety nets exist — use both: Set yourself a reminder the moment the recording starts. You know the expected capture length (the interaction you are about to drive). Immediately after screen-recording-start returns, schedule a wake-up for that expected end time using whatever your harness provides — a built-in reminder/wakeup or scheduled-task tool if you have one, otherwise a background shell running sleep whose completion notification pulls you back. When it fires, call screen-recording-stop . Do not rely on remembering. Read the tool-result notes. While a recording is running, every argent tool result carries a NOTE: reminding you it is still going and how to stop it. If the note says the recording already ended (time limit hit), still call screen-recording-stop — that is what hands you the file.
3. Workflow Show more Installs 857 Repository software-mansion/argent GitHub Stars 1.8K First Seen 8 days ago Security Audits Gen Agent Trust Hub Pass Socket Pass Snyk Pass