openclaw/docs/start/bootstrapping.md

summary, read_when, title, sidebarTitle

summary	read_when	title	sidebarTitle
Agent bootstrapping ritual that seeds the workspace and identity files	Understanding what happens on the first agent run Explaining where bootstrapping files live Debugging onboarding identity setup	Agent bootstrapping	Bootstrapping

Bootstrapping is the first‑run ritual that prepares an agent workspace and collects identity details. It happens after onboarding, when the agent starts for the first time.

What bootstrapping does

On the first agent run, OpenClaw bootstraps the workspace (default ~/.openclaw/workspace):

• Seeds AGENTS.md, BOOTSTRAP.md, IDENTITY.md, USER.md.
• Runs a short Q&A ritual (one question at a time).
• Writes identity + preferences to IDENTITY.md, USER.md, SOUL.md.
• Removes BOOTSTRAP.md when finished so it only runs once.

For embedded/local model runs, OpenClaw keeps BOOTSTRAP.md out of the privileged system context. On the primary interactive first run, it still passes the file contents in the user prompt so models that do not reliably call the read tool can complete the ritual. If the current run cannot safely access the workspace, the agent gets a limited bootstrap note instead of a generic greeting.

Skipping bootstrapping

To skip this for a pre-seeded workspace, run openclaw onboard --skip-bootstrap.

Where it runs

Bootstrapping always runs on the gateway host. If the macOS app connects to a remote Gateway, the workspace and bootstrapping files live on that remote machine.

When the Gateway runs on another machine, edit workspace files on the gateway host (for example, `user@gateway-host:~/.openclaw/workspace`).

Related docs

• macOS app onboarding: Onboarding
• Workspace layout: Agent workspace