Windows Node and Android Node are in testing. They are available to try, but compatibility and reliability are still being validated. An available installer does not mean every system, phone model or operation has been verified.
Mobile actions follow observed UI state
A mobile agent inspects the screen, chooses a control and clicks it. Between inspection and action, a dialog can open, a list can move, or another app can become active. This release tightens the relationship between an action and the UI the agent observed, while reducing repeated full snapshots during a wait for change.
Snapshot-bound actions reject a changed UI. After a stale-state rejection, inspect again and select the target from the new observation. Repeating an old click without a fresh observation can still address the wrong control. For a workflow such as opening Settings, verify the foreground app and resulting screen before proceeding.
The implementation waits for Accessibility revisions, resolves clickable ancestors without an arbitrary traversal-depth cutoff, and releases native callbacks when the service stops. This improves action handling; it does not remove local permission requirements or make every app expose a complete semantic UI. Android Node remains in testing.
Long-running MCP sessions stay current
An MCP client can stay open for hours while devices reconnect or the owner changes an Agent access. A cached tool list can show an unavailable device, omit a new tool or encourage a call that the current grant denies. Long-running MCP sessions now refresh tools, targets and authorization context while the server remains open.
Discovery refresh does not replace invocation authorization. The service still checks each request and the device retains its local limits. After a permission change, inspect the refreshed list and make a small read-only call. If the client itself caches tools indefinitely, reconnect that client to discover the current surface.
A malformed MCP request and a denied request need different fixes. Check the request format for the former and the grant for the latter. Expanding access is not a remedy for a transport or schema error.
Find outdated devices without blocking work
The console shows installed and available desktop versions, including the last reported version of an offline device. This helps locate old installations but does not prove reachability. CLI update checks remain advisory so a version lookup does not block ordinary commands.
Run adc update on the relevant installation and then adc-node status. Confirm the version, service origin and online state, followed by one tool call through the agent connection. If the new version is installed but the device stays offline, check startup, credentials and outbound connectivity before reinstalling.
Windows Node also remains in testing. New installations should use the current release; this historical article explains the change, while the Connector guide maintains current setup and recovery instructions.
adc update --check --json
adc update
adc-node status
adc-node logs