software-mansion/argent

argent-screen-recording

Record a video of an iOS simulator or Android emulator/device screen using argent MCP tools.

View source

How to use

  1. Copy the installation command and review the source package before installing it in your own agent environment.
  2. Check the source document for required tools, credentials and supported hosts.
  3. Describe your input and desired deliverable; review the output against the source material.
npx skills add https://github.com/software-mansion/argent --skill argent-screen-recording

Before you start

  • Installation does not include a model subscription, API allowance or permission to access your files.
  • Repository stars and installation counts describe activity, not an independent quality or security test.
Original skill document

Rendered from the source repository. Headings, examples, code, tables, links, and referenced images are preserved.

screen-recording-start and screen-recording-stop carry the options (timeLimitSeconds, trimStatic, showTouches) and the result fields. One recording per device at a time; different devices can record concurrently.

1. Critical: never leave a recording running

A forgotten recording keeps capturing until its timeLimitSeconds cap fires, holding the session and delaying the video. Use both safety nets:

  1. Set yourself a reminder the moment the recording starts, for the expected end of the interaction. Use whatever your harness provides: a reminder/wakeup or scheduled-task tool if you have one, otherwise a background shell running sleep <expected-seconds> whose completion notification pulls you back. When it fires, call screen-recording-stop. Do not rely on remembering.
  2. Read the tool-result notes. While a recording runs, every argent tool result carries a NOTE: about it. If the note says the recording already ended, still call screen-recording-stop: that is what hands you the file.

2. Workflow

  1. Get the device booted and the app into the state the video should open on (list-devices, launch-app, argent-device-interact).
  2. Call screen-recording-start with udid and a timeLimitSeconds slightly above the expected interaction length.
  3. Set the end-of-recording reminder from §1; this step is not optional.
  4. Drive the interaction (argent-device-interact). Prefer run-sequence for tight multi-step interactions so tool-call latency does not pad the video.
  5. Call screen-recording-stop with the same udid. Check warning (cap-triggered stop, early encoder exit, dropped frame stream, possibly truncated file) and confirm the file has a sane size before presenting it.

Where the file lands. A finished recording is saved durably on the client, even with a remote argent link tool-server: into <project>/.argent/recordings/ (the nearest ancestor of the client's working directory with a .git/package.json/.argent), or ~/.argent/recordings/ outside a project. Change it with argent config set recordings.directory <dir> (--scope project for a per-repo choice). Mention the path to the user, and that the file is untracked: add it to .gitignore or clean it up if it shouldn't be committed.

3. Platform notes and limits

  • Recordable: iOS simulators (local and remote remote:), Android emulators and physical Android devices. Unsupported: physical iPhones, tvOS simulators, Chromium apps, Vega/Fire TV and HarmonyOS. For a still frame use screenshot; for a replayable interaction script use argent-create-e2e.
  • One size per video: the video keeps the size of the screen at the start; a later size change is letterboxed. On a foldable simulator, start recording on the panel you need at full size.
  • Remote (`remote:`) simulators: the video keeps the screen's portrait orientation, so a device in landscape plays sideways.
  • Android: secure screens (DRM, some password fields) come out black.
  • Watermark: a faint Argent logo is stamped bottom-left. Turn it off with argent disable video-watermark; the flag is read when a recording starts.
from this repository

More skills

All skills
software-mansion
Community

argent-android-emulator-setup

Set up and connect to an Android emulator using argent MCP tools. Use when starting a new session on Android, booting an emulator, getting a device serial, or before any UI interaction task.

1h installs
6
GitHub stars
3.2K
Updated
Nov 19
software-mansion
Community

argent-create-e2e

Create, record, edit, replay, or repair reusable Argent e2e test YAML files. Use when the user asks to record, replay, or run an e2e test or a repeatable device path, set up profiling or an A/B comparison, or invoke the authoring engine behind argent-qa-e2e. Also use before repeating three or more interactions. For one-off UI checks, acceptance-driven regression tests, or screen video, use argent-test-ui-flow, argent-qa-e2e, or argent-screen-recording respectively.

1h installs
6
GitHub stars
3.2K
Updated
Nov 19
software-mansion
Community

argent-device-interact

Interact with an iOS simulator or iPhone, Android emulator or phone, or Chromium (CDP) app using argent MCP tools. Use when tapping UI elements, performing gestures, scrolling/swiping, typing text, pressing hardware buttons, launching apps, opening URLs, taking screenshots, waiting for an element to appear or disappear, or checking visible app state after interactions. Not for TV targets.

1h installs
6
GitHub stars
3.2K
Updated
Nov 19
software-mansion
Community

argent-ios-device-interact

Drive a physical iPhone through argent. Use when a physical iPhone is involved (a list-devices iOS entry with kind "device") and ONLY then; never for a simulator. For cable, trust, or signing problems read argent-ios-device-setup.

1h installs
6
GitHub stars
3.2K
Updated
Nov 19