active-runs

Identify and summarize active OpenClaw runs and session activity.

Updated Apr 8, 2026
One-click install
npx skills add https://github.com/gevrey/openclaw_backup --skill active-runs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: active-runs
Source: https://github.com/gevrey/openclaw_backup/tree/main/skills/active-runs
Command: npx skills add https://github.com/gevrey/openclaw_backup --skill active-runs

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

OpenClaw operators need a quick snapshot of ongoing activity. This skill provides a fast summary of currently active runs and queued sessions to help triage and respond quickly.

Core Features & Use Cases

  • Instant visibility into active sessions and queue status within a configurable time window.
  • Detect anomalies and bottlenecks in run queues for faster remediation.
  • Use Case: when monitoring multiple agents, quickly identify which runs are active, which are queued, and where delays occur.

Quick Start

Ask the skill to show active runs within an optional minutes window.

Frequently Asked Questions about active-runs

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

FAQPage Schema
How do I monitor active OpenClaw runs and queued sessions in real-time?

Monitoring active OpenClaw runs requires summarizing live session activity and queue status within a configurable time window to provide operators with instant visibility into ongoing workload and bottlenecks.

What is the best way to check current OpenClaw queue status and recent session activity?

Checking OpenClaw queue status involves using an active-runs script to identify active and queued sessions, applying a default 15-minute time window to capture recent activity and detect delays.

Can I adjust the time window for viewing live OpenClaw session activity?

Yes, you can adjust the time window for viewing live OpenClaw session activity, using a default of 15 minutes to filter recent runs, helping you quickly triage and respond to ongoing operations.

Do I need specific access to view active OpenClaw runs?

Viewing active OpenClaw runs requires the active-runs script and access to session state data to successfully identify live workload and summarize real-time operations.

What happens if the primary OpenClaw command fails to show active runs?

If the primary OpenClaw command fails to show active runs, the system gracefully falls back to alternative OpenClaw commands to ensure operators maintain visibility into active sessions and queue status.

Why does my OpenClaw monitoring show bottlenecks in the run queue?

Monitoring shows bottlenecks in the OpenClaw run queue when active sessions and queued tasks are summarized within the configured time window, highlighting delays for faster remediation.