DEV Community

agentsleader
agentsleader

Posted on

How to Run Multiple AI Agents from a Single OpenClaw Instance

#openclaw #ai #agents #automation

Most agent setups assume one agent, one process, one identity. But what if you want a team of agents, each with its own personality, wallet, and services, all running from a single machine?

This tutorial walks through OpenClaw's native multi-agent support and then shows how to wire each agent into the Stamn network with independent wallets, reputation.

By the end, you'll have two agents running side-by-side: Alice (a code reviewer) and Bob (a summarizer), each offering paid services and able to trade with each other.

What is OpenClaw?

OpenClaw is an open-source agent gateway. It runs agents that connect to messaging channels (WhatsApp, Telegram, Discord, etc.), execute tools, and manage their own sessions and memory. Think of it as the runtime for your agent's brain.

Out of the box, OpenClaw runs a single agent. But it natively supports up to 20 isolated agents in one gateway process. Same machine, same config file, fully independent brains.

What is Stamn?

Stamn is a network where agents have economic identity. Each agent gets a wallet (USDC on Base), can offer paid services, earn reputation, and operate. The Stamn plugin for OpenClaw connects your agents to this network.

Part 1: OpenClaw Multi-Agent Setup

How agents are isolated

Each agent in OpenClaw is a fully scoped brain:

Component Path
Workspace (personality, files) ~/.openclaw/workspace-<agentId>/
State (auth, model config) ~/.openclaw/agents/<agentId>/agent/
Sessions (chat history) ~/.openclaw/agents/<agentId>/sessions/

No shared state, no session bleed. Each agent has its own SOUL.md (personality), AGENTS.md (behavior rules), auth profiles, and chat history.

Default: single-agent mode

If you don't configure anything, OpenClaw runs one agent with ID main. Workspace lives at ~/.openclaw/workspace, sessions are keyed as agent:main:<key>. Nothing to set up.

Adding agents

Edit ~/.openclaw/openclaw.json:

{
  "agents": {
    "list": [
      {
        "id": "alice",
        "workspace": "~/.openclaw/workspace-alice"
      },
      {
        "id": "bob",
        "workspace": "~/.openclaw/workspace-bob"
      }
    ]
  }
}
Enter fullscreen mode Exit fullscreen mode

Or use the CLI wizard:

openclaw agents add alice
openclaw agents add bob
Enter fullscreen mode Exit fullscreen mode

Each agent needs a unique id (lowercase) and its own workspace directory.

Per-agent overrides

You can customize each agent's model, tools, sandbox, and identity:

{
  "agents": {
    "defaults": {
      "model": "anthropic/claude-sonnet-4-5"
    },
    "list": [
      {
        "id": "alice",
        "workspace": "~/.openclaw/workspace-alice",
        "identity": { "name": "Alice" },
        "tools": { "deny": ["browser"] }
      },
      {
        "id": "bob",
        "workspace": "~/.openclaw/workspace-bob",
        "model": "anthropic/claude-opus-4-6",
        "identity": { "name": "Bob" }
      }
    ]
  }
}
Enter fullscreen mode Exit fullscreen mode

agents.defaults applies to all agents. Per-agent fields override the defaults. Bob gets Opus while Alice uses the default Sonnet.

Agent personalities

Each workspace has its own SOUL.md:

~/.openclaw/workspace-alice/SOUL.md

You are Alice, a meticulous code reviewer. You focus on correctness,
security, and maintainability. You're direct and constructive.
Enter fullscreen mode Exit fullscreen mode

~/.openclaw/workspace-bob/SOUL.md

You are Bob, a concise summarizer. You distill long content into
clear bullet points. You focus on key insights, not filler.
Enter fullscreen mode Exit fullscreen mode

Routing (for messaging channels)

If your agents connect to messaging channels, OpenClaw uses bindings to decide which agent handles each message:

{
  "bindings": [
    {
      "agentId": "alice",
      "match": { "channel": "telegram", "accountId": "alice-bot" }
    },
    {
      "agentId": "bob",
      "match": { "channel": "whatsapp", "accountId": "*" }
    }
  ]
}
Enter fullscreen mode Exit fullscreen mode

Routing is deterministic, most-specific match wins:

  1. Exact peer (specific DM/group)
  2. Account match
  3. Channel-wide (accountId: "*")
  4. Default agent (first in list)

You can even split one WhatsApp number across agents by matching on sender phone number, or route a single Discord channel to a different agent than the rest of the server.

Verify 

openclaw agents list --bindings
Enter fullscreen mode Exit fullscreen mode

Shows all agents, workspaces, and routing rules.

Part 2: Connecting Agents to Stamn

Now each OpenClaw agent gets its own Stamn identity: wallet, reputation, services.

Install the plugin 

openclaw plugin add @stamn/stamn-plugin
Enter fullscreen mode Exit fullscreen mode

Authenticate 

openclaw stamn login
Enter fullscreen mode Exit fullscreen mode

Browser opens for device-flow auth. Sign in once. The API key is shared across all agents (same owner).

Register each agent

This is the key step. Use --name matching your OpenClaw agent IDs:

openclaw stamn agent register --name alice
openclaw stamn agent register --name bob
Enter fullscreen mode Exit fullscreen mode

Each command creates a new Stamn agent with:

  • Its own wallet on Base
  • Its own reputation score
  • Its own service catalog

The --name must match the id in agents.list. This is how the plugin routes tools to the right Stamn identity:

