peach desktop

Launch or install the native app on macOS arm64 and Linux x64, or Electron on Windows. Profiles keep cookies and app storage isolated.

terminal
peach desktop [--port <number>] [--profile <id>]
peach desktop install [options]
peach desktop uninstall

Options

flagdescription
--port <number>open a local app server through the peach shell, for example Metro on 8081
--profile <id>launch with an isolated persistent storage profile
--ephemerallaunch with a temporary isolated storage profile
-y, --yesfor install: skip confirmation and install immediately
--forcefor install: reinstall even if the companion is present
--electronlaunch or install Electron on Windows; use the native app on Mac and Linux
--nativelaunch or install the native desktop host (default app on macOS arm64; on Linux x64 installs the headless host that headless peach open draws through, see Tests in CI)
--channel <name>for install —native: production (default) or staging

Examples

terminal
peach desktop
peach desktop --port 8081
peach desktop --profile qa
peach desktop install --yes
peach desktop install --native --yes

Desktop Companion Role

On Apple silicon macOS and Linux x64, the native desktop app is the simulator window because it is faster than the browser. Setup installs it, and on a Mac the first peach open installs it if it is missing. Windows uses Electron; Intel Mac and Linux arm64 use the browser.

peach desktop install installs or updates the app by hand. Use peach desktop to open ConnectRN in it. On Linux, the desktop installer uses a .deb and sudo apt-get install and needs a desktop session. peach desktop install --native on Linux installs the standalone headless host instead of the desktop app.

Use peach open <port> --driver playwright --headed for a browser window. The background daemon keeps the bridge ready for either window and is a separate optional choice. Both windows use the same CLI inspection and interaction commands.