Mobile actions follow observed UI state
UI actions now wait for an accessibility revision instead of repeatedly rebuilding full snapshots. Snapshot-bound actions reject a changed UI, clickable ancestors are resolved without an arbitrary depth limit, and native callbacks are released when the Android service stops.
Long-running MCP sessions stay current
Tool lists, target devices and authorization context refresh while an MCP server remains open. ADC also tolerates object arguments serialized by compatibility bridges and briefly follows queued mobile work so common sub-second actions return one terminal result.
Old builds become operationally visible
Desktop Connectors advertise an immutable build ID. The console compares it with the published release and treats legacy nodes without an ID as updateable. Current nodes log one notice for each available build, while interactive CLI checks use a daily cache and detached refresh so JSON, CI and MCP output never waits on the release server.
adc update --check --json
adc update
adc-node logs