BLOG/TUTORIAL
TUTORIAL·7 MIN READ·MARCH 9, 2026

How to Set Up OpenClaw With a Custom Soul

Step-by-step guide to loading a custom Agent Soul into OpenClaw for production use.

How to Set Up OpenClaw With a Custom Soul

OpenClaw is one of the most powerful agent frameworks available. But out of the box, it runs on generic prompts — and generic prompts produce generic work.

Here's how to load a custom Soul into OpenClaw and get dramatically better results.

What You Need

  • OpenClaw installed and configured
  • A Soul file (.md format)
  • 15 minutes

Step 1: Choose Your Soul

Before setup, decide which Soul you're loading. This depends on what you want OpenClaw to do.

For engineering workflows: CTO Agent Soul, Code Review Agent, or Backend Dev Soul.

For content workflows: SEO Content Writer or Xiaohongshu Copywriter.

For operations: Context Manager or Inbox Zero Agent.

Download your Soul from soulkit.io/shop. Free Souls don't require an account.

Step 2: Locate Your OpenClaw Config

OpenClaw stores agent configuration in your project directory. The exact location depends on your setup, but it's typically:

``

~/.openclaw/agents/

`

Or in your project:

`

.openclaw/agents/

`

Step 3: Create the Soul File

Create a new file in your agents directory. Name it after the Soul you're loading:

`bash

touch ~/.openclaw/agents/code-reviewer.md

`

Paste the Soul content into this file.

Step 4: Reference the Soul in Your Agent Config

In your OpenClaw agent configuration (usually agent.yaml or agent.json), add a reference to your Soul file:

`yaml

agent:

name: code-reviewer

soul: ~/.openclaw/agents/code-reviewer.md

model: claude-3-5-sonnet

tools:

- file_read

- file_write

- bash

`

Step 5: Test the Soul

Run a test prompt that exercises the Soul's identity:

`bash

openclaw run code-reviewer "Review this function for security issues: [paste code]"

`

You should see the agent respond with the Soul's characteristic voice — specific, direct, labeled by severity.

If the response feels generic, check that the Soul file is correctly referenced and the content is complete.

Step 6: Add the Context Manager Skill

For any Soul running in a long session, add the Context Manager Skill alongside it.

Context Manager prevents silent context overflow — the gradual degradation that happens when sessions run long. It monitors token usage and executes clean handoffs.

Load it the same way as your primary Soul:

`yaml

agent:

name: code-reviewer

soul: ~/.openclaw/agents/code-reviewer.md

skills:

- ~/.openclaw/skills/context-manager.md

model: claude-3-5-sonnet

``

Common Issues

Agent ignores the Soul and responds generically

Check that the Soul file path is correct and the file isn't empty. OpenClaw silently falls back to defaults if it can't load the Soul.

Agent is inconsistent across sessions

Add the Context Manager Skill. Inconsistency often comes from context overflow.

Agent is too rigid

Your Decision Rules may be too specific. Loosen them to give the Soul more room to exercise judgment.

What to Expect

A well-loaded Soul changes the character of every interaction.

The agent becomes more consistent. It makes better decisions at edge cases. It develops a recognizable voice.

Most importantly: it holds under pressure. When a situation arises that no instruction covers, the Soul generates the right behavior because the identity and values are there.

That's what makes the difference between an agent you trust and one you babysit.

Browse Souls for OpenClaw →

// READY TO BUILD?
Browse production-tested Agent Souls
Free souls to start with. No account required.
// MORE ARTICLES