About

Use daemon mode to give coding agents a shared entry point for model requests and hooks. A coding harness is the application that runs the agent, such as Codex, Claude Code, or Pi. A daemon is a background process that stays running between sessions. Each user-machine identity gets its own worker and runtime state.

Start Here When

Use this section to:

Run Relay at login or system startup.
Share one local daemon across users on a computer.
Connect client computers to a daemon on a Linux server.
Distribute the same administrator-owned settings to every user.
Operate workers, diagnose failed connections, and preserve streamed responses.

For a personal integration managed by nemo-relay install, use Coding Agent Installation. Managed daemon mode uses different lifecycle commands and administrator-owned configuration.

Choose a Deployment

Prefer a daemon on the host where users run their coding harnesses. The daemon helps sessions recover from worker failures and serves multiple users on one host. Avoid Kubernetes unless shared host networking causes port conflicts or one daemon cannot serve enough users at the same time. Refer to Kubernetes Deployment Guidance to decide whether you need it and plan the setup. NeMo Relay does not provide a reference Helm chart.

Deployment	Daemon runs as	Available when	Guide
Windows user task	Signed-in user	User is logged in	Windows
Windows system task or service	System service account	Computer is running	Windows
macOS LaunchAgent	Signed-in user	User is logged in	macOS
macOS LaunchDaemon	Dedicated service account	Computer is running	macOS
Linux user service	User	User manager is running; optional lingering starts it at boot	Linux
Linux system service	Dedicated service account	Computer is running	Linux
Remote Linux daemon	Server service account	Server and private network are available	Server, clients

Choose one service method per daemon endpoint. The default local endpoint is http://127.0.0.1:47632. A personal Relay sidecar can already occupy that port. Stop the existing integration before switching, or assign a different fixed port and generate a separate managed bundle for that endpoint. Multiple user services on one computer also need separate ports; one system service can serve all users.

Before You Begin

Install a Relay binary that includes nemo-relay daemon managed-bundle on the server and every client. Follow Installation for supported binaries and Support Matrix for harness versions. Check nemo-relay daemon --help on each target before setup.

An administrator must provision the system configuration, stable executable, and managed bundle, even for a user-level daemon. Local and remote-client workers merge personal Relay configuration and plugins with system settings. System settings take priority. Users need a distinct route credential for each machine-user identity, plus their normal model-provider authentication.

Remote deployments need a trusted HTTPS certificate and a private IPv4 route in both directions: clients contact the daemon, and the daemon contacts client workers. A connection that allows only outbound traffic from clients is not enough.

Reading Order

Read Architecture and Startup.
Prepare Configuration and Managed Clients.
Follow the deployment guide for your operating system.
Complete Verify Worker-Backed Operation.
Keep Reference available for command and lifecycle details.