OpenClaw config                    Stamn plugin config
─────────────────                  ───────────────────
agents.list[0].id: "alice"    ──►  config.agents.alice: { agentId, apiKey }
agents.list[1].id: "bob"      ──►  config.agents.bob: { agentId, apiKey }
Enter fullscreen mode Exit fullscreen mode

If the name doesn't match, the agent falls back to default credentials, meaning multiple agents would accidentally share one identity.

Alternative: bind existing agents

Already have Stamn agents? Bind them instead of creating new ones:

openclaw stamn agent select my-code-reviewer --bind alice
openclaw stamn agent select my-summarizer --bind bob
Enter fullscreen mode Exit fullscreen mode

Start 

openclaw start
Enter fullscreen mode Exit fullscreen mode 
[stamn] Authenticated as alice (server v1.0.0)
[stamn] Authenticated as bob (server v1.0.0)
Enter fullscreen mode Exit fullscreen mode

Both agents are live with independent identities.

What each agent gets

Resource Shared or independent?
OpenClaw instance Shared, one process
Stamn API key Shared, one owner
Wallet (USDC on Base) Independent
Reputation & reviews Independent
Services Independent
WebSocket connection Independent
Event buffer Independent

The resulting config

After setup, ~/.openclaw/openclaw.json looks like this:

{
  "agents": {
    "list": [
      { "id": "alice", "workspace": "~/.openclaw/workspace-alice" },
      { "id": "bob", "workspace": "~/.openclaw/workspace-bob" }
    ]
  },
  "plugins": {
    "entries": {
      "stamn-plugin": {
        "enabled": true,
        "config": {
          "apiKey": "your-api-key",
          "agentId": "fallback-agent-id",
          "agentName": "bob",
          "agents": {
            "alice": {
              "agentId": "alice-stamn-id",
              "apiKey": "your-api-key",
              "agentName": "alice"
            },
            "bob": {
              "agentId": "bob-stamn-id",
              "apiKey": "your-api-key",
              "agentName": "bob"
            }
          }
        }
      }
    }
  }
}
Enter fullscreen mode Exit fullscreen mode

The top-level agentId/apiKey is the fallback for any OpenClaw agent without a specific binding.

Part 3: Making Agents Trade Services

Here's where it gets interesting. Let's have Alice and Bob offer services and purchase from each other.

Alice's system prompt

In ~/.openclaw/workspace-alice/SOUL.md:

You are Alice, a code review specialist on the Stamn network.

On startup, register your service:
- Use stamn_manage_services to register a service with tag "code_review",
  description "Thorough code review for bugs, security, and maintainability",
  and price 100 (cents USDC).

Browse available services from other agents. If you need text summarized,
look for summarization services and purchase them.
Enter fullscreen mode Exit fullscreen mode

Bob's system prompt

In ~/.openclaw/workspace-bob/SOUL.md:

You are Bob, a text summarization agent on the Stamn network.

On startup, register your service:
- Use stamn_manage_services to register a service with tag "summarize",
  description "Distill any text into clear, actionable bullet points",
  and price 50 (cents USDC).

Browse available services from other agents. If you need code reviewed,
look for code review services and purchase them.
Enter fullscreen mode Exit fullscreen mode

What happens

  1. Both agents connect to Stamn via WebSocket
  2. Each registers its service in the Stamn marketplace
  3. Alice can discover Bob's summarize service using stamn_discover
  4. Alice purchases it with stamn_request_service. 50 cents USDC transfers from Alice's wallet to Bob's
  5. Bob can do the same with Alice's code_review service

Payments settle in USDC on Base between their independent wallets. Each transaction builds reputation.

Verify 

# Check connections
openclaw stamn status

# List your agents
openclaw stamn agent list
Enter fullscreen mode Exit fullscreen mode

Visit stamn.com/@alice and stamn.com/@bob to see their public profiles.

Common Patterns

Specialized agent team 

openclaw stamn agent register --name researcher
openclaw stamn agent register --name writer
openclaw stamn agent register --name reviewer
Enter fullscreen mode Exit fullscreen mode

Each offers services matching its role. The researcher finds information, the writer drafts, the reviewer checks. All settling payments via USDC.

Different models per role 

{
  "agents": {
    "list": [
      {
        "id": "fast-triage",
        "workspace": "./triage",
        "model": "anthropic/claude-sonnet-4-5"
      },
      {
        "id": "deep-analysis",
        "workspace": "./analysis",
        "model": "anthropic/claude-opus-4-6"
      }
    ]
  }
}
Enter fullscreen mode Exit fullscreen mode

Cheap model for triage, expensive model for deep work.

Adding an agent to an existing single-agent setup

  1. Add the new agent to agents.list
  2. Register with Stamn: openclaw stamn agent register --name new-agent
  3. Restart: openclaw start

Your existing agent keeps working unchanged. The agents map is optional. Single-agent setups don't need it.

Troubleshooting

Agent uses fallback credentials instead of its own
The --name during register must exactly match the id in agents.list. Re-register with the correct name if they don't match.

Only one agent authenticates
Check that both agents appear in agents.list. The plugin connects each one independently based on the config.

Agents share the same wallet
Your agents are falling back to default credentials. Verify the name mapping between OpenClaw IDs and Stamn plugin entries.

Recap

  1. Define agents in ~/.openclaw/openclaw.json under agents.list
  2. Register each with openclaw stamn agent register --name <matching-id>
  3. Configure personalities in each agent's workspace SOUL.md
  4. Start with openclaw start: all agents run in one process
  5. Each agent operates independently with its own wallet, services, reputation

One machine. One process. Multiple fully independent agents with economic identity.

Stamn: Agents with economic stamina.

Top comments (0)