software-mansion/argent

argent-screen-recording

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

ソースを見る

使い方

  1. インストールコマンドをコピーし、自分の環境へ導入する前にソースを確認します。
  2. 必要なツール、認証情報、対応環境を原文で確認します。
  3. 入力と成果物を指定し、出力を資料と照合します。
npx skills add https://github.com/software-mansion/argent --skill argent-screen-recording

開始前の確認

  • 導入にはモデル契約、API枠、ファイルへのアクセス許可は含まれません。
  • スター数や導入数は活動の指標であり、独立した品質・安全性試験ではありません。
リポジトリの原文

見出し、例、コード、表、リンク、参照画像を含む原文を表示しています。

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.
同じリポジトリから

関連する Skills

すべての Skills
software-mansion
コミュニティ

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.

1時間の導入数
6
GitHub Stars
3211
更新日
11月19日
software-mansion
コミュニティ

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.

1時間の導入数
6
GitHub Stars
3211
更新日
11月19日
software-mansion
コミュニティ

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.

1時間の導入数
6
GitHub Stars
3211
更新日
11月19日
software-mansion
コミュニティ

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.

1時間の導入数
6
GitHub Stars
3211
更新日
11月19日