Skip to main content

Agent 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, WednesdayAI 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. The template instructs the agent to delete it with the built-in delete tool, so the ritual completes even on agents with tools.exec.security: "deny".
Once BOOTSTRAP.md is gone, WednesdayAI stamps onboardingCompletedAt in the workspace state file and the file is not recreated on later starts. With the default bootstrap file list, an absent BOOTSTRAP.md is omitted from the injected context entirely: no placeholder marker is injected for it. If you list BOOTSTRAP.md explicitly in systemPrompt.sections.projectContext.files, mark that entry optional: true to get the same behavior. With workspace lanes enabled, each lane completes onboarding independently by deleting its own BOOTSTRAP.md copy. The shared persona workspace keeps its BOOTSTRAP.md as the seed template for new lanes.

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).