Openclaw agents Commands Guide: Manage Multiple AI Agents

Table of contents: [Show]

Quick Start

The openclaw agents command lets you create and manage multiple isolated AI agents. Each agent can have its own workspace, model, and channel bindings.

Managing Agents

List All Agents

View your configured agents with optional bindings and JSON output:

openclaw agents list

Options:

• --bindings - Shows routing bindings
• --json - Machine-readable output

Add a New Agent

Create an agent interactively or bypass the wizard:

openclaw agents add work --workspace ~/.openclaw/workspace-work

Available options:

• --workspace <dir> - Set workspace directory
• --model <id> - Specify model
• --bind <channel[:accountId]> - Bind to channels (repeatable)
• --non-interactive - Skip wizard (requires --workspace)

Routing Bindings

Bindings connect channels to specific agents. For more on channel management, see our guide on Channels Command List.

List Bindings

openclaw agents bindings --agent work

Bind an Agent

Route channel traffic to a specific agent:

openclaw agents bind --agent work --bind telegram:ops --bind discord:guild-a

Use * as accountId for channel-wide fallback:

openclaw agents bind --agent default --bind telegram:*

Unbind an Agent

Remove specific bindings or all at once:

openclaw agents unbind --agent work --bind telegram:ops openclaw agents unbind --agent work --all

Agent Identity

Set your agent personality and appearance. If you are configuring multiple agents, you might also want to review our Config Commands Guide for additional settings.

Set Identity Manually

openclaw agents set-identity --agent main --name "OpenClaw" --emoji "🤖" --avatar avatars/openclaw.png

Load from IDENTITY.md

openclaw agents set-identity --workspace ~/.openclaw/workspace --from-identity

Complete Example

Create a work agent with full setup:

openclaw agents add work --workspace ~/.openclaw/workspace-work --model openai/gpt-4 --bind slack:team-a

Troubleshooting

• Binding conflicts: Upgrading a channel-only binding to an explicit account binding updates in-place (no duplicates)
• Non-interactive fails: Always include --workspace with --non-interactive
• Avatar not showing: Use absolute path or valid URL for avatar

Best Practices

• Use descriptive agent names (e.g., work, personal, support)
• Bind specific accounts for production agents, use wildcards for fallbacks
• Keep workspace directories organized and separate
• Use IDENTITY.md files for consistent agent branding