# Remote hosts Reach your organization's own Unix hosts and Windows desktops from PrivateMind: in the browser, from your own computer with the `pm` CLI, or unattended from CI with a service identity. > [!NOTE] > Remote hosts are turned on per organization. If you don't see **Remote Hosts** under **Compute**, ask your account team. **Remote hosts** let your team open a terminal on your organization's own Unix machines, or a desktop on its Windows machines, through PrivateMind. Access is granted per user and per host. PrivateMind never stores a key to your Unix hosts: each session creates a short-lived key in memory. ## In the browser **Compute → Remote Hosts** lists the hosts you've been granted. **Connect** opens a terminal in the browser. **Server** opens the serial console, where the host's controller allows it. ## From your own terminal (`pm`) Install the CLI once, then sign in and connect: ```bash curl -fsSL https://privatemind.com/pm/install.sh | sh # macOS / Linux # Windows: irm https://privatemind.com/pm/install.ps1 | iex pm login # device code, approved in the browser where you're signed in pm host # list the hosts you can reach pm host # open a shell pm host console # serial console ``` Opening a shell needs a recent sign-in, so a long-lived token file on a lost laptop isn't enough to open a root shell. Run `pm login` again if prompted. For automation, use a [service identity](https://docs.privatemind.com/remote-hosts.html#unattended-access-for-ci-service-identities). ## Windows desktops A Windows machine in **Remote Hosts** is a desktop. Your admin pins the certificate it presents when adding it. If that certificate changes, PrivateMind refuses the connection until they pin it again. ### In the browser **Desktop** opens it in a browser window. **Open full screen** gives it the whole screen and sends keyboard shortcuts to Windows; hold **Esc** to leave. In Chrome or Edge with more than one screen, **Open on all screens** spreads the desktop across them. Click once on each extra screen to show its part. ### In your own RDP client (`pm host rdp`) ```bash pm host rdp # open the desktop in your RDP client pm host rdp --no-launch # start the connection and open the client yourself ``` `pm` opens Remote Desktop Connection on Windows, your app for `.rdp` files on macOS (such as Windows App), and FreeRDP (`xfreerdp3` or `xfreerdp`) on Linux. Sign in to Windows as usual. The connection is encrypted from your RDP client to the desktop, and PrivateMind passes it through without seeing your Windows password. Keep `pm` running while you work; Ctrl-C ends the connection. With `--no-launch`, or when `pm` finds no client, it prints a local address on 127.0.0.1 and an `.rdp` file to open yourself. On Windows and Linux, `pm` refuses connections to that address from other users on the same computer. On macOS it can't tell who connected, so it warns you: use it only on a Mac nobody else signs in to. The `.rdp` file `pm` writes turns off drive and printer sharing, and turns on only what the desktop's switches allow (below). Like `pm host`, it needs a recent sign-in, and it's for people only: service identities can't open desktops. If `pm` reports that the desktop chose TLS 1.3, limit your RDP client to TLS 1.2 or ask the desktop's admin to turn off TLS 1.3 for Remote Desktop. ### Clipboard, file copy, sound, microphone and camera Each Windows desktop has switches for **Sound**, **Microphone**, **Camera**, **Clipboard** and **File copy**. They're off until an admin who can edit the host turns them on, when adding the desktop or under **Edit**. Changes apply from the next session. With **Clipboard** on, the browser desktop copies and pastes text both ways with Ctrl+C and Ctrl+V, in Chrome and Edge. Your browser may ask once for clipboard permission. With **File copy** on as well, it copies files too: drop them on the desktop or upload them, then paste in Windows, and download what you copy there. In the browser PrivateMind allows only what the switches permit, and drive and printer sharing stay off either way. With `pm host rdp`, **Clipboard** turns on clipboard sharing in the `.rdp` file, which in Remote Desktop Connection on Windows covers files as well as text. If your `pm` predates the switch, run the install line again first. PrivateMind can't see inside the encrypted connection, so it can't block what the client shares: the switch only sets what the `.rdp` file asks for. To keep the clipboard or drives off for every client, turn them off in the desktop's own Remote Desktop policy. ## Unattended access for CI (service identities) A **service identity** is a non-human credential for scripts and CI that need `pm host`, or the [Model Servers API](https://docs.privatemind.com/model-servers-api.html#service-identities), without a person signing in. It never sees the recent-sign-in prompt, because it exchanges its client id and secret for a fresh short-lived token on every run. Organization admins create one under **Settings → Organization → Service Identities → New**, also reachable from **Compute → Remote Hosts**: 1. Give it a name. 2. Tick the hosts it may reach. 3. Tick **May manage model servers** if it should launch and register model servers. 4. Copy the **client id** and **client secret**. The secret is shown only once. Use it from CI: ```bash export PM_CLIENT_ID=pmsvc_… export PM_CLIENT_SECRET=pmsec_… pm login --service # no browser; exchanges a short-lived token pm host # or `pm host` to list ``` If your runner already holds a token, pass it as `PM_SERVICE_TOKEN` and skip `pm login --service`. A service identity reaches only the hosts you grant it, and only what a shell allows; it never holds a stored key on the host. With model servers granted, it launches and registers servers as a member of your org, under its own compute quota, and those servers show its name as the launcher. Rotating its secret or disabling it, at any time from the same panel, revokes its live tokens immediately. Every session it opens and every server it launches appears in your audit log.