HumanLayer Docs

Run a Remote Daemon ​

This guide shows you how to install, authenticate, and launch a remote daemon.

For one guided launch-token path, use the remote daemon tutorial. For host choices, persistence, capabilities, and security, read how remote daemons work. To learn the local macOS path, use the first-session tutorial.

Install the CLI ​

Install the HumanLayer CLI on the daemon host. Then check the installation.

bash
npm install -g @humanlayer/cli@latest
humanlayer --help

Option 1: Use interactive login ​

Use interactive login when the daemon host has an interactive terminal. The command stores credentials on that host. You can restart the daemon without a new launch token.

Run the login command.

bash
humanlayer login

The CLI prints a verification URL and a user code. Open the URL. Complete authentication. Select the organization if the browser prompts you. Then return to the terminal.

After login succeeds, launch the daemon.

bash
humanlayer daemon launch

For beta, add the beta environment flag to both commands.

bash
humanlayer --beta login
humanlayer --beta daemon launch

Option 2: Use a launch token ​

Use a launch token for one non-interactive command. Examples include a shell without an interactive PTY and a one-time remote bootstrap script.

Open app.humanlayer.com on a machine or phone. Go to Settings -> Daemons. Generate a daemon launch token. Copy it to the daemon host.

Launch tokens are short-lived credentials. If a token expires before the daemon starts, generate a new token in the app.

bash
humanlayer daemon launch --launch-token <TOKEN>

For beta, add the beta environment flag.

bash
humanlayer daemon launch --launch-token <TOKEN> --beta

Check the connection ​

Open app.humanlayer.com after the daemon connects. Create and manage sessions on the daemon host from a machine or phone. You can send messages to the coding agent from the same website while it works.

The native app is optional for this workflow. Read browser and native app capabilities before you depend on a native app feature.

Keep the daemon running ​

The launch command does not create a managed background service. If you launch over SSH, use tmux, screen, or another process supervisor. This keeps the daemon running after you disconnect.

Troubleshooting ​

  • If a launch token expires before startup, generate a new token in Settings -> Daemons.
  • If you restart a daemon that used --launch-token, provide another valid launch token or run humanlayer login first.
  • If saved authentication no longer refreshes, run humanlayer login again.
  • If a recreated container loses authentication, read container persistence.