Problem
Currently, session scripts are always saved to ~/.agent-device/sessions/<session>-<timestamp>.ad with no option to specify a custom output path. This requires users to manually copy files after recording if they want to store workflows in a specific location (e.g., a repository).
From the README:
Session recordings are always saved to ~/.agent-device/sessions/. There's no flag to specify a custom output path, so copy the file after recording.
Proposed Solution
Allow --save-script to accept an optional path argument:
# Proposed: with optional path argument
agent-device open com.example.app --platform android --session e2e --save-script ./workflows/my-flow.ad
Problem
Currently, session scripts are always saved to
~/.agent-device/sessions/<session>-<timestamp>.adwith no option to specify a custom output path. This requires users to manually copy files after recording if they want to store workflows in a specific location (e.g., a repository).From the README:
Proposed Solution
Allow
--save-scriptto accept an optional path argument: