Files

sol 43cfebee96 feat: Phase 0+1 — repo sync, pino, lint fixes, core components

Phase 0:
- Synced latest live-status.js from workspace (9928 bytes)
- Fixed 43 lint issues: empty catch blocks, console statements
- Added pino dependency
- Created src/tool-labels.json with all known tool mappings
- make check passes

Phase 1 (Core Components):
- src/config.js: env-var config with validation, throws on missing required vars
- src/logger.js: pino singleton with child loggers, level validation
- src/circuit-breaker.js: CLOSED/OPEN/HALF_OPEN state machine with callbacks
- src/tool-labels.js: exact/prefix/regex tool->label resolver with external override
- src/status-box.js: Mattermost post manager (keepAlive, throttle, retry, circuit breaker)
- src/status-formatter.js: pure SessionState->text formatter (nested, compact)
- src/health.js: HTTP health endpoint + metrics
- src/status-watcher.js: JSONL file watcher (inotify, compaction detection, idle detection)

Tests:
- test/unit/config.test.js: 7 tests
- test/unit/circuit-breaker.test.js: 12 tests
- test/unit/logger.test.js: 5 tests
- test/unit/status-formatter.test.js: 20 tests
- test/unit/tool-labels.test.js: 15 tests

All 59 unit tests pass. make check clean.

2026-03-07 17:26:53 +00:00

2.2 KiB

Raw Blame History

Live Status Skill

Real-time progress updates in Mattermost via in-place post editing. Creates a single "status box" post and updates it repeatedly — no chat spam.

Usage

Create a status box

live-status --channel <CHANNEL_ID> create "🚀 **Task Started:** Initializing..."

Returns the POST_ID (26-char string). Capture it.

Create in a thread

live-status --channel <CHANNEL_ID> --reply-to <ROOT_POST_ID> create "🚀 Starting..."

Update the status box

live-status update <POST_ID> "🚀 **Task Running**
\`\`\`
[10:00] Step 1... OK
[10:01] Step 2... Working
\`\`\`"

Mark complete

live-status update <POST_ID> "✅ **Task Complete**
\`\`\`
[10:00] Step 1... OK
[10:01] Step 2... OK
[10:05] Done.
\`\`\`"

Delete a status box

live-status delete <POST_ID>

Multi-Agent Support

When multiple agents share a channel, each creates its own status box:

# Agent A
BOX_A=$(live-status --channel $CH --agent god-agent create "🤖 God Agent working...")
# Agent B
BOX_B=$(live-status --channel $CH --agent nutrition-agent create "🥗 Nutrition Agent working...")

Each agent updates only its own box by ID. No conflicts.

Options

Flag	Purpose
`--channel ID`	Target channel (or set `MM_CHANNEL_ID`)
`--reply-to ID`	Post as thread reply (sets `root_id`)
`--agent NAME`	Use bot token mapped to this agent in openclaw.json
`--token TOKEN`	Explicit bot token (overrides everything)
`--host HOST`	Mattermost hostname

Auto-Detection

The tool reads openclaw.json automatically for:

Host — from mattermost.baseUrl
Token — from mattermost.accounts (mapped via --agent or defaults)
No env vars or manual config needed in most cases.

Protocol

Always capture the POST_ID from create.
Always append to previous log (maintain full history in the message).
Use code blocks for technical logs.
Each new task gets a new status box — never reuse old IDs across tasks.

2.2 KiB Raw Blame History