Menu
Server Operations Toolkit — Monitoring, Log Analysis, Service Management, Docker (服务器运维工具集 — 监控巡检、日志分析、服务管理、Docker容器管理)
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
| name | ops-toolkit |
| description | Server Operations Toolkit — Monitoring, Log Analysis, Service Management, Docker (服务器运维工具集 — 监控巡检、日志分析、服务管理、Docker容器管理) |
| version | 2.0.0 |
| category | devops |
| license | MIT |
| author | dockercore |
| triggers | ["运维","巡检","监控","服务器状态","server health","log analysis","日志分析","故障排查","troubleshooting","服务管理","service management","docker管理","docker management","容器管理","container management","sre"] |
A comprehensive Linux/macOS server operations skill covering 4 modules: Monitoring, Log Analysis, Service Management, and Docker Management. 全面的 Linux/macOS 服务器运维 skill，覆盖监控巡检、日志分析、服务管理、Docker 容器管理四大模块。
Run the built-in health check script to automatically inspect CPU, memory, disk, network, processes, services, and Docker: 运行内置巡检脚本，自动检查 CPU、内存、磁盘、网络、进程、服务、Docker 状态：
# Quick mode (default) — for daily checks / 快速模式（默认）—— 适合日常巡检
bash ~/.hermes/skills/devops/ops-toolkit/scripts/health-check.sh --quick
# Full mode — includes network interfaces, container details / 完整模式 —— 包含网络接口详情、容器详情等
bash ~/.hermes/skills/devops/ops-toolkit/scripts/health-check.sh --full
# Show help / 显示帮助
bash ~/.hermes/skills/devops/ops-toolkit/scripts/health-check.sh --help
Expected Output / 期望输出：
=========================================
服务器健康巡检 2026-04-14 14:36:20
系统: Darwin
=========================================
[系统信息]
主机名: zailing
内核: 25.4.0
运行时间: up 7 days, 23:51
当前用户: dockercore
[CPU]
[OK] CPU 使用率 51%
CPU 核心数: 8
负载均值: 10.75 8.35 7.25
[内存]
[OK] 内存使用率 8% (1340M/16384M)
可用内存: 694M
[WARN] Swap 使用率 95% (6836M/7168M)
[磁盘]
[OK] 挂载: / 大小: 460Gi 已用: 12Gi 可用: 46Gi 使用率: 21%
[WARN] 挂载: /System/Volumes/Data 大小: 460Gi 已用: 375Gi 可用: 46Gi 使用率: 89%
[网络]
[OK] 监听端口数: 20
端口列表: 80 3306 5000 8080 ...
[进程]
[OK] 进程总数: 565
[OK] 无僵尸进程
[Docker]
[OK] Docker 守护进程运行中
运行容器: 5
镜像数: 12
=========================================
巡检完成
=========================================
Output Legend / 输出图例：
[OK] = Normal / 正常[WARN] = Warning, needs attention / 警告，需要关注[FAIL] = Critical, must fix immediately / 严重，必须立即处理# Real-time CPU usage (1-second sample) / 实时 CPU 使用率（采样1秒）
# Linux:
top -bn1 | grep "Cpu(s)" | awk '{print "User: "$2", System: "$4", Idle: "$8}'
# macOS:
top -l 1 -n 0 | grep "CPU usage"
# CPU core count / CPU 核心数
nproc # Linux
sysctl -n hw.ncpu # macOS
# Load average (1min/5min/15min) / 负载均值（1分钟/5分钟/15分钟）
# Load average = average number of processes waiting for CPU
# 负载均值 = 等待 CPU 的平均进程数
# Rule of thumb: load < core count = healthy
# 经验法则：负载 < 核心数 = 健康
cat /proc/loadavg # Linux
sysctl -n vm.loadavg # macOS
# Per-core CPU usage / 按核心查看 CPU 使用率
mpstat -P ALL 1 1 # Requires sysstat package / 需要 sysstat 包
# Top 10 CPU-consuming processes / 高 CPU 进程 Top 10
ps aux --sort=-%cpu | head -11 # Linux
ps aux -r | head -11 # macOS
What is Load Average? / 什么是负载均值？
# Memory overview (MB) / 内存使用概览（MB）
free -m # Linux
vm_stat # macOS (pages, multiply by 4096 for bytes)
# Memory details / 内存使用详情
cat /proc/meminfo | head -20 # Linux
sysctl -n hw.memsize # macOS: total physical memory
# Top 10 memory-consuming processes / 内存 Top 10 进程
ps aux --sort=-%mem | head -11 # Linux
ps aux -m | head -11 # macOS
# Continuous monitoring (refresh every 2s) / 持续监控内存（每2秒刷新）
watch -n2 free -m # Press Ctrl+C to stop / 按 Ctrl+C 停止
Understanding Memory: / 理解内存：
used = memory currently in use / 当前使用的内存free = completely unused memory / 完全未使用的内存available = memory available for new programs (includes cache that can be freed)available = 可分配给新程序的内存（含可释放的缓存）buffers/cache = disk cache, automatically freed when neededbuffers/cache = 磁盘缓存，需要时自动释放free is low — Linux uses free memory for cachefree 很低不要慌 — Linux 会把空闲内存用作缓存# Disk usage overview / 磁盘使用概览
df -hT -x tmpfs -x devtmpfs # Linux
df -h # macOS
# Inode usage (filesystem can run out of inodes even with free space)
# Inode 使用率（即使空间有余，Inode 耗尽也会报错）
df -i -x tmpfs -x devtmpfs # Linux only
# Top 10 largest directories / 大目录 Top 10
du -ah /path 2>/dev/null | sort -rh | head -10
# Mount details / 挂载详情
findmnt # Linux
mount # macOS
# Disk I/O statistics / 磁盘 I/O 统计
iostat -xz 1 3 # Requires sysstat / 需要 sysstat 包
What are Inodes? / 什么是 Inode？
# Listening ports / 监听端口
ss -tlnp # Linux
lsof -iTCP -sTCP:LISTEN -P -n # macOS
# Connection statistics / 网络连接统计
ss -s # Linux
netstat -s # macOS
# Connections by state / 各状态连接数
ss -ant | awk '{print $1}' | sort | uniq -c | sort -rn
# Network interface traffic / 网络接口流量
ip -s link show eth0 # Linux
netstat -I en0 # macOS (replace en0 with your interface)
# Real-time bandwidth monitoring / 实时带宽监控
iftop -i eth0 # Requires iftop
nload # Requires nload
# Top IPs by connection count / 连接数 Top IP（排查异常访问）
ss -nt | awk '{print $5}' | cut -d: -f1 | sort | uniq -c | sort -rn | head -10
# Process tree / 进程树
ps auxf # Linux
ps aux # macOS
# Find zombie processes / 僵尸进程
ps aux | awk '$8=="Z"'
# File handles by process / 占用文件句柄最多的进程
lsof 2>/dev/null | awk '{print $1}' | sort | uniq -c | sort -rn | head -10
# Total open file handles / 系统打开文件句柄总数
cat /proc/sys/fs/file-nr # Linux only
# Process resource usage / 某进程的详细资源占用
pidstat -p <PID> 1 5 # Linux, requires sysstat
# View recent system logs / 查看最近系统日志
journalctl -n 50 --no-pager
# By time range / 按时间范围查看
journalctl --since "2024-01-01" --until "2024-01-02"
# By priority (0=emerg ... 7=debug) / 按优先级过滤
journalctl -p err -n 50 # Show errors only / 只看错误
# By service / 按服务过滤
journalctl -u nginx.service --since "1 hour ago"
# Follow logs in real-time / 实时跟踪日志
journalctl -f # Press Ctrl+C to stop / 按 Ctrl+C 停止
# Kernel logs / 内核日志
dmesg -T -l err,warn | tail -20 # Linux only
# Search for keyword in log directory / 在日志目录中搜索关键词
grep -rn "ERROR" /var/log/ --include="*.log" | tail -20
# Search by time range / 按时间区间搜索
awk '/2024-01-15 10:00/,/2024-01-15 11:00/' /var/log/app.log
# Error type distribution / 统计错误类型分布
grep "ERROR" /var/log/app.log | awk -F'[: ]' '{print $1}' | sort | uniq -c | sort -rn | head -10
# HTTP status code distribution (Nginx) / 提取 HTTP 状态码分布
awk '{print $9}' /var/log/nginx/access.log | sort | uniq -c | sort -rn
# Slow requests (>5 seconds) / 慢请求（超过5秒的请求）
awk '$NF > 5 {print $0}' /var/log/nginx/access.log | tail -20
# Top IPs by request count / 查找 IP 访问频率（排查异常访问）
awk '{print $1}' /var/log/nginx/access.log | sort | uniq -c | sort -rn | head -20
| Service 服务 | Path 路径 |
|---|---|
| System 系统 | /var/log/syslog or /var/log/messages |
| Auth 认证 | /var/log/auth.log or /var/log/secure |
| Nginx | /var/log/nginx/access.log, /var/log/nginx/error.log |
| MySQL | /var/log/mysql/error.log |
| PostgreSQL | /var/log/postgresql/ |
| Docker | journalctl -u docker.service |
| App 应用 | /var/log/app/, /opt/app/logs/ |
health-check.sh --full 获取全局状态journalctl -p err --since "1 hour ago"journalctl -u <service> --since "30 min ago"top / iotop / iftop 定位 CPU/IO/网络瓶颈df -h 确认未满cat /proc/sys/fs/file-nr and lsof | wc -lcurl -v <url> / telnet <host> <port> / traceroute <host># Check service status / 查看服务状态
systemctl status <service>
# Example / 示例:
systemctl status nginx
# Start/Stop/Restart / 启动/停止/重启
systemctl start <service> # Start a stopped service / 启动已停止的服务
systemctl stop <service> # Stop a running service / 停止运行中的服务
systemctl restart <service> # Stop then start (brief downtime) / 停止再启动（短暂中断）
# Reload config (no downtime) / 重载配置（不中断服务）
systemctl reload <service> # Reloads config without stopping / 不停止服务重载配置
# Enable/Disable autostart / 开机自启
systemctl enable <service> # Start automatically on boot / 开机自动启动
systemctl disable <service> # Don't start on boot / 开机不启动
# List failed services / 查看所有失败的服务
systemctl --failed
# View service logs / 查看服务日志
journalctl -u <service> -n 50 --no-pager
# List running services / 列出所有活跃服务
systemctl list-units --type=service --state=running
# View service dependencies / 查看服务依赖
systemctl list-dependencies <service>
| Application 应用 | Service Name 服务名 |
|---|---|
| Nginx | nginx |
| Apache | apache2 / httpd |
| MySQL | mysql / mysqld |
| PostgreSQL | postgresql |
| Redis | redis / redis-server |
| Docker | docker / dockerd |
| SSH | sshd |
| Cron | cron / crond |
| Firewall | ufw / firewalld |
# Find process by keyword / 查找进程
pgrep -af <keyword>
# Example / 示例: pgrep -af nginx
# Terminate process / 终止进程
kill <PID> # SIGTERM: graceful stop / 优雅终止
kill -9 <PID> # SIGKILL: force kill (data loss risk!) / 强制终止（有数据丢失风险！）
# Kill by name / 按名称终止
pkill -f <pattern>
killall <process_name>
# Check which port a process uses / 查看进程占用的端口
ss -tlnp | grep <PID> # Linux
lsof -i -P -n | grep <PID> # macOS
SIGTERM vs SIGKILL: / SIGTERM 和 SIGKILL 的区别：
kill (SIGTERM, signal 15): Asks the process to shut down gracefully. The process can clean up.kill (SIGTERM, 信号15): 请求进程优雅退出。进程可以清理资源。kill -9 (SIGKILL, signal 9): Immediately kills the process. No cleanup. May cause data corruption.kill -9 (SIGKILL, 信号9): 立即杀死进程。无法清理。可能导致数据损坏。kill first. Only use kill -9 as last resort.kill。kill -9 只作为最后手段。# UFW (Ubuntu)
ufw status # Check status / 查看状态
ufw allow 80/tcp # Allow port 80 / 允许端口 80
ufw deny 3306/tcp # Deny port 3306 / 拒绝端口 3306
# firewalld (CentOS/RHEL)
firewall-cmd --list-all # List all rules / 列出所有规则
firewall-cmd --add-port=80/tcp --permanent # Allow port 80 permanently / 永久允许端口 80
firewall-cmd --reload # Apply changes / 应用更改
# iptables
iptables -L -n -v # List all rules / 列出所有规则
# List containers / 列出容器
docker ps # Running containers only / 只看运行中的
docker ps -a # All containers (including stopped) / 所有（含停止的）
# Start/Stop/Restart / 启动/停止/重启
docker start <container> # Start a stopped container / 启动停止的容器
docker stop <container> # Gracefully stop (10s timeout) / 优雅停止（10秒超时）
docker restart <container> # Stop then start / 停止再启动
# Create and start / 创建并启动
docker run -d --name myapp -p 8080:80 nginx:latest
# -d = detached (background) / 后台运行
# --name = container name / 容器名
# -p 8080:80 = host port 8080 -> container port 80 / 宿主机8080映射到容器80
# Remove container / 删除容器
docker rm <container> # Remove stopped container / 删除停止的容器
docker rm -f <container> # Force remove (even if running) / 强制删除（含运行中的）
# Clean up all stopped containers / 清理所有停止的容器
docker container prune -f
# View container logs / 查看容器日志
docker logs <container> # All logs / 所有日志
docker logs --tail 100 -f <container> # Last 100 lines, follow / 最近100行，实时跟踪
docker logs --since 1h <container> # Last 1 hour / 最近1小时
docker logs --since "2024-01-15T10:00:00" <container> # Since specific time / 从指定时间
# Enter container / 进入容器
docker exec -it <container> bash # Use bash shell / 使用 bash
docker exec -it <container> sh # Use sh (if no bash) / 使用 sh（无 bash 时）
# Resource usage / 查看容器资源使用
docker stats # All containers, real-time / 所有容器，实时
docker stats <container> # Single container / 单个容器
# Container details / 查看容器详情
docker inspect <container>
# Container processes / 查看容器进程
docker top <container>
# Port mappings / 容器端口映射
docker port <container>
# List images / 列出镜像
docker images
# Pull image / 拉取镜像
docker pull <image>:<tag> # Example / 示例: docker pull nginx:1.25
# Build image / 构建镜像
docker build -t myapp:v1 . # Build from Dockerfile in current directory
# Remove image / 删除镜像
docker rmi <image>
# Clean up dangling images / 清理悬空镜像（无标签的中间镜像）
docker image prune -f
# Image details / 镜像详情
docker inspect <image>
# Image layers / 镜像历史（查看构建层）
docker history <image>
# Start stack / 启动服务栈
docker compose up -d # -d = detached / 后台运行
# Stop / 停止
docker compose down # Stop and remove containers / 停止并删除容器
docker compose down -v # Also remove volumes / 同时删除数据卷
# Status / 查看状态
docker compose ps
# Logs / 查看日志
docker compose logs -f <service> # Follow logs for a service / 跟踪某个服务的日志
# Restart single service / 重启单个服务
docker compose restart <service>
# Pull latest and rebuild / 拉取最新镜像并重建
docker compose pull
docker compose up -d --build
# Scale / 扩容
docker compose up -d --scale <service>=3 # Run 3 instances / 运行3个实例
# Docker disk usage / Docker 磁盘使用
docker system df
# Full cleanup (stopped containers, dangling images, unused networks, build cache)
# 全面清理（停止容器、悬空镜像、未用网络、构建缓存）
docker system prune -f
# Deep cleanup (also removes all unused images)
# 深度清理（含所有未使用镜像）— WARNING: re-download needed next time
# 警告：下次使用需要重新下载
docker system prune -a -f
# Clean build cache / 清理构建缓存
docker builder prune -f
# Clean volumes / 清理卷（WARNING: deletes data! / 警告：会删除数据！）
docker volume prune -f
What each prune removes: / 各清理命令删除什么：
| Command 命令 | Removes 删除内容 | Risk 风险 |
|---|---|---|
docker system prune -f | Stopped containers, dangling images, unused networks, build cache | Low / 低 |
docker system prune -a -f | Above + all unused images | Medium (need re-pull) / 中（需重新拉取） |
docker volume prune -f | Unused volumes | HIGH (data loss!) / 高（数据丢失！） |
docker image prune -f | Dangling images only | Low / 低 |
docker builder prune -f | Build cache | Low / 低 |
| Metric 指标 | Warning 警告 | Critical 严重 | Explanation 说明 |
|---|---|---|---|
| CPU usage | >70% | >90% | Server may become unresponsive / 服务器可能无响应 |
| Memory usage | >80% | >90% | OOM killer may trigger / 可能触发 OOM 杀进程 |
| Swap usage | >30% | >50% | Excessive swap = slow performance / 大量 Swap = 性能差 |
| Disk usage | >80% | >90% | Risk of write failure / 写入可能失败 |
| Inode usage | >80% | >90% | Cannot create new files / 无法创建新文件 |
| Zombie processes | >0 | >5 | May indicate bugs / 可能存在程序缺陷 |
| Load (1min) | >cores*0.7 | >cores | CPU overloaded / CPU 过载 |
# Step 1: Check CPU / 第1步：检查 CPU
top -bn1 | head -20 # Look for high CPU% / 找高 CPU% 的进程
# Step 2: Check memory / 第2步：检查内存
free -m # Is swap being used heavily? / Swap 是否大量使用？
# Step 3: Check disk I/O / 第3步：检查磁盘 I/O
iostat -xz 1 3 # High %util = disk bottleneck / %util 高 = 磁盘瓶颈
# Step 4: Check load / 第4步：检查负载
cat /proc/loadavg # Compare with core count / 对比核心数
# Step 1: Which filesystem? / 第1步：哪个分区满了？
df -h
# Step 2: Find large files / 第2步：找大文件
du -ah / 2>/dev/null | sort -rh | head -20
# Step 3: Check inodes / 第3步：检查 inode
df -i
# Step 4: Clean up / 第4步：清理
docker system prune -f # Clean Docker / 清理 Docker
journalctl --vacuum-size=100M # Shrink system logs / 缩减系统日志
# Step 1: Check status / 第1步：查看状态
systemctl status <service>
# Step 2: View logs / 第2步：查看日志
journalctl -u <service> --since "30 min ago"
# Step 3: Restart / 第3步：尝试重启
systemctl restart <service>
# Step 4: Verify / 第4步：验证恢复
systemctl status <service>
curl -s http://localhost:<port>/ # Health check / 健康检查
# Step 1: Check container status / 第1步：查看容器状态
docker ps -a # Look for "Restarting" / 找 "Restarting" 状态
# Step 2: View container logs / 第2步：查看容器日志
docker logs --tail 100 <container>
# Step 3: Inspect restart policy / 第3步：检查重启策略
docker inspect <container> | grep -A5 RestartPolicy
# Step 4: Run interactively to debug / 第4步：交互运行调试
docker run -it --rm <image> sh # Run once, don't auto-restart / 运行一次，不自动重启
# Step 1: Top memory processes / 第1步：找内存大户
ps aux --sort=-%mem | head -11
# Step 2: Check if swap is abused / 第2步：检查 Swap 是否被滥用
free -m
# Step 3: Check for memory leaks / 第3步：检查是否有内存泄漏
pidstat -r -p <PID> 1 10 # Watch RSS growth / 观察 RSS 增长
# Step 1: Connection count by state / 第1步：按状态统计连接数
ss -ant | awk '{print $1}' | sort | uniq -c | sort -rn
# Step 2: Top IPs by connections / 第2步：连接数最多的 IP
ss -nt | awk '{print $5}' | cut -d: -f1 | sort | uniq -c | sort -rn | head -20
# Step 3: Check if a port is flooded / 第3步：检查某端口是否被淹没
ss -tn | grep :80 | wc -l
# Step 4: Block abusive IPs / 第4步：封禁恶意 IP
iptables -A INPUT -s <bad_ip> -j DROP
systemctl, no journalctl, no free, no /proc filesystem. macOS uses vm_stat, top -l 1, lsof, sysctl instead.sudo (e.g., iptables, lsof for other users' processes, Docker for non-docker group users).wc -l to avoid hanging.log-driver and log-opts in production to limit log size. Add to /etc/docker/daemon.json: {"log-driver": "json-file", "log-opts": {"max-size": "10m", "max-file": "3"}}.kill -9 risk / kill -9 风险: Force kill may cause data loss. Always prefer kill (SIGTERM) first.docker system prune -a / 深度清理风险: Removes ALL unused images. Next deploy will need to re-pull. Confirm before running.-e TZ=Asia/Shanghai or mount /etc/localtime./dev disk 100%: This is normal for devfs virtual filesystem, not an actual problem. Can be safely ignored in health check reports.This skill can be used in three popular AI agents. Below are quick-start instructions. 此技能可在三大主流 AI 智能体中使用，以下是快速上手指南。
Setup / 配置:
# Add CLAUDE.md to your project root / 在项目根目录添加 CLAUDE.md
cat >> CLAUDE.md << 'EOF'
## SRE Ops-Toolkit
Health check script: bash scripts/health-check.sh --full
Key commands:
- Quick check: bash scripts/health-check.sh --quick
- Full check: bash scripts/health-check.sh --full
- Help: bash scripts/health-check.sh --help
EOF
# Custom slash command / 自定义斜杠命令
mkdir -p .claude/commands
cat > .claude/commands/health-check.md << 'EOF'
Run the server health check and analyze results:
1. Execute: bash scripts/health-check.sh --full
2. Analyze any [WARN] or [FAIL] items
3. Suggest fixes for each issue found
EOF
# Custom SRE Agent / 自定义 SRE Agent
mkdir -p .claude/agents
cat > .claude/agents/sre-operator.md << 'EOF'
---
name: sre-operator
description: SRE operations and health check agent
model: sonnet
tools: [Read, Bash]
---
You are an SRE operator. When asked about server health:
1. Run health-check.sh with appropriate flags
2. Analyze the output for warnings and failures
3. Provide actionable fix recommendations
4. For critical issues, suggest immediate mitigation steps
EOF
Usage / 使用:
# Print mode (one-shot) / 一次性模式
claude -p "运行服务器巡检并分析结果" --allowedTools 'Read,Bash' --max-turns 10
# Interactive mode / 交互模式
claude "帮我检查服务器健康状态，分析巡检报告"
# With custom agent / 使用自定义 Agent
claude "Use @sre-operator to run a full health check"
# Slash command / 斜杠命令 (in interactive session)
/health-check
Setup / 配置:
# Method 1: Auto-install from hub / 从技能中心安装
hermes skills search ops-toolkit
hermes skills install ops-toolkit
# Method 2: Manual copy / 手动复制
cp -r ~/.hermes/skills/devops/ops-toolkit ~/.hermes/skills/devops/ops-toolkit
Usage / 使用:
# Load skill in session / 在会话中加载技能
/skill ops-toolkit
# Or start with skill preloaded / 启动时预加载技能
hermes -s ops-toolkit
# Delegate parallel SRE tasks / 委派并行 SRE 任务
# (In Hermes session, use delegate_task tool to run health checks on multiple servers)
# Cron job for scheduled checks / 定时巡检
# (Use the cronjob tool to schedule regular health checks)
Gateway Mode / 网关模式: Run health checks from Telegram, Discord, Slack, WhatsApp, etc. 从 Telegram、Discord、Slack、WhatsApp 等平台触发巡检。
# Start gateway / 启动网关
hermes gateway run
# Then in your messaging app, send:
# "运行服务器巡检" or "run health check"
Setup / 配置:
# Copy skill to OpenClaw workspace / 复制到 OpenClaw 工作区
cp -r ~/.hermes/skills/devops/ops-toolkit ~/.openclaw/skills/ops-toolkit
# Verify / 验证安装
openclaw skills list
openclaw skills info ops-toolkit
Usage / 使用:
# Run agent locally / 本地运行 Agent
openclaw agent --local "运行健康巡检脚本 bash scripts/health-check.sh --full"
# Send check report via messaging / 通过消息平台发送巡检报告
openclaw message send --channel telegram --target @mychat --message "巡检报告：CPU 85% 警告"
# Interactive mode / 交互模式
openclaw agent --to +155****0123 --message "帮我检查服务器状态" --deliver
Gateway Mode / 网关模式:
# Start gateway / 启动网关
openclaw gateway --port 18789
# Then interact from your connected platform
# 然后从已连接的平台上交互
| Feature / 特性 | Claude Code | Hermes Agent | OpenClaw |
|---|---|---|---|
| Skill auto-load / 自动加载 | CLAUDE.md | ~/.hermes/skills/ | ~/.openclaw/skills/ |
| Custom commands / 自定义命令 | .claude/commands/ | /skill + cron | openclaw skills |
| Messaging platforms / 消息平台 | No | 15+ platforms | Multiple platforms |
| Parallel tasks / 并行任务 | tmux sessions | delegate_task | openclaw agents |
| Scheduled checks / 定时巡检 | External cron | Built-in cronjob | External cron |
| Chinese support / 中文支持 | Partial | Full (bilingual) | Full (中文版) |