Install NanoClaw & Reach First Message

Rule: Bring a provider credential (Claude subscription / OAuth / API key—or Codex paths if offered). The installer aims to bring Node, pnpm, Docker, and OneCLI.

Typical install path (verify on docs)

git clone https://github.com/nanocoai/NanoClaw.git
cd NanoClaw
bash nanoclaw.sh

Public materials describe nanoclaw.sh walking you from a fresh machine to a named agent: install deps, register Anthropic credential with OneCLI, build agent container, pair first channel (Telegram/Discord/WhatsApp/CLI). Failed steps may offer AI-assisted recovery (Claude Code) and resume.

Caveats called out in docs: do not run as root on Linux; some cloud images (e.g. certain Google Cloud VMs) are known-bad—check current quickstart.

What “done” looks like

Host service running (launchd/systemd) from the checkout
Agent workspace under groups/, state under data/, logs under logs/
Credential in OneCLI vault—not in the agent container env
You can message the agent on the paired channel

First-week checklist

Day	Goal
0	Install + one channel; confirm vault holds keys
1	Read isolation docs; decide if egress lockdown is on
2	Mount only required directories; test “cannot see host home”
3	Optional Docker Sandboxes / microVM path if threat model needs it
7	Backup checkout + vault config; review scheduled jobs

Prerequisites mindset

Expect macOS/Linux/WSL2, Node 20+, pnpm, Docker, and often Claude Code for customize/debug flows. If Docker is missing, installer may try to install it—still confirm your environment yourself.

This column

Last updated: 2026-07-14 · Independent analysis on OpenClaw Roadmap. Verify features on each project’s official site/repo—this space moves fast.