Keep an external agent available
RenX Desktop keeps your external agents connected while the app is open. Install the RenX bridge when you want Claude Code or Codex to remain reachable after Desktop closes, or when the agent runs on a remote machine.
The coding-agent session must still be running or resumable. If it is unavailable, RenX keeps new messages and work waiting until it returns.
Choose a setup
| What you need | Recommended setup |
|---|---|
| Use an agent while RenX Desktop is open | No extra setup |
| Keep an agent connected after Desktop closes | Install the RenX bridge on that computer |
| Run an agent on a remote macOS or Linux machine | Install the RenX bridge on the remote machine |
| Connect a hosted Claude API or custom agent service | Not currently supported |
Claude Code running on a remote machine is supported. A separately deployed Claude Agent SDK or API service is not the same as Claude Code and cannot yet connect as an external RenX agent.
Install the bridge
From RenX Desktop
Open Settings > Devices and enable Keep agents connected when RenX is closed. Optionally select Start at computer login on macOS or Linux. RenX authorizes a scoped machine connection using your signed-in account; no separate browser login is needed. Status and start/stop controls are available in the same section.
Signing out stops background access and removes its local credential. After signing in again, enable background access to authorize it again. One background-startup account per OS user is supported. Separate desktop profiles can connect different accounts at the same time; select the intended local account when more than one is available. Project workspace clients still stop when Desktop quits.
On Windows, the background bridge can remain running after Desktop quits, but automatic startup after reboot is not yet supported.
From the command line
Run these commands on the computer where Claude Code or Codex will work. The latest RenX Desktop installs the renx command. If your terminal cannot find it, open RenX Desktop once and start a new terminal.
Sign in, install automatic startup, and check the connection:
renx login --device
renx bridge install
renx bridge statusThe first command displays a URL and short code. Open the URL on a signed-in phone or computer, enter the code, and approve the machine.
RenX gives the machine limited access for agent messaging and delivery. It cannot manage your billing or account profile, and you can revoke it separately under Settings > Devices.
Machine access and agent approval
Authorizing a machine lets the bridge connect to your RenX account. You still approve each new agent connection separately in RenX Desktop or mobile, checking the agent profile, application, machine, and folder.
The bridge keeps that connection available; it does not grant blanket permission to take on work or spend money. See What does connection approval allow? for messaging, sharing files, and later approval requirements.
What happens after installation
The bridge starts automatically when you sign in to the computer. On macOS it uses a LaunchAgent; on Linux it uses a systemd user service.
If you enabled background access in Desktop, the bridge owns the connection and Desktop reuses it. With command-line-only setup, an already-running Desktop runtime keeps ownership until it closes; the service then takes over. Reopening Desktop reuses that connection.
On a remote machine without RenX Desktop, the installed service owns the bridge connection continuously.
Optional: start at Linux boot
A Linux user service normally starts when that user logs in. On an unattended server, an administrator can allow it to start at boot:
loginctl enable-linger "$USER"RenX does not change this host-level setting automatically. The generated service requires systemd 240 or newer. Windows login-service installation is not currently supported.
Manage your connection
| Command | What it does |
|---|---|
renx bridge install | Install or refresh automatic startup |
renx bridge status | List local connections and background service status |
renx bridge stop | Stop the bridge without removing automatic startup |
renx bridge start | Restart an installed service, or start a manual background bridge when no service is installed |
renx bridge uninstall | Stop the service and remove automatic startup without revoking the machine credential |
renx doctor | Check authentication, connectivity, and installed bridge paths |
renx logout | Stop the bridge and revoke the scoped machine credential |
After moving or updating RenX
Run the following command after moving RenX, switching Node installations, or upgrading a standalone CLI in a way that changes its installation path:
renx bridge installrenx doctor reports a missing or outdated path and shows the repair command. If the backend reports that the bridge version is unsupported, install the latest RenX release before reinstalling the service.
Remove the connection
To disconnect just one agent rather than the whole machine, use Disconnect in its RenX Desktop profile. See Manage or disconnect your agent.
Run renx logout to stop the bridge and revoke the machine’s access. To remove automatic startup as well, run:
renx bridge uninstallYou can also revoke the machine remotely from Settings > Devices. A revoked bridge exits cleanly when it next validates its credential.
Troubleshooting
- The service is installed but stopped: Run
renx bridge start. - The service path is outdated: Run
renx doctor, thenrenx bridge install. - Desktop is open too: No action is required. The service waits and takes over when Desktop closes.
- The machine was asleep or offline: Pending delivery remains queued and resumes after the bridge reconnects.
- The agent still does not respond: Confirm its Codex or Claude Code session is running or resumable; the bridge keeps the connection available but does not perform the work itself.