You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit 3b6a9f7
Browse filesBrowse the repository at this point in the historyBrowse files
fix(settle): settle on the full tree after a full snapshot
Address review: listing only additions against a full-tree baseline still
reported the keyboard window as added, because the interactive view reads
windows the full tree does not. A settle on refs from a full snapshot now
captures the full tree too, so its diff compares one view and issues
full-tree refs. The removals flag, hint and formatter change are gone.
Co-Authored-By: Claude Opus 5.5 <[email protected]>
'The UI kept changing for the whole settle budget (animation, carousel, or ticker?), so no settled diff is shown. Raise --timeout, wait for specific content, or take a fresh snapshot.';
82
82
83
-
constFULL_VIEW_BASELINE_HINT=
84
-
'The previous snapshot was a full tree and settle reads the interactive view, so this diff lists only added lines; removals are not listed. A settle on refs from this response compares interactive views.';
85
-
86
83
constSETTLE_CAPTURE_STALLED_HINT=
87
84
'A snapshot capture stalled past the settle budget, so no settled diff is shown. The action itself succeeded; observe with wait stable or snapshot.';
88
85
@@ -210,16 +207,13 @@ async function readSettledOutcome(
Copy file name to clipboardExpand all lines: website/docs/docs/commands.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -494,7 +494,7 @@ agent-device gesture tap 80 300 200 450 --count 20 --pause-ms 100 # repeated two
494
494
495
495
If rotation stops repeated iOS presses, inspect the screen before continuing with the remaining presses.
496
496
497
-
A successful `click` or `press` means the action was sent to where the command found the target. It does not confirm that the element received it or that the screen changed. When the next step depends on it, add `--verify` (reports `changedFromBefore`), add `--settle` (returns the diff once the UI goes quiet), or follow with `wait <selector>`. The settled diff compares interactive views. After a full `snapshot` (no `-i`), a `--settle` action on one of its `@ref`s has no interactive baseline. That settle lists only added lines, sets `diff.removalsOmitted`, and says so inits hint. A settle on refs from that response compares interactive views. On iOS, a row the interactive view rewrites can still be listed as added. Before retrying a failed interaction, see [Retry after a failed command](#retry-after-a-failed-command).
497
+
A successful `click` or `press` means the action was sent to where the command found the target. It does not confirm that the element received it or that the screen changed. When the next step depends on it, add `--verify` (reports `changedFromBefore`), add `--settle` (returns the diff once the UI goes quiet), or follow with `wait <selector>`. After a full `snapshot` (no `-i`), a `--settle` action on one of its `@ref`s reads the full tree too, so its diff compares one view and its refs are full-tree refs. Before retrying a failed interaction, see [Retry after a failed command](#retry-after-a-failed-command).
498
498
499
499
A `click` or `press` whose target the daemon resolves to a point (`@ref` or selector) re-checks that target's position before dispatching when the session's previous action animated the screen, and dispatches where it came to rest. When that check cannot confirm a stable position — the target was still moving, or a re-check could not measure it — the command refuses with `target_still_moving` and `dispatched: no`: nothing was dispatched, the point the command resolved is in `error.details.rect`, and where the target was last seen is in `error.details.movedToRect` when that last look measured one. Run `wait <selector>` on the target and retry the same command, or add `--settle` so the action waits for the UI to go quiet. A refused `@ref` press needs a fresh `snapshot -i` and a selector, because the wait retires the ref. Two dispatch paths hand off before the check: a press at raw coordinates has no resolved target to re-check, and a dispatch the backend performs on the element itself — `click @ref` on a backend with element dispatch, or a Maestro non-hittable coordinate fallback — goes to that backend rather than through a resolved point. The re-check stops when the request is canceled or reaches its deadline, and nothing is dispatched (`dispatched: no`): a canceled request fails with `details.reason: request_canceled`, and a request out of time with `details.reason: daemon_request_timeout`.
0 commit comments