openclaw - 💡(How to fix) Fix feat(tasks): add compressed operational summaries [1 comments, 2 participants]

Summary

Add a compact, actionable summary layer for task status across the task system, CLI, and auto-reply surfaces.

The goal is to make long-running or blocked work understandable in one glance, without requiring users or downstream consumers to reconstruct state from logs or scattered fields.

Problem

Task state is visible today, but the operator experience is still too raw in many places:

• state is present, but not always the last meaningful checkpoint
• blockers are visible, but not always framed as the current actionable issue
• different surfaces may summarize the same task differently

This makes it harder to answer simple questions:

• what is happening right now?
• what was the last successful step?
• what is blocking progress?
• what should happen next?

Proposal

Add a shared summary builder for tasks with a compact structure like:

• current state
• last successful checkpoint
• current blocker
• recommended next action

Example output:

• blocked · awaiting approval · last good step: patch applied · next: approve exec to push branch
• active · waiting external · last good step: workflow triggered · next: wait for CI result
• finished · completed · last good step: PR opened · next: no action

Scope

• Add a shared summary-generation utility for task status
• Reuse the same summary contract across:
  • task CLI output
  • task summary views
  • auto-reply status rendering
• Keep summaries concise and deterministic

Acceptance criteria

• A task can be rendered as a short operational summary in a consistent format
• The summary includes:
  • current state
  • last good checkpoint when available
  • blocker when present
  • next recommended action when known
• CLI and auto-reply stop hand-rolling different summary phrasing for the same task state

Notes

This should build on the newer intermediate task states work rather than reintroducing queued/running-only summaries.