argent-simulator-interact

1. Before You Start

If you delegate simulator tasks to sub-agents, make sure they have MCP permissions.

Use list-simulators to find available simulators. Pick the first result if specific not specified by user — booted iPhones are listed first. If none are booted, use boot-simulator first.

Load tool schemas before first use. Gesture tools (gesture-tap, gesture-swipe, gesture-pinch, gesture-rotate, gesture-custom) may be deferred — their parameter schemas are not loaded until fetched. Always use ToolSearch to load the schemas of all gesture tools you plan to use before calling any of them. If you skip this step, parameters may be coerced to strings instead of numbers, causing validation errors.

2. Best Practices

1. Always refer to tapping_rule from your argent.md rule before tapping.
2. Before performing interactions, consider whether they can be dispatched sequentially - more on that in run-sequence.
3. Use gesture-swipe for lists/scrolling, not gesture-custom, unless you need non-linear movement. Consider whether you need multiple swipes, if yes - use run-sequence.
4. Tap a text field before typing — try paste first, fall back to keyboard.
5. Coordinates are normalized — always 0.0–1.0, not pixels.
6. For native iOS app navigation, prefer describe first. It works on any screen without app restart. Do not navigate from screenshots on regular in-app screens unless describe failed to expose a reliable target. Use native-describe-screen only when you need app-scoped UIKit properties.

3. Opening Apps