Connect another computer, authorize workspaces, run tasks remotely, and view results.
When your project or runtime is on another computer, connect to it from the Qoder desktop app to send tasks and follow their progress and results. This guide calls the computer that starts the connection the controlling device, and the computer that runs the task the remote device.
Both devices must use the same product and run Qoder with device connection support. Keep the remote device online and awake with Qoder running during tasks. To control the desktop app from a phone or web browser, see Remote control.
Choose a connection method based on the accounts and networks used by the two devices:
Both devices must be reachable over the LAN and have internet access to generate and verify the pairing code. Accounts in different organizations cannot pair.
On the remote device, open Settings → Remote devices → Allow connections to this device, find the controlling device in the authorized devices list, and edit its permissions.
Open the remote task from the controlling device's sidebar to see its synced status, execution steps, and file change counts. When the task finishes, the controlling device shows an unread indicator and a notification.
Task records remain on the execution device. For tasks with a workspace, files remain in that remote workspace. From the controlling device, view synced files, images, and remote web pages, and use the terminal and Git where supported. Supported Office files can be previewed, edited, and saved from the controlling device; see Office Plugins for file workflows.
When the device is online and supports read-state sync, reading a task or marking it unread syncs to other authorized devices. Offline read marks stay local; after reconnecting, the execution device's state takes precedence.
If an output is missing, check that the task has finished and Qoder is still running on the remote device, then refresh the task results.
If the remote device supports workspace creation and grants the required permissions, select that device in the workspace creation flow and choose one of its folders. Confirm the device and path before creating the workspace. Files are still handled by the remote device.
If the connection drops during creation, reconnect and check the workspace or task list to see whether creation succeeded before retrying.
If no project directory is needed, choose No workspace on a remote device that supports it. Remote tasks without a workspace do not support live voice, Agent Team, Issue, Agent delegation, or creating a workspace from within the conversation.
Type
Supported remote conversations can use an authorized connection to operate the controlling device's Qoder built-in browser. Files and commands still run on the task's execution device. This does not connect external Chrome or grant file access to the entire controlling device.
To run a task on a schedule, create an automation from the
The Qoder desktop app can connect to a compatible CLI Bridge already running on the same computer or on a device reachable over your LAN. After connecting and authorizing access, select the CLI device to open a workspace or task it provides. File, Git, and terminal operations run on the CLI device and depend on the capabilities and access it grants.
View the remote device's reported system information under My devices. Latency and direct or relay connection status appear when measurements are available.
Cached conversations remain readable after disconnection. A local task can also reference cached content from an offline device while its identity and authorization remain valid. The cache may be outdated; the remote device must reconnect before it can accept more tasks.
Connect a device
Choose a connection method based on the accounts and networks used by the two devices:
| Method | Use it when | What you need |
|---|---|---|
| Same-account connection | Both devices use the same account, including on different networks | Allow control enabled on the remote device |
| LAN pairing | Devices use different accounts in the same organization, or same-account devices need manual pairing | LAN reachability, the remote device address, and an eight-digit pairing code |
Connect with the same account
- On the remote device, open Settings → Remote devices → Allow connections to this device and turn on Allow control.
- On the controlling device, open Settings → Remote devices → Connect to other devices.
- Select the target under Available devices and connect. No address or pairing code is needed.
- After connecting, find the device in the sidebar and check workspace and conversation access.
Pair over the local network
Both devices must be reachable over the LAN and have internet access to generate and verify the pairing code. Accounts in different organizations cannot pair.
- On the remote device, open Settings → Remote devices → Allow connections to this device. In the manual LAN pairing area, get the device address and generate an eight-digit code.
- On the controlling device, open Settings → Remote devices → Connect to other devices and choose LAN pairing. If the client shows Add device, open it and select the LAN option.
- Enter the remote device address and code, then pair and connect. The code is hidden by default and can be used once. Generate a new one if it expires.
- Authorize workspaces and conversations on the remote device before opening a workspace from the controlling device.
Check workspace and conversation access
On the remote device, open Settings → Remote devices → Allow connections to this device, find the controlling device in the authorized devices list, and edit its permissions.
- Grant access to all workspaces or selected workspaces. All workspaces includes future workspaces, tasks without a workspace, and the ability to browse local folders and create workspaces. Selected workspaces includes only checked items. SSH workspaces and workspaces on other devices cannot be shared with this device.
- Choose the conversation sync scope. Enable syncing all conversations in the selected scope, or turn it off to sync only conversations started by this controlling device.
- Save, then open an authorized workspace from the controlling device's sidebar. If a project is missing, check the selected workspace scope on the remote device.
These settings control which workspaces and conversations are exposed; they do not provide file system security isolation. Remote tasks run as the remote device's local user and may still access other files or conversations. Also manage the Agent's task actions through Access permissions.
Send your first remote task
- Select the remote device in the controlling device's sidebar, open an authorized workspace, and start a new task. The new task uses the selected device.
- Describe the goal and add attachments or context as needed. Before sending, you can browse remote files, open an available terminal or built-in browser, and upload attachments. Retry failed transfers in the draft.
- Choose a model, permission mode, and Agent from the options provided by the execution device. Agent directories on other devices are read-only.
- Check the execution device and workspace shown for the task, then send the message. File operations and terminal commands run on the remote device.
View progress and results
Open the remote task from the controlling device's sidebar to see its synced status, execution steps, and file change counts. When the task finishes, the controlling device shows an unread indicator and a notification.
Task records remain on the execution device. For tasks with a workspace, files remain in that remote workspace. From the controlling device, view synced files, images, and remote web pages, and use the terminal and Git where supported. Supported Office files can be previewed, edited, and saved from the controlling device; see Office Plugins for file workflows.
When the device is online and supports read-state sync, reading a task or marking it unread syncs to other authorized devices. Offline read marks stay local; after reconnecting, the execution device's state takes precedence.
If an output is missing, check that the task has finished and Qoder is still running on the remote device, then refresh the task results.
Choose a workflow for your task
Create a remote workspace
If the remote device supports workspace creation and grants the required permissions, select that device in the workspace creation flow and choose one of its folders. Confirm the device and path before creating the workspace. Files are still handled by the remote device.
If the connection drops during creation, reconnect and check the workspace or task list to see whether creation succeeded before retrying.
Work without a workspace
If no project directory is needed, choose No workspace on a remote device that supports it. Remote tasks without a workspace do not support live voice, Agent Team, Issue, Agent delegation, or creating a workspace from within the conversation.
Delegate from a local task
Type @ in a local task, search by device name or full workspace name, and select one or more workspaces on connected devices. Qoder creates tasks on those devices while the current conversation stays on its original execution device. Offline devices cannot be selected as delegation targets.
Use the browser and automations
Supported remote conversations can use an authorized connection to operate the controlling device's Qoder built-in browser. Files and commands still run on the task's execution device. This does not connect external Chrome or grant file access to the entire controlling device.
To run a task on a schedule, create an automation from the / entry in the corresponding remote device conversation. That device manages the automation.
Connect a CLI device
The Qoder desktop app can connect to a compatible CLI Bridge already running on the same computer or on a device reachable over your LAN. After connecting and authorizing access, select the CLI device to open a workspace or task it provides. File, Git, and terminal operations run on the CLI device and depend on the capabilities and access it grants.
Manage connected devices
View the remote device's reported system information under My devices. Latency and direct or relay connection status appear when measurements are available.
- Change or revoke access: Edit permissions or revoke access in the remote device's authorized devices list. Revoking access disconnects the controlling device immediately. Turn off Allow control to prevent new same-account connections.
- Remove a device from the list: Removing a device on the controlling device affects only that device's list. Manage authorization on the remote device.
- Update the remote device: The remote device must allow remote Qoder updates. Updates require a restart; Qoder will not restart while tasks are running or files are unsaved. Check the work state, follow the update prompts, and wait for the result. A submitted request alone does not confirm completion if connectivity is lost.
Handle disconnections and connection problems
Cached conversations remain readable after disconnection. A local task can also reference cached content from an offline device while its identity and authorization remain valid. The cache may be outdated; the remote device must reconnect before it can accept more tasks.
| Problem | What to check |
|---|---|
| A same-account device is missing | Check that both devices use the same account, Allow control is enabled on the remote device, and the network and clients support discovery. If discovery is unavailable, pair manually when the devices can reach each other over the LAN. |
| LAN pairing fails | Check the address, network reachability, and system local network permissions. Generate a new code if the previous one expired or was used. Diagnostics do not guarantee reachability behind a VPN, virtual adapter, or firewall. |
| The device connects but no workspace appears | Check the workspace scope in the remote device's authorized devices list, especially after initial pairing between different accounts in the same organization. |
| The connection drops after wake, an IP change, or a network switch | Wait for automatic reconnection. If authentication fails, follow the prompt to authenticate or connect again. |
| The task is not running | Check whether the remote device is asleep or off and whether Qoder is running. Quitting Qoder on the remote device stops its tasks. Reconnect and check the original task before resending. |