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.

Share a device with people you choose

Connector 0.1.5 (October 31) added teams with per-member device policies and sharing with one named account. You pick exact folders, tools and approvals; the device keeps its owner, and every person still authorizes their own agent.

Shared work runs read-only, in a temporary Linux container with no network, or directly on the host after you explicitly trust that person on the device.

For example, an engineer can share an existing project environment so a colleague's agent can inspect it. A team can reuse the same build machine without installing a separate agent on that target. Create a team and member policies, or send a named invitation; each recipient accepts and creates their own Agent access.

The modes have different effects: read-only does not run commands; isolated execution discards workspace changes after each call; trusted host work can change the real device. Choose the mode before granting tools. Linux isolation needs Docker with seccomp and a digest-pinned image, and cannot use a whole filesystem root.

Configure teams and sharing

Share a whole root with a team

Connector 0.1.6 (November 1) lets a team share a device's exposed / or drive root, so you no longer need to add a separate project folder. Member policies and each Agent access still narrow it. External users continue to receive specific folders.

The console now shows the current and available Connector version for every device, including offline ones. Root sharing needs Connector and CLI 0.1.6, SDK 0.2.2 or the updated plugins.

Update the relevant Connectors first, then explicitly select the exposed root in team sharing. This release does not give every team member full device authority. Smaller project folders remain appropriate for isolated execution. Windows Node and Android Node are still in testing; Android does not provide the desktop root-sharing toolset.

adc update --check
adc update
adc-node status
Update and inspect the Connector

Follow shared work the same way

Calls on shared devices return the same jobId, approval and receipt states as your own devices. If both you and the device owner require approval, both must approve before it runs.

A wait ending does not mean the job failed. Keep the returned jobId and wait again; do not submit a replacement command. Revoking a share stops further access, but cannot undo changes already made in trusted host mode. Verify a read-only shared call before granting the tools for the real task.

adc invoke task.wait --args '{"jobId":"job_example","waitMs":4000}' --json
Waiting and task states