Skip to content
RemoteClaw

Nix

Nix Installation

The recommended way to run RemoteClaw with Nix is via nix-remoteclaw — a batteries-included Home Manager module.

Quick Start

Paste this to your AI agent (Claude, Cursor, etc.):

I want to set up nix-remoteclaw on my Mac.
Repository: github:remoteclaw/nix-remoteclaw


What I need you to do:
1. Check if Determinate Nix is installed (if not, install it)
2. Create a local flake at ~/code/remoteclaw-local using templates/agent-first/flake.nix
3. Help me create a Telegram bot (@BotFather) and get my chat ID (@userinfobot)
4. Set up secrets (bot token, Anthropic key) - plain files at ~/.secrets/ is fine
5. Fill in the template placeholders and run home-manager switch
6. Verify: launchd running, bot responds to messages


Reference the nix-remoteclaw README for module options.

📦 Full guide: github.com/remoteclaw/nix-remoteclaw

The nix-remoteclaw repo is the source of truth for Nix installation. This page is just a quick overview.

What you get

  • Gateway + macOS app + tools (whisper, spotify, cameras) — all pinned
  • Launchd service that survives reboots
  • Plugin system with declarative config
  • Instant rollback: home-manager switch --rollback

Nix Mode Runtime Behavior

When REMOTECLAW_NIX_MODE=1 is set (automatic with nix-remoteclaw):

RemoteClaw supports a Nix mode that makes configuration deterministic and disables auto-install flows. Enable it by exporting:

Terminal window
REMOTECLAW_NIX_MODE=1

On macOS, the GUI app does not automatically inherit shell env vars. You can also enable Nix mode via defaults:

Terminal window
defaults write ai.remoteclaw.mac remoteclaw.nixMode -bool true

Config + state paths

RemoteClaw reads JSON5 config from REMOTECLAW_CONFIG_PATH and stores mutable data in REMOTECLAW_STATE_DIR. When needed, you can also set REMOTECLAW_HOME to control the base home directory used for internal path resolution.

  • REMOTECLAW_HOME (default precedence: HOME / USERPROFILE / os.homedir())
  • REMOTECLAW_STATE_DIR (default: ~/.remoteclaw)
  • REMOTECLAW_CONFIG_PATH (default: $REMOTECLAW_STATE_DIR/remoteclaw.json)

When running under Nix, set these explicitly to Nix-managed locations so runtime state and config stay out of the immutable store.

Runtime behavior in Nix mode

  • Auto-install and self-mutation flows are disabled
  • Missing dependencies surface Nix-specific remediation messages
  • UI surfaces a read-only Nix mode banner when present

Packaging note (macOS)

The macOS packaging flow expects a stable Info.plist template at:

apps/macos/Sources/RemoteClaw/Resources/Info.plist

scripts/package-mac-app.sh copies this template into the app bundle and patches dynamic fields (bundle ID, version/build, Git SHA, Sparkle keys). This keeps the plist deterministic for SwiftPM packaging and Nix builds (which do not rely on a full Xcode toolchain).