clm agent
Manage agent lifecycle: install, configure, start, stop, and monitor agents.
Synopsis
clm agent <command> [options]
Commands
install
Install an agent on a host.
clm agent install <agent-type> --host <host> --name <agent-name> [options]
Arguments:
agent-type- Type of agent to install (e.g.,openclaw,zeroclaw,nanoclaw)
Options:
--host <hostname>- Target host (required)--name <name>- Agent instance name (required)--version <version>- Specific version to install (default: latest)--user <username>- User to run the agent as (default: from manifest)
Examples:
# Install latest openclaw
clm agent install openclaw --host lab1 --name opc-work
# Install specific version
clm agent install zeroclaw --host pi4 --name zc-edge --version 2026.3.0
# Install with custom user
clm agent install openclaw --host lab2 --name opc-dev --user alice
What happens:
- Verifies host compatibility
- Downloads agent package
- Deploys to host
- Initializes onboarding (state: PENDING)
- Returns installation summary
Success output:
✓ Installed openclaw v2026.4.2 on lab1
✓ Agent: opc-work
✓ Status: PENDING (onboarding required)
Next step: clm agent configure opc-work
Related:
- clm registry show - Check agent requirements before install
- clm agent configure - Configure the installed agent
configure
Configure an agent through interactive onboarding wizard.
clm agent configure <agent-name> [options]
Arguments:
agent-name- Name of the agent to configure
Options:
--stage <stage>- Configure specific stage only (providers, identity, channels, validate)--yes- Accept defaults and skip confirmations--provider <id>- Pre-select provider (skips provider selection prompt)
Examples:
# Full interactive wizard
clm agent configure opc-work
# Configure specific stage
clm agent configure opc-work --stage providers
clm agent configure opc-work --stage identity
# Non-interactive (use defaults)
clm agent configure opc-work --yes
# Pre-select provider
clm agent configure opc-work --provider openai-prod --yes
Stages:
| Stage | Purpose | Skippable? |
|---|---|---|
| providers | Assign inference provider | No |
| identity | Configure personality/behavior | Depends on agent type |
| channels | Set up communication methods | Depends on agent type |
| validate | Verify configuration | No |
Interactive wizard flow:
$ clm agent configure opc-work
Starting onboarding for 'opc-work' (openclaw)
Current state: PENDING
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
[1/4] PROVIDERS - Select Inference Provider
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Available providers:
1. openai-prod (OpenAI GPT-4)
2. local-ollama (Ollama - llama3:latest)
Select provider [1-2]: 1
✓ Provider 'openai-prod' assigned
[... continues through remaining stages ...]
✓ Onboarding complete! 'opc-work' is ready to start.
Related:
- Agent Onboarding Guide - Detailed onboarding walkthrough
- clm agent status - Check configuration progress
start
Start a configured agent.
clm agent start <agent-name> [options]
Arguments:
agent-name- Name of the agent to start
Options:
--wait- Wait for agent to be fully running before returning--timeout <seconds>- Max wait time (default: 30)
Examples:
# Start agent
clm agent start opc-work
# Start and wait for confirmation
clm agent start opc-work --wait
# Start with custom timeout
clm agent start opc-work --wait --timeout 60
Requirements:
- Agent must be in READY state (onboarding complete)
- Host must be reachable
- Required secrets must be set
Success output:
✓ Starting 'opc-work' on lab1...
✓ Agent started successfully
Error: Onboarding incomplete:
✗ Cannot start 'opc-work' - onboarding incomplete
Status: ONBOARDING (2/4 stages)
Remaining stages:
- channels
- validate
Complete onboarding: clm agent configure opc-work
Related:
- clm agent stop - Stop a running agent
- clm agent status - Check if agent is running
stop
Stop a running agent.
clm agent stop <agent-name> [options]
Arguments:
agent-name- Name of the agent to stop
Options:
--force- Force stop (send SIGKILL instead of graceful shutdown)--timeout <seconds>- Wait time before force kill (default: 10)
Examples:
# Graceful stop
clm agent stop opc-work
# Force stop immediately
clm agent stop opc-work --force
# Graceful with custom timeout
clm agent stop opc-work --timeout 30
Success output:
✓ Stopping 'opc-work' on lab1...
✓ Agent stopped successfully
Related:
- clm agent start - Start a stopped agent
- clm agent restart - Restart a running agent
restart
Restart a running agent (stop + start).
clm agent restart <agent-name> [options]
Arguments:
agent-name- Name of the agent to restart
Options:
--wait- Wait for agent to be fully running after restart--force- Force stop before restart
Examples:
# Restart agent
clm agent restart opc-work
# Force restart
clm agent restart opc-work --force
# Restart and wait for confirmation
clm agent restart opc-work --wait
Success output:
✓ Stopping 'opc-work' on lab1...
✓ Agent stopped
✓ Starting 'opc-work' on lab1...
✓ Agent started successfully
status
Display agent status and health information.
clm agent status [agent-name] [options]
Arguments:
agent-name- Specific agent to check (optional - shows all if omitted)
Options:
--verbose- Show detailed information including onboarding progress--json- Output in JSON format
Examples:
# Show all agents
clm agent status
# Show specific agent
clm agent status opc-work
# Detailed view with onboarding progress
clm agent status opc-work --verbose
# JSON output for scripting
clm agent status --json
Output (all agents):
Agent Status:
┌──────────┬──────┬───────┬─────────────┬──────────┐
│ Name │ Host │ Type │ Status │ Progress │
├──────────┼──────┼───────┼─────────────┼──────────┤
│ opc-work │ lab1 │ opc │ RUNNING │ 4/4 │
│ zc-edge │ pi4 │ zc │ READY │ 4/4 │
│ opc-home │ lab1 │ opc │ ONBOARDING │ 2/4 │
│ nc-test │ lab2 │ nc │ PENDING │ 0/4 │
└──────────┴──────┴───────┴─────────────┴──────────┘
Output (verbose):
$ clm agent status opc-work --verbose
Agent: opc-work
Host: lab1 (192.168.1.100)
Type: openclaw v2026.4.2
Status: RUNNING
Process ID: 12345
Uptime: 2d 5h 32m
Onboarding: COMPLETE (4/4 stages)
✓ PROVIDERS (completed 2026-04-05 10:02:00 UTC)
Provider: openai-prod (OpenAI GPT-4)
✓ IDENTITY (completed 2026-04-05 10:05:00 UTC)
Files: SOUL.md, IDENTITY.md
✓ CHANNELS (completed 2026-04-05 10:07:00 UTC)
Default: CLI
✓ VALIDATE (completed 2026-04-05 10:08:00 UTC)
Resource Usage:
CPU: 2.3%
Memory: 245 MB
Disk: 1.2 GB
Health: HEALTHY
Last check: 2026-04-07 15:30:00 UTC
Response time: 120ms
Status values:
| Status | Description | Can Start? |
|---|---|---|
PENDING | Installed, onboarding not started | ❌ No |
ONBOARDING | Configuration in progress | ❌ No |
READY | Configured, not running | ✅ Yes |
RUNNING | Active and operational | - |
STOPPED | Previously running, now stopped | ✅ Yes |
ERROR | Configuration or runtime error | ❌ No |
Related:
- clm agent logs - View agent logs
- Agent Onboarding Guide - Understanding onboarding states
logs
View agent logs.
clm agent logs <agent-name> [options]
Arguments:
agent-name- Name of the agent
Options:
--follow/-f- Stream logs in real-time--lines <n>/-n <n>- Number of lines to show (default: 50)--since <time>- Show logs since timestamp (e.g., "2h", "30m", "2024-01-01")--level <level>- Filter by log level (debug, info, warn, error)
Examples:
# Show last 50 lines
clm agent logs opc-work
# Show last 200 lines
clm agent logs opc-work --lines 200
# Follow logs in real-time
clm agent logs opc-work --follow
# Show logs from last 2 hours
clm agent logs opc-work --since 2h
# Show only errors
clm agent logs opc-work --level error
Output:
2026-04-07 15:30:15 [INFO] Agent started successfully
2026-04-07 15:30:16 [INFO] Connected to provider: openai-prod
2026-04-07 15:30:17 [INFO] Ready to accept requests
2026-04-07 15:32:45 [INFO] Processing request: "What's the weather?"
2026-04-07 15:32:47 [INFO] Request completed (2.1s)
Related:
- clm agent status - Check agent health
- Troubleshooting Guide - Debugging common issues
remove
Remove an agent from a host.
clm agent remove <agent-name> [options]
Arguments:
agent-name- Name of the agent to remove
Options:
--force- Skip confirmation prompt--keep-data- Preserve agent data and configuration files
Examples:
# Remove with confirmation
clm agent remove opc-work
# Force remove (no prompt)
clm agent remove opc-work --force
# Remove but keep data
clm agent remove opc-work --keep-data
Interactive prompt:
Remove agent 'opc-work' from host 'lab1'?
This will:
- Stop the agent (if running)
- Remove the installation
- Delete configuration and data
Are you sure? [y/N]: y
✓ Stopping agent...
✓ Removing installation...
✓ Cleaning up data...
✓ Agent 'opc-work' removed from lab1
Warning: By default, removal is permanent and deletes all agent data including:
- Configuration files
- Identity files (SOUL.md, IDENTITY.md)
- Logs and session history
- Cache and temporary files
Use --keep-data to preserve these files for later reinstallation.
list
List all installed agents across the fleet.
clm agent list [options]
Options:
--host <hostname>- Filter by host--type <agent-type>- Filter by agent type--status <status>- Filter by status (pending, onboarding, ready, running, stopped, error)--json- Output in JSON format
Examples:
# List all agents
clm agent list
# List agents on specific host
clm agent list --host lab1
# List all openclaw instances
clm agent list --type openclaw
# List running agents only
clm agent list --status running
# JSON output
clm agent list --json
Output:
Installed Agents (4):
┌──────────┬──────┬─────────┬─────────────┬────────────┐
│ Name │ Host │ Type │ Version │ Status │
├──────────┼──────┼─────────┼─────────────┼────────────┤
│ opc-work │ lab1 │ openclaw│ 2026.4.2 │ RUNNING │
│ opc-home │ lab1 │ openclaw│ 2026.4.2 │ READY │
│ zc-edge │ pi4 │ zeroclaw│ 2026.3.1 │ RUNNING │
│ nc-test │ lab2 │ nanoclaw│ 2026.2.0 │ ONBOARDING │
└──────────┴──────┴─────────┴─────────────┴────────────┘
upgrade
Upgrade an agent to a newer version.
clm agent upgrade <agent-name> [options]
Arguments:
agent-name- Name of the agent to upgrade
Options:
--version <version>- Upgrade to specific version (default: latest)--restart- Restart agent after upgrade (if it was running)
Examples:
# Upgrade to latest version
clm agent upgrade opc-work
# Upgrade to specific version
clm agent upgrade opc-work --version 2026.5.0
# Upgrade and restart
clm agent upgrade opc-work --restart
Output:
Agent: opc-work
Current version: 2026.4.2
Latest version: 2026.5.1
Upgrading to v2026.5.1...
✓ Downloaded package
✓ Stopped agent
✓ Installed new version
✓ Started agent
✓ Upgrade complete
opc-work is now running v2026.5.1
Note:
- Onboarding configuration is preserved during upgrades
- Secrets and identity files are not affected
- Agent is stopped during upgrade (use
--restartto auto-start)
Related Commands
clm provider
Manage inference providers used by agents.
clm provider list # List configured providers
clm provider add # Add new provider
clm provider remove # Remove provider
See clm provider for full reference.
clm secret
Manage agent secrets and API keys.
clm secret set <agent> <key> # Set secret value
clm secret list <agent> # List required secrets
clm secret remove <agent> <key> # Remove secret
See clm secret for full reference.
clm registry
Browse available agent types.
clm registry list # List available agents
clm registry show <type> # Show agent details
See clm registry for full reference.
Exit Codes
| Code | Meaning |
|---|---|
| 0 | Success |
| 1 | General error |
| 2 | Invalid arguments |
| 3 | Agent not found |
| 4 | Host unreachable |
| 5 | Onboarding incomplete |
| 6 | Permission denied |
Example usage in scripts:
#!/bin/bash
clm agent start opc-work
if [ $? -eq 5 ]; then
echo "Onboarding required"
clm agent configure opc-work --yes
clm agent start opc-work
fi
Environment Variables
| Variable | Description | Default |
|---|---|---|
CLAWRIUM_CONFIG | Config directory path | ~/.config/clawrium |
CLAWRIUM_LOG_LEVEL | Logging verbosity | info |
CLAWRIUM_TIMEOUT | Default operation timeout (seconds) | 30 |
See Also
- Agent Onboarding Guide - Detailed onboarding walkthrough
- Fleet Management Guide - Managing multiple agents
- Secret Management Guide - Working with API keys
- Troubleshooting - Common issues and solutions