Control your computer from another device

Can I control my computer through Lyre?

Yes. Lyre has built-in whole-desktop capture and control for Windows and macOS hosts. From an authorized client, open a screen, begin viewing and request control when permitted. A normal native-host installation needs no Docker, VNC server, RDP server or separately installed input helper.

The host computer runs the desktop application; your other device receives its screen and sends permitted input. No project or coding agent is required. Viewing and control have separate permissions, and an App-only viewer cannot open a whole desktop.

Choose the screen or app you actually need

Viewing or controlling a desktop does not attach the screen to a coding agent or grant it screenshot, input or project tools. Agent work still uses its own conversation, context and approvals.

Prepare the host and access

For the first check, use the same trusted network and a harmless application, such as a new unsaved text document. Keep private windows off the selected screen. System dialogs, elevated windows, locked sessions and optional virtual screens have their own host and operating-system requirements; do not assume control of every surface.

Try a harmless view-and-control task

1. Choose the host and screen

   Open Remote desktop, check the computer name, then choose View Whole Desktop or the intended screen under Computer screens. Read any consent prompt before Start viewing. Opening the chooser alone does not start capture.

2. Check viewing before control

   Start in View only. Move a window on the host and confirm that the client shows the change. Input should be refused while viewing only. A connected status without a changing picture does not establish a working media path.

3. Request control explicitly

   On phone, choose Take control; on desktop/browser, choose Control in the viewer's interaction controls. If it is unavailable, read the reason rather than trying to bypass it. Only proceed when the host permits both viewing and control.

4. Type one test line and return to viewing

   In your harmless host application, type Lyre control check from the client. Verify the text on the host. Return to View only and check that further client input is no longer accepted. This is a manual desktop-control check, not an agent task.

Check phone, network and gateway limits

Whole-desktop viewing has its own local and relay connection paths. Away from the local network, native screen media needs a working route and any required host relay entitlement or configuration. A conversation or host-control connection can succeed while screen media fails. Check off-network connectivity and current plan limits, then repeat the view-and-control task on the actual connection you need.

On native iPhone and iPad clients, individual-app streaming is restricted to the host's local network. That restriction belongs to saved app-window streams; generic whole-desktop viewing has a separate local/relay path. Web app previews also have their own delivery and authorization. A working preview does not establish desktop or individual-app availability.

External RDP/VNC gateways are optional and separate. Desktop/browser clients can use a configured saved gateway through its existing owner. It needs its own reachable server and credentials; Lyre does not install that server. The native phone whole-desktop viewer requires Lyre's native capture path and does not substitute a saved gateway. Existing gateway setup.

Recover without expanding access

No screen or the computer is offline

Check the selected host, power, network and whether Lyre is open there. Read its capture or platform error. Restore the host connection, then use Reconnect. Offline recovery.

The picture is black or stops updating

Check capture readiness, macOS recording permission and the media route. A working message connection is not proof of screen delivery. Inspect the actual error before starting another session.

Viewing works but input is refused

Check View only versus Control, the host's separate control policy, operating-system permissions and the target window. View-only input refusal is correct. Do not widen project or App-only access to repair a desktop-control denial.

Another developer is already using the screen

The host permits one Developer native session per screen and one Developer saved-gateway slot. Check the existing session and ask its user to stop when appropriate; do not create another grant as a workaround.

Stop viewing or withdraw authority

Use the viewer's stop or disconnect action to end the screen session; on phone the action is Stop desktop. Read its confirmation. Returning to Agent can retain a desktop session, so use Stop when you intend to end capture. Stopping a screen session does not stop an unrelated agent or your host applications.

The host owner manages desktop viewing and control separately in its permissions and Remote desktop settings. Withdrawing control ends the affected control session; viewing can remain available under its separate permission. To remove that device's connection authority, revoke its relevant grant in Pair device.

After withdrawal, check the existing session and a fresh open attempt on a client that has only the affected grant. Further control must be refused, and withdrawal of viewing must prevent that screen access. Switching your own viewer to View only, closing it or uninstalling a client does not revoke a host grant.