Skip to main content
OpenClaw gives you a private AI assistant that can run continuously and automate real tasks. On Agencii, you can deploy your own OpenClaw instance with the official template in a few clicks.

Launch Fast

Start from a ready template and deploy in minutes.

Add Model Keys

Add your model provider keys in Agencii Secrets Vault.

Persistent Runtime

OpenClaw state is stored under /mnt/openclaw so it survives restarts.

Start Here

Before You Begin

Before you start, make sure you have:
  • An Agencii account
  • A GitHub account
  • Model provider keys in Agencii Secrets Vault

Deploy OpenClaw On Agencii

1

Create your repository

Open agency-ai-solutions/openclaw-starter-template.Click Use this template and create your own repository.Use this template dropdown
2

Connect the repository in Agencii

In Agencii, connect your GitHub account, then select the repository you created from the template.
3

Add model credentials

This step is for your Agencii deployment environment. Add provider keys in Agencii Secrets Vault, then attach those secrets as environment variables in the deployment settings.Common keys:
  • OPENAI_API_KEY
  • ANTHROPIC_API_KEY
4

Deploy

Start deployment and wait for the build to complete. Agencii builds and runs the repository automatically.
5

Run your first chat

Open your deployed agency chat and send a simple prompt.Example: What can you automate for me today?
For local run and local OAuth instructions, see the template README: agency-ai-solutions/openclaw-starter-template

Architecture On Agencii

Customize Your Assistant (OpenClaw Basics)

OpenClaw already has a built-in way to customize instructions. You do not need to invent a new format. On first start, OpenClaw creates starter files in its workspace. On Agencii, that workspace lives at /mnt/openclaw/.openclaw/workspace. This path is expected:
  • /mnt/openclaw is the runtime path inside the project.
  • In the full sandbox filesystem, this maps to /app/mnt/openclaw.
  • .openclaw/workspace is OpenClaw’s standard workspace layout inside that root.
Right now, the practical way to customize these files in Agencii is:
  1. Open your deployed agent
  2. Go to Customization -> Persistent File Storage
  3. Navigate to /mnt/openclaw/.openclaw/workspace
  4. Upload replacement versions of the files you want to change (for example AGENTS.md and SOUL.md)
Agencii persistent file storage view for OpenClaw workspace The most important files are:
  • AGENTS.md: main operating rules and priorities
  • SOUL.md: personality, tone, and boundaries
  • USER.md: who you are and how the agent should speak to you
  • IDENTITY.md: assistant name and identity style
  • TOOLS.md: tool usage notes and conventions
  • HEARTBEAT.md: optional checklist for proactive heartbeat runs
  • BOOTSTRAP.md: one-time first-run ritual file for a brand-new workspace
  • MEMORY.md and memory/*.md: long-term and daily memory notes
SOUL.md absolutely affects behavior. When you replace it, OpenClaw uses the new persona guidance in future runs. How instructions combine:
  • Onboarding instructions and workspace files are both used.
  • They are combined, not auto-merged intelligently.
  • If they conflict, responses can feel inconsistent, so keep them aligned.
Beginner best practice:
  1. Start with AGENTS.md and SOUL.md.
  2. Keep both files short and clear.
  3. Put stable preferences in USER.md and durable facts in MEMORY.md.

What You Get After Deploy

  • A deployable OpenClaw-based agency on Agencii
  • You chat in your normal Agencii workspace UI
  • Persistent OpenClaw files under /mnt/openclaw
  • Your own isolated runtime and data directory

Keys And Security

Add provider API keys in Agencii deployment secrets. Do not collect raw API keys in onboarding forms.
Use one OpenClaw deployment per trusted team or workspace. Provider keys you add in Agencii are injected into the running sandbox so OpenClaw can call model providers. Follow OpenClaw Security before exposing access.

If Something Is Not Working

  • Agent does not respond:
    • re-check provider keys in Agencii deployment secrets, then try again
  • Deployment succeeds but responses fail:
    • open deployment logs in Agencii, then redeploy
  • Data does not persist between restarts:
    • check that /mnt is mounted and writable in your runtime

Technical Reference

For implementation details (routes, runtime defaults, model alias behavior, and manual wiring), see:

Next Steps