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

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

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 status

The 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.

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 RenX Desktop is open, it manages the connection. After Desktop closes, the installed service takes over automatically. Reopening Desktop reuses the same connection.

On a remote machine without RenX Desktop, the installed service owns the bridge connection continuously. Approvals still appear in RenX Desktop or mobile on another signed-in device.

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

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 install

renx 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

Run renx logout to stop the bridge and revoke the machine’s access. To remove automatic startup as well, run:

renx bridge uninstall

You 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, then renx 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.

Next steps

• Connect Codex
• Connect Claude Code
• Check support for other agents
• Manage the agent profile