Skip to content
RemoteClaw

Setup

Setup

If you are setting up for the first time, start with [Getting Started](/start/getting-started). For onboarding details, see [Onboarding (CLI)](/start/wizard).

TL;DR

  • Tailoring lives outside the repo: ~/.remoteclaw/workspace (workspace) + ~/.remoteclaw/remoteclaw.json (config).
  • Stable workflow: install the macOS app; let it run the bundled Gateway.
  • Bleeding edge workflow: run the Gateway yourself via pnpm gateway:watch, then let the macOS app attach in Local mode.

Prereqs (from source)

  • Node 24 recommended (Node 22 LTS, currently 22.16+, still supported)
  • pnpm
  • Docker (optional; only for containerized setup/e2e — see Docker)

Tailoring strategy (so updates do not hurt)

If you want “100% tailored to me” and easy updates, keep your customization in:

  • Config: ~/.remoteclaw/remoteclaw.json (JSON/JSON5-ish)
  • Workspace: ~/.remoteclaw/workspace (skills, prompts, memories; make it a private git repo)

Bootstrap once:

Terminal window
remoteclaw setup

From inside this repo, use the local CLI entry:

Terminal window
remoteclaw setup

If you don’t have a global install yet, run it via pnpm remoteclaw setup.

Run the Gateway from this repo

After pnpm build, you can run the packaged CLI directly:

Terminal window
node remoteclaw.mjs gateway --port 18789 --verbose

Stable workflow (macOS app first)

  1. Install + launch RemoteClaw.app (menu bar).
  2. Complete the onboarding/permissions checklist (TCC prompts).
  3. Ensure Gateway is Local and running (the app manages it).
  4. Link surfaces (example: WhatsApp):
Terminal window
remoteclaw channels login
  1. Sanity check:
Terminal window
remoteclaw health

If onboarding is not available in your build:

  • Run remoteclaw setup, then remoteclaw channels login, then start the Gateway manually (remoteclaw gateway).

Bleeding edge workflow (Gateway in a terminal)

Goal: work on the TypeScript Gateway, get hot reload, keep the macOS app UI attached.

0) (Optional) Run the macOS app from source too

If you also want the macOS app on the bleeding edge:

Terminal window
./scripts/restart-mac.sh

1) Start the dev Gateway

Terminal window
pnpm install
pnpm gateway:watch

gateway:watch runs the gateway in watch mode and reloads on relevant source, config, and bundled-plugin metadata changes.

2) Point the macOS app at your running Gateway

In RemoteClaw.app:

  • Connection Mode: Local The app will attach to the running gateway on the configured port.

3) Verify

  • In-app Gateway status should read “Using existing gateway …”
  • Or via CLI:
Terminal window
remoteclaw health

Common footguns

  • Wrong port: Gateway WS defaults to ws://127.0.0.1:18789; keep app + CLI on the same port.
  • Where state lives:
    • Credentials: ~/.remoteclaw/credentials/
    • Sessions: ~/.remoteclaw/agents/<agentId>/sessions/
    • Logs: /tmp/remoteclaw/

Credential storage map

Use this when debugging auth or deciding what to back up:

  • WhatsApp: ~/.remoteclaw/credentials/whatsapp/<accountId>/creds.json
  • Telegram bot token: config/env or channels.telegram.tokenFile (regular file only; symlinks rejected)
  • Discord bot token: config/env or SecretRef (env/file/exec providers)
  • Slack tokens: config/env (channels.slack.*)
  • Pairing allowlists:
    • ~/.remoteclaw/credentials/<channel>-allowFrom.json (default account)
    • ~/.remoteclaw/credentials/<channel>-<accountId>-allowFrom.json (non-default accounts)
  • Model auth profiles: ~/.remoteclaw/agents/<agentId>/agent/auth-profiles.json
  • File-backed secrets payload (optional): ~/.remoteclaw/secrets.json
  • Legacy OAuth import: ~/.remoteclaw/credentials/oauth.json More detail: Security.

Updating (without wrecking your setup)

  • Keep ~/.remoteclaw/workspace and ~/.remoteclaw/ as “your stuff”; don’t put personal prompts/config into the remoteclaw repo.
  • Updating source: git pull + pnpm install (when lockfile changed) + keep using pnpm gateway:watch.

Linux (systemd user service)

Linux installs use a systemd user service. By default, systemd stops user services on logout/idle, which kills the Gateway. Onboarding attempts to enable lingering for you (may prompt for sudo). If it’s still off, run:

Terminal window
sudo loginctl enable-linger $USER

For always-on or multi-user servers, consider a system service instead of a user service (no lingering needed). See Gateway runbook for the systemd notes.