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
- Group related events: "3 files modified" instead of 3 separate file edit entries
- Collapse low-value events (file reads) by default with expand affordance
- Inject phase checkpoints: "Phase 1/3: Context loaded ✓" / "Phase 2/3: Implementation in progress..."
- Add overall progress indicator (e.g., iteration count / estimated remaining)
Acceptance Criteria
Affected Components
web-ui/src/app/execution/[taskId]/page.tsx
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
Acceptance Criteria
Affected Components
web-ui/src/app/execution/[taskId]/page.tsx