// Persistent task queue for tracking issues, user tasks, improvements, and followups. Survives context resets.
| name | task-queue |
| description | Persistent task queue for tracking issues, user tasks, improvements, and followups. Survives context resets. |
| user-invocable | true |
./run.ts add --title "Fix WhatsApp bridge" --type issue --source "morning-briefing" [--description "..."] [--priority 2] [--due-by "2026-03-05"] [--tags infra,whatsapp]
./run.ts list [--status pending] [--type issue] [--limit 10]
./run.ts next
./run.ts update <id> --status in_progress
./run.ts resolve <id> --resolution "Fixed by reconfiguring channel"
./run.ts wontfix <id> --resolution "No longer relevant"
./run.ts stats
./run.ts --help
--title <string> — Short imperative description (required)--type <issue|task|improvement|followup> — Task type (required)--source <string> — Who/what created it: "user", "morning-briefing", etc. (required)--description <string> — Detailed context, error output--priority <1|2|3|4> — 1=critical, 2=high, 3=normal, 4=low. Auto-assigned by type if omitted.--due-by <ISO 8601> — Optional deadline--tags <comma-separated> — Optional tags: infra, api, skill, cron--status <pending|in_progress|blocked> — Filter by status--type <issue|task|improvement|followup> — Filter by type--limit <number> — Max results (default: all)No options. Returns highest-priority pending task with fewer than 3 attempts.
<id> — Task UUID--status <pending|in_progress|blocked> — New status--priority <1|2|3|4> — New priority--description <string> — Append/replace description<id> — Task UUID--resolution <string> — What was done (required)No options. Returns queue health metrics.
JSON to stdout. Examples:
{"action": "added", "task": {"id": "uuid", "title": "...", ...}}
{"action": "duplicate_skipped", "task": {"id": "existing-uuid", ...}}
{"action": "list", "count": 5, "tasks": [...]}
{"action": "next", "task": {...}}
{"action": "next", "task": null, "reason": "queue empty"}
{"action": "stats", "active": {"total": 12, "pending": 8}, ...}
~/.local/state/openclaw-cron/task-queue/tasks.json
| Type | Default Priority | When |
|---|---|---|
| task | 1 (critical) | User-assigned work |
| issue | 2 (high) | Broken infrastructure |
| followup | 3 (normal) | Time-sensitive from cron |
| improvement | 4 (low) | Nice-to-have |
Manage ZSA keyboard layouts via the oryx-bench CLI. Use when discussing keyboard layouts, key bindings, layer changes, achordion, tap-hold, custom keycodes, key overrides, combos, ZSA, Oryx, Keymapp, QMK, or the ZSA Voyager. v0.1 supports the Voyager geometry only — Moonlander/Ergodox are tracked for a future release. Supports both Oryx-mode (visual editor + local code) and local-only mode (no cloud dependency).
Plan, create, edit, remove, list, and test scheduled cron jobs. Each cron job runs as an AI agent session — use the plan→build→create workflow to keep sessions efficient.
Scaffold new OpenClaw skills with correct directory structure, SKILL.md, and run.ts template.
Track asset prices (BTC, etc.) and alert on percentage drops within a time window. Uses CoinGecko API.
Fetch and filter job board listings. Returns structured JSON.
Fetch and parse RSS/Atom feeds. Returns structured JSON.