Task Resume

Use this skill to ensure interrupted tasks are recovered automatically.

Defaults (MANDATORY)

• Make interruption enqueue the default behavior.
• On any non-explicit context switch, auto-enqueue the active unfinished task.
• Enqueue at message-time (immediately when interruption is detected), not only on periodic checks.
• Use one shared queue file for all sessions/clones so the view is unified.

Rules

• Treat user-explicit commands (cancel, pause, change priority, do it tomorrow) as overrides.
• Treat all other topic switches as potential interruptions.
• Before switching topics, persist interruption context to queue.
• After completing the active task, immediately resume the oldest queued interrupted task.
• If queue is empty, do nothing.

Shared Queue Storage (cross-session)

• Canonical queue file: memory/task-resume-queue.json
• This file is workspace-global and shared across main + clone + group sessions.
• Always pass source with session/channel identity.
• Use helper script: scripts/task_resume_queue.py

Interruption Detection

Consider a task interrupted when all are true:

• There is an active task with unfinished acceptance criteria.
• A new user request is unrelated to finishing that active task.
• User did not explicitly cancel/pause/defer the active task.

Message-Time Enforcement (required)

Before handling every new user message:

• Check whether an active task exists and is unfinished.
• If the incoming message is an unrelated request and no explicit override is present, enqueue immediately.
• Only then switch to the new request.

Log-based Recovery (ENOENT-safe)

When recovery needs session .jsonl context, use:

python3 skills/task-resume/scripts/task_resume_queue.py recover \
  --log "~/.openclaw/agents/main/sessions/<session>.jsonl" \
  --title "<active task title>" \
  --acceptance "<acceptance criteria>" \
  --source "<channel>" \
  --session "<session_key_or_chat_id>"

If the log file is missing (ENOENT), treat it as expected and continue (skipped_missing_log), do not raise alert-level failure.

On Interruption (auto-enqueue)

Run immediately at interruption detection:

python3 skills/task-resume/scripts/task_resume_queue.py add \
  --title "<active task title>" \
  --context "<what was done + exact next step>" \
  --acceptance "<acceptance criteria>" \
  --source "<channel>" \
  --session "<session_key_or_chat_id>"

Then acknowledge briefly: queued + will auto-resume.

On Active Task Completion (resume)

Run:

python3 skills/task-resume/scripts/task_resume_queue.py pop

• If one item is returned, resume it immediately and announce: Resuming previously interrupted task: