AI Agent Setup

March 28, 2026 · View on GitHub

Nerve supports agent-driven installation.

If you want an AI agent to install, configure, and validate Nerve, the canonical raw instruction file is:

INSTALL.md
raw URL: https://raw.githubusercontent.com/daggerhashimoto/openclaw-nerve/master/docs/INSTALL.md

Use that file as the operational contract. Use this page for the human-readable explanation, boundaries, and topology map.

Copy-paste prompt

Install, configure, and validate Nerve on this machine.

Fetch and follow instructions from:
https://raw.githubusercontent.com/daggerhashimoto/openclaw-nerve/master/docs/INSTALL.md

Default agent behavior

Unless you say otherwise, agents should use these defaults:

local-first
localhost-only by default
~/nerve as the install path
installer-first (install.sh)
setup wizard first
validate before reporting completion

That means the common happy path is:

detect an existing OpenClaw gateway
install Nerve
run setup
start or restart Nerve
validate the UI and gateway connection

What agents may do automatically

For the default local path, agents may automatically:

inspect the current machine and existing install state
detect whether ~/nerve already exists
detect whether OpenClaw is installed and reachable
detect the gateway token and gateway URL
install missing core prerequisites for the local path
run the Nerve installer
run the setup wizard
use defaults mode for local-only setup when no TTY is available
write a minimal local .env if the wizard cannot be used
restart local services or processes
run validation and smoke checks

Agents may also apply minimal localhost-safe OpenClaw changes needed for the default path, such as local origin allowlisting, local pairing fixes, or required local tool allow entries.

What requires confirmation

Agents should ask before they do anything that changes exposure, trust, or install ownership.

That includes:

installing OpenClaw
exposing Nerve beyond localhost
LAN access
public internet exposure
reverse proxy setup
Tailscale setup or topology changes
destructive reinstall, replacement, or deletion
remote gateway auth or allowlist changes
cloud-hosted assumptions that materially change the security posture

Short version: local repair and local setup can be automated. Public or destructive changes need consent.

Dependency behavior

Nerve is not a standalone app. It depends on an OpenClaw gateway.

Expected agent behavior:

look for an existing reachable gateway first
prefer using that gateway
if none is found, explain the dependency clearly
ask before installing OpenClaw

For the default same-machine flow, agents may make the smallest safe local OpenClaw fixes required for Nerve to connect. For remote or public gateway changes, they should stop and ask.

Topology map

Choose the guide that matches the intended setup:

Local / same machine: DEPLOYMENT-A.md
Hybrid / local Nerve + remote gateway: DEPLOYMENT-B.md
Cloud / remote Nerve: DEPLOYMENT-C.md
Add Tailscale to an existing install: TAILSCALE.md

Recommended default: start with the local setup unless you already know you need something else.

Done criteria

An agent should only report success when all of these are true:

Nerve is installed at the intended path
Nerve starts successfully
it points at the intended OpenClaw gateway
access and auth match the requested mode
the smoke test passes

A script finishing is not enough. A valid install must actually respond and connect.

Smoke test expectations

Keep validation minimal and real:

confirm the Nerve service or process is running
confirm the expected URL responds
confirm the intended gateway responds
confirm .env matches the intended gateway
if auth is enabled, confirm the login surface or protected access path is present

Typical local checks:

openclaw gateway status
curl -fsS http://127.0.0.1:18789/health
curl -fsS http://127.0.0.1:3080/health

For remote or custom setups, agents should adjust the URLs to match the requested topology.

Failure and recovery behavior

Agents should fail clearly, not vaguely.

No OpenClaw gateway found

Explain that Nerve depends on OpenClaw and ask before installing it.

Installer or setup wizard unavailable

Use the smallest correct fallback:

clone the repo if needed
npm install
npm run setup when available
if local-only and no TTY is available, npm run setup -- --defaults
if needed, write a minimal .env, then build and start manually

Install, configure, and validate Nerve on this machine.
Use the safest local-first path and keep it localhost-only unless you need my approval.

Fetch and follow instructions from:
https://raw.githubusercontent.com/daggerhashimoto/openclaw-nerve/master/docs/INSTALL.md

Local Nerve + existing remote gateway

Install Nerve on this machine and connect it to my existing remote OpenClaw gateway.
Do not expose Nerve beyond localhost unless I approve it.
If remote gateway config needs changing, tell me before you do it.

Fetch and follow instructions from:
https://raw.githubusercontent.com/daggerhashimoto/openclaw-nerve/master/docs/INSTALL.md

Tailscale setup

Install Nerve and make it reachable over Tailscale.
Ask before making any exposure or gateway allowlist changes.
Use the repo's Tailscale guidance instead of inventing a new flow.

Fetch and follow instructions from:
https://raw.githubusercontent.com/daggerhashimoto/openclaw-nerve/master/docs/INSTALL.md

Existing install repair

Inspect my existing Nerve install, repair it if needed, and validate it.
Do not reinstall or delete anything unless you ask first.

Fetch and follow instructions from:
https://raw.githubusercontent.com/daggerhashimoto/openclaw-nerve/master/docs/INSTALL.md