Script Location

CODEBLOCK0

Two Running Modes

Mode 1: Cron Scheduled Sync (Default)

OpenClaw's built-in cron executes the script periodically:

CODEBLOCK1

Trigger phrases: say "sync status", "restart sync" or "同步状态", "重启同步状态" — OpenClaw will trigger execution on schedule.

Mode 2: Daemon Mode

Use --fork to start a real background daemon:

Command	Description
INLINECODE1	Start daemon
INLINECODE2

Start with custom interval (minutes) |
| python3 scripts/status_uploader.py stop | Stop service |
| python3 scripts/status_uploader.py status | Check service status |
| python3 scripts/status_uploader.py set-interval <minutes> | Set sync interval |
| python3 scripts/status_uploader.py test | Single test upload |

Examples:
CODEBLOCK2

Trigger Conditions

Triggers when any of the following conditions are met:

1. 1. First-time initialization: say "enable status monitor", "setup status-monitor" or "启用状态监控", "开启监控同步", "配置 status-monitor"
2. Manual trigger: say "sync status", "sync status-monitor", "upload status" or "同步状态", "同步 status-monitor", "上传状态" → single execution
3. Scheduled sync: OpenClaw cron triggers → single execution
4. Check status: say "check status monitor", "monitor status", "check upload service" or "查看状态监控", "状态监控状态", "检查上传服务"
5. Stop service: say "stop status monitor", "stop upload service" or "停止状态监控", "停止上传服务"
6. Change interval: say "sync every 10 minutes", "change to 15 minutes" or "每10分钟同步一次", "改成15分钟"
7. Daemon mode: say "start status monitor", "start daemon", "run in background" or "启动状态监控", "启动守护进程", "后台运行" → execute INLINECODE7

Additional triggers: say "start status-monitor service", "restart status-monitor service" or "启动status-monitor服务", "重启status-monitor服务".

Initialization Flow (Must Execute on First Use)

Step 1: Check Token Configuration

When the skill runs, first check for the token in these locations:

1. 1. Environment variable INLINECODE8
2. File INLINECODE9

Step 2: Handling Missing Token

If no token is found, guide the user to register/login:

1. 1. Prompt the user:

CODEBLOCK3

1. 2. Wait for user to reply with token

1. 3. Save the token:

- Create directory ~/.openclaw/credentials/ - Save to ~/.openclaw/credentials/openclaw-status-monitor.json: CODEBLOCK4

1. 4. Validate the token

Step 3: After Successful Token Validation

CODEBLOCK5

Core Functions: Managing the Upload Script

1. Check if Script Exists

CODEBLOCK6

2. Start Service (Recommended)

CODEBLOCK7

3. Set Sync Interval

CODEBLOCK8

4. Stop Service

CODEBLOCK9

5. Check Service Status

CODEBLOCK10

6. View Error Logs

CODEBLOCK11

CODEBLOCK12

Log rotation: log files auto-rotate when exceeding 10MB, format: INLINECODE12

7. Manually Trigger One Upload

CODEBLOCK13

Upload Logic (Simplified)

The script only reads all agent IDs from openclaw.json and uploads them — it does not perform any offline detection.

Offline detection is handled by the monitoring platform (openclaw-agent-monitor):

• - The platform automatically updates lastActiveTimestamp based on upload time
• If no upload is received for 5+ minutes, the platform automatically marks the agent as offline

Storage Configuration

Token Storage Location

INLINECODE15:

CODEBLOCK14

Log Locations

• - Service log: INLINECODE16
• Error log: INLINECODE17
• PID file: INLINECODE18
• Token config: INLINECODE19

Error Handling

1. Missing Token

During initialization:
CODEBLOCK15

2. Script Not Found

CODEBLOCK16

3. Service Start Failed

Check the error log:
CODEBLOCK17

Common errors:

• - Token not configured
• Network connection failed
• Port already in use

4. Invalid Token

CODEBLOCK18

Example Conversations

First-time Enable

User: 启用状态监控 / enable status monitor
Agent:
Checking monitoring configuration...

❌ No Agent Token detected

Please complete these steps first:

1. 1. Visit https://openclaw-agent-monitor.vercel.app
2. Click Sign In (supports Google/GitHub, etc.)
3. After logging in, generate an Agent Token on the Settings page
4. Send me the token

---

User: 我的 Token 是 e2d3262f-b626-4850-af11-5f2cb1c0dcad / My token is e2d3262f-b626-4850-af11-5f2cb1c0dcad Agent: Validating token...

✅ Token validated successfully!

Starting upload service...

• - Running initial sync test...
• ✅ Service started successfully!

---

✅ Status monitor enabled!

• - Monitor platform: https://openclaw-agent-monitor.vercel.app
• Upload interval: 5 minutes
• Service status: running

Management commands:

• - Say "sync status" / "同步状态" to manually trigger an upload
• Say "check status monitor" / "查看状态监控" to check service status
• Say "stop status monitor" / "停止状态监控" to stop the service

Check Service Status

User: 查看状态监控 / check status monitor
Agent:
Checking upload service status...

✅ Service is running
PID: 12345
Sync interval: 5 minutes
Log file: ~/.openclaw/logs/status_uploader.log

Recent logs:
CODEBLOCK19

Error log: none

Stop Service

User: 停止状态监控 / stop status monitor
Agent:
Stopping upload service...

✅ Service stopped

To restart, say "start status monitor" / "启动状态监控".

Manual Sync

User: 同步状态 / sync status
Agent:
Executing manual upload...

Online agents: ['main', 'coding']
Upload result: ✅ Success

Restart Service

User: 重启状态监控 / restart status monitor
Agent:
Restarting upload service...

✅ Service restarted, PID: 67890

Check Errors

User: 查看状态监控错误日志 / check status monitor error log
Agent:
Checking error logs...

Recent errors:
CODEBLOCK20

Suggestion: Check if the token is correct, or check your network connection.