Background agent results lost when user accidentally dismisses confirmation

Status Closed — not planned
Maintainer reply None cached
Activity 4 comments · opened Mar 28, 2026 · closed Apr 30, 2026

Problem

When multiple agents are launched (not in background mode), their results are delivered as tool outputs that can be accepted/rejected via a confirmation dialog. If the user accidentally hits escape or reject, the agent results are permanently lost - even though the agents already completed and consumed significant tokens/time.

Expected behavior

  • Completed agent results should be delivered regardless of UI dismissal
  • Background agents should not be killable by a single keypress
  • There should be a clear separation between "cancel a pending action" and "discard completed results"

Reproduction

  1. Launch 3 research agents in parallel (foreground mode)
  2. Wait several minutes for them to complete
  3. Accidentally hit escape/reject on the confirmation
  4. All results are lost, tokens wasted

Suggestion

Agent results that have already been computed should flow through unconditionally. The accept/reject dialog should only gate actions that haven't happened yet (like file writes), not discard already-completed research.

View original on GitHub ↗

This issue has 4 comments on GitHub. Read the full discussion on GitHub ↗