long-task-monitor

Coordinate Worker and Monitor agents to automate long-running task monitoring.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/buer2233/my_openclaw --skill long-task-monitor
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: long-task-monitor
Source: https://github.com/buer2233/my_openclaw/tree/main/skills/long-task-monitor
Command: npx skills add https://github.com/buer2233/my_openclaw --skill long-task-monitor

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Long-running tasks in OpenClaw often lack visibility into progress and health; this Skill provides automated orchestration by launching a Worker to perform the task and a Monitor that periodically reports status back to the main session, enabling proactive control and recovery.

Core Features & Use Cases

  • Worker-Monitor orchestration: creates a dedicated Worker for the task and a Monitor that polls progress on a fixed cadence.
  • Progress reporting with Announce: Monitor reports status to the main session every 10 minutes or on completion.
  • Session management & cleanup: supports session keys, auto-retries for transient failures, and manual cleanup when tasks finish.
  • Use Case: Manage long model-training or data processing jobs with automatic progress insight and user alerts.

Quick Start

Start a new long-running task by creating a Worker, then spawn a Monitor and supply their session keys when available.

Frequently Asked Questions about long-task-monitor

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I monitor long-running tasks in OpenClaw?

You can monitor long-running tasks in OpenClaw by using a worker-monitor orchestration that launches a dedicated Worker to execute the task and a Monitor to periodically poll and report progress back to your main session.

How does automated progress reporting work for long-running AI agent sessions?

Automated progress reporting for long-running AI agent sessions works by having a Monitor agent poll the Worker's status on a fixed cadence and send updates via Announce to the main session every 10 minutes or upon task completion.

What do I need to set up before orchestrating long-task monitoring?

To set up long-task monitoring, you need a local Long Tasks registry under ~/.openclaw/workspace/long-tasks, a Worker session key, a Monitor session key, and the hook-logger plugin installed for status insights.

Can I get automatic alerts when a model training job finishes or fails?

Yes, the Monitor reports status to the main session on completion and includes automatic retry logic for transient failures, providing proactive alerts and recovery control for model training or data processing jobs.

How do I clean up session keys after a long-running task finishes?

After a long-running task finishes, the orchestration supports manual cleanup of the Worker and Monitor session keys to clear the completed job and free up the local long-tasks registry resources.