Open The Template
Create your own repository from the official OpenClaw starter template.
Official OpenClaw Docs
Learn what OpenClaw can do and how its workspace files work.
Launch OpenClaw On Agent Swarm
Create your repository
Open agency-ai-solutions/openclaw-starter-template.Click Use this template and create a repository in your own GitHub account or organization.

Connect the repository
In Agent Swarm, connect your GitHub account and pick the repository you created from the template.
Enable persistent storage
Turn on Persistent File Storage for the swarm before the first deploy.For Agent Swarm deploys, set
OPENCLAW_HOME=/app/mnt/openclaw.
The file browser should show that same path directly, not a raw /mnt root.Add your AI provider secrets
Default deploy: add
OPENAI_API_KEY in Secrets Vault before you deploy.If you later switch away from the default OpenAI GPT-5.4 setup, add the matching provider secret for that model too.Optional advanced settings:OPENCLAW_PROVIDER_MODELonly if you want a different provider or modelANTHROPIC_API_KEYonly if you switch to an Anthropic modelOPENCLAW_GATEWAY_TOKENonly if you want to override the internal gateway token
Fill the onboarding form
Choose the assistant name, describe what it should help with, and add any extra instructions you want before deploy.

Customize OpenClaw After Deploy
OpenClaw keeps its own workspace files on persistent storage. That is where you update its personality, rules, and long-term notes. Agency Swarm now writes the default OpenClaw workspace to/app/mnt/openclaw/workspace.
At the storage root, you should also see sibling folders like logs and state.
The most important files are:
AGENTS.mdfor operating rules and prioritiesSOUL.mdfor voice, tone, and personalityUSER.mdfor user-specific preferencesMEMORY.mdfor durable notes you want OpenClaw to keep
- Open your deployed agent
- Go to Customization -> Persistent File Storage
- Open
/app/mnt/openclaw/workspace - Upload the replacement file

If OpenClaw starts behaving strangely, check both the onboarding instructions and the workspace files. They are both part of the final behavior.
If you are upgrading an older deploy, OpenClaw may still have legacy files under
.openclaw/workspace until the integration migrates them to the cleaner workspace path.What You Get
- A private OpenClaw deployment running on Agent Swarm
- Normal chat inside your Agent Swarm workspace
- Persistent OpenClaw files under
/app/mnt/openclaw - A clean upgrade path through the starter template repo