> For the complete documentation index, see [llms.txt](https://docs.tryorchard.dev/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.tryorchard.dev/cli/live-device-access/screen.md).

# scrcpy, VNC & screen

Live, interactive screens. The CLI bridges the right channel to a local port and launches the matching viewer, falling back to printing the address if the viewer isn't installed (see [Installation](/cli/install.md)).

## scrcpy, Android

```bash
orchard scrcpy my-pixel
```

Bridges adb to an ephemeral local port, `adb connect`s it, and launches `scrcpy -s 127.0.0.1:<port>`, full video + input. Android providers only.

## vnc, iOS VM

```bash
orchard vnc frida2
```

Bridges the guest's RFB (VNC) server to a local port and opens a VNC viewer (password shown). iOS **VM** (vphone) only, the iOS *simulator* has no VNC, and Android has no RFB (use `scrcpy`). `orchard vnc` on those prints a clear pointer.

## screen, auto

```bash
orchard screen my-pixel
```

Picks the right view for the platform: Android → scrcpy, iOS VM → VNC, iOS simulator → a saved screenshot.

## WebRTC, browser

```bash
orchard screen my-pixel --webrtc
```

Prints the control-plane WebRTC signaling URL and, if it can find the standalone player (the `orchard_agent` package, or `ORCHARD_WEBRTC_PLAYER`), opens it in your browser with the URL prefilled. WebRTC's media peer is the browser, so the CLI hands off the URL rather than decoding frames itself; the Orchard console's screen panel is the other way to watch it.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.tryorchard.dev/cli/live-device-access/screen.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.