Observe the result of a screen action
Android 0.2.7 can return the resulting interface with a screen action when includeObservation is supported by the current tool catalog. A caller can use the returned snapshot for its next decision and avoid a separate interface-read request.
Each action still uses the current screen-control session and a fresh interface reference. Stale or ambiguous targets require a new observation; an unknown result must not be replayed as a new action.
Keep connections and recovery bounded
The Android Node reuses HTTP connections and limits DNS and request time. Updates and reconnection restore the Node and Accessibility binding. User takeover and screen-control expiry continue to stop new screen actions.
A standalone Python GUI executor example is included in the ADC repository. It reuses one public MCP process, verifies bounded goals and supports supervision when a decision stalls. It keeps model time and tool time separate in its execution records.
Update through the official channels
Update the CLI and Desktop Connector to 0.1.8. SDK 0.2.4 is distributed as a versioned HTTPS archive. Android uses its separate 0.2.7 APK channel and preserves the existing testing certificate for in-place upgrades. Android installation remains under the device owner's control.
adc update --check
adc update
adc task wait JOB_ID --wait 4000 --json
adc invoke task.wait --args '{"jobId":"JOB_ID","waitMs":4000}' --json