DocsPricing
Sign in
Search⌘K
Getting Started
OverviewInstallationQuick StartFirst TestPlansFAQ
Personal
Preview uploads & sharingApp Store screenshots
CI & GitHub
GitHub PR PreviewsTests in CITest Results
Cloud services (experimental)
OverviewJS ClientLimits & Pricing
Testing
OverviewMaestro SuitesDetox SuitesPlain-Language Tests
Guides
ConfigurationWrap Existing AppReporting IssuesTroubleshootingMCP
Agents
SetupCLI UseAgent Devtool (Inspect)
REST API
OverviewAuthenticationPreviewsBuildsTest RunsCloud SessionsBilling & LimitsRate LimitsErrors
API
ConfigSettingsMetro PluginOne PluginAgent SkillsTest BridgeDetox DriverMaestro Driver
CLI
Overviewmaestrodetoxcleanuprecordfilmstoragepermissionsperfdescribefindassertscreenshotgetdowaitshellmodedevicenetworklogsdebugwhat-happenedtimelineboxiosandroidopenlistuseskillclaimagentclosesetupcompatreport-issuedesktopdaemonversionupgradeserveruntimeauthloginlogoutconfig
Compatibility
OverviewCustom Stubs
[ Documentation ]
rnx desktop

rnx desktop

rnx desktop

Launch the optional desktop companion from the standalone CLI, or install it when missing. Profiles map to Electron partitions, so cookies and app storage stay isolated per profile.

terminal
rnx desktop [--port <number>] [--profile <id>]

rnx desktop install [options]

Options

flagdescription
--port <number>open a local app server through the rnx 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

Examples

terminal
rnx desktop

rnx desktop --port 8081

rnx desktop --profile qa

rnx desktop install --yes

Desktop Companion Role

The desktop companion is the persistent local host option. It is the right fit when you want:

  • +
    a tray or login-item style workflow
  • +
    a window that stays inspectable over the same bridge host
  • +
    an installed local companion that rnx open can prefer automatically

The CLI command here is intentionally thin. Its job is to find or install the companion and launch it with the right URL.

Related

previous

report-issue

next

daemon