Skip to content

UX: Compress and summarize verbose execution event stream #475

@frankbria

Description

@frankbria

Problem

The execution EventStream shows raw tool call events (file reads, file edits, command runs) in chronological order. After 50+ events, users see an overwhelming technical log with no sense of overall progress or completion.

Impact

Users cannot assess if execution is stuck or making progress without parsing technical log entries. Stall vs. normal operation is indistinguishable. High cognitive load during execution monitoring.

Recommendation

  1. Group related events: "3 files modified" instead of 3 separate file edit entries
  2. Collapse low-value events (file reads) by default with expand affordance
  3. Inject phase checkpoints: "Phase 1/3: Context loaded ✓" / "Phase 2/3: Implementation in progress..."
  4. Add overall progress indicator (e.g., iteration count / estimated remaining)

Acceptance Criteria

  • Low-value events (reads) collapsed by default, expandable
  • Related file edits grouped into single summary line
  • Phase progress checkpoints injected at natural milestones
  • Users can distinguish active work from stuck execution
  • Full raw log accessible via 'Show all events' expand

Affected Components

web-ui/src/app/execution/[taskId]/page.tsx

Metadata

Metadata

Assignees

No one assigned

    Labels

    phase-6.3Phase 6.3: UX/UI design improvements for user journey through Think→Build→Prove→Shippriority:mediumux

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions