How to share devices with Swarmbot when the other user has no phones connected
The owner selects one or more devices in Swarmbot, chooses an expiry and permissions, then sends one share code. The recipient enters that code in their own client and works with the devices within the granted permissions.
Swarmbot Device Sharing lets you temporarily give another Swarmbot user access to phones that are already connected to your computer. It is useful for remote assistance, collaboration across locations and lending test devices: the owner chooses the devices, expiry and permissions; the recipient enters a share code; and the phones appear as shared devices on the recipient's device wall.
You do not need to deploy another device server or expose Android debugging or ACC addresses to the public internet. Select the devices on the Swarmbot device wall and open Device Sharing from the dock to begin.
How the owner creates a share
One share can contain one or several devices. A practical sequence is:
- Filter and select the devices. Check their numbers, models and the selected count so unrelated phones are not included.
- Open Device Sharing. Add a short title when it will help both people identify the session.
- Choose the expiry. The current client offers one hour, one day, seven days and 30 days. Use a short window for temporary help and a longer one only when the work requires it.
- Choose permissions. Control, clipboard, automation, files, app installation, Shell and reboot can be granted separately. Enable only what the recipient needs.
- Generate the code or link. Send it through a private channel trusted by both parties. Do not post a live share code in a public group or webpage.
A share code represents real device access, not just an invitation number. Least privilege matters especially for installation, Shell and reboot. If the recipient only needs to view the screen, there is no reason to enable file or Shell access.
How the recipient connects the devices
Open Device Sharing in the recipient's Swarmbot client, go to the connection area, and paste the code or full share link. Once binding succeeds, the devices join the unified device list and wall with a Shared badge and an expiry time.
The recipient can then open a stream much like a local device. Whether control, clipboard sync, app installation or Shell works depends on the permissions granted by the owner. If a button is unavailable, check the share permissions before treating it as a device fault.
For the first connection, perform three low-risk checks:
- confirm that the device-wall image keeps updating;
- double-click the device and confirm that the stream opens;
- if control is allowed, test Back or Home.
Only after picture and basic control are working should you install apps, transfer files or run automation. If the next task is one app across several shared phones, follow the Swarmbot batch installation guide and still validate on a small sample first.
Where does the device traffic go?
The Swarmbot public platform handles identities, share codes, permissions, expiry and the signaling needed to establish WebRTC connections. It does not act as the ordinary central path for device video, control commands, app packages, scripts or private device-network addresses. The two computers first try to establish a WebRTC peer connection. The official WebRTC documentation explains that signaling lets peers exchange the information needed to connect, while TURN is commonly used when a direct path is unavailable. Read how WebRTC peer connections are established
This creates two possible paths for remote use:
- RTC direct: when both networks permit it, transport runs directly between the owner's and recipient's computers.
- RTC relay: if direct traversal fails, Swarmbot can schedule a TURN node to relay the WebRTC transport. NAT and firewalls are common reasons why a direct socket cannot be established. Read the official TURN overview
Relay does not mean the share has failed, but the longer path makes the experience more dependent on both networks and the relay route. Enable latency details in the stream window to see whether the session is using RTC direct or relay. Do not judge the whole session from one instantaneous millisecond value.
What must remain online on the owner's side?
The shared devices are still provided by the owner's computer. Its Swarmbot client must stay online, and the target phones must remain available. Existing connections are released when the recipient exits, the owner goes offline, the share expires or the owner stops it.
The owner can see shared devices, recipient status and expiry in the share records, and can stop access at any time. The recipient can disconnect the binding. Once a share stops, expires or is disconnected, it should no longer provide access. Create a new share with the right duration and permissions when collaboration resumes.
The device is listed, but there is no picture or control
Check these items in order instead of repeatedly deleting and rebinding the share:
- Public platform status: this tells you whether account and signaling services are reachable.
- Owner online status: a reachable public platform does not prove that the computer providing the devices is online.
- Expiry and permissions: confirm that the share has not expired and that the owner has not stopped it or removed the needed permission.
- Client versions: sharing data channels evolve. If the two versions differ significantly, update both clients before trying again.
- Device diagnostics: right-click the shared device and run diagnostics, then copy the full support report. It records the owner, signaling, RTC, control and video-channel stages for support.
If video works but control does not, focus on control permission and the control data channel. If the device says it is waiting for the owner, check the owner's client rather than looking for a local USB phone on the recipient's computer. The Swarmbot USB, Wi-Fi, ACC and shared-device connection guide explains how the connection types differ.
Can Local API and scripts use shared devices?
Yes. A connected shared device is merged into the recipient's unified device list and receives a virtual device ID that is valid on that computer. Swarmbot UI operations, scripts and Local API calls use that ID for capabilities permitted by the owner.
Do not store the owner's internal device ID or try to bypass sharing with the owner's LAN address. After reconnecting a share, use the ID returned by the recipient's current device list. An external AI or business system can download the matching development documentation from the client; the developer overview explains the roles of scripts and Local API.
A safer collaboration routine
- Decide whether the recipient needs viewing, control or app installation before sharing.
- Select only the relevant devices, grant only the relevant permissions and set a sensible expiry.
- Validate video and control on one device before expanding to the group.
- Keep both clients online and avoid unnecessary network changes during the task.
- Stop the share when the work ends; the recipient can also disconnect it.
- When something fails, copy the diagnostic report and include the time, device number and exact action that failed.
Swarmbot Device Sharing is designed to temporarily hand devices already connected to one computer to another authorized user. Clear scope, permissions and expiry make that arrangement easier to manage than distributing a permanent remote address.