iphoneclaw-action-scripts

You can automate remote iPhone control by registering pre-recorded action scripts in a local JSON registry and triggering them remotely via supervisor APIs for governance and debugging. This maps short names to recorded flows for deterministic execution.

The best way to organize iPhone automation scripts is using a local registry that maps short names to recorded actions. Store available scripts in dedicated common and recorded directories to enable deterministic execution and easy reuse.

Yes, you can export action scripts directly from previous recording runs. The system supports recording new flows and exporting scripts from runs, which you can then add to the registry for future automated execution.

Yes, you need a populated action_scripts/registry.json file to map short names to scripts. You also require access to action_scripts/common and action_scripts/recorded directories to resolve names and execute the scripts properly.

A local script registry reduces token usage by mapping short names to pre-recorded actions. Instead of passing full script logic, you call run_script(name=...), which resolves the short name locally and executes the recorded flow.

Action scripts fail to resolve when the registry.json file is missing entries or the script files are absent from the action_scripts/common or action_scripts/recorded directories required for name resolution and execution.