[FEATURE]: Recovery agentic workflow after system wakeup

[artyconst]

Feature hasn't been suggested before.

• I have verified this feature I'm about to request hasn't been suggested before.

Describe the enhancement you want to request

OpenCode Desktop app - When running some long task on Laptop in my case Mac OS on MBP, and me as a user walk away from laptop till tasks are running, the laptop is entering in to the sleep mode which interrupt the tasks execution, but UI still showing as task is running. Only way to check as execution was stop is through monitoring the requests to llm provider, and reset task manually by Press stop button and ask agent to continue.

It would be nice if App will be able to recovery its current workflow without manual actions.

[github-actions]

This issue might be a duplicate of existing issues. Please check:

• [BUG] SSE connection becomes stale after laptop sleep/wake — no detection or recovery #21716: SSE connection becomes stale after laptop sleep/wake — no detection or recovery (very similar scenario)
• [Bug] opencode session freezes after macOS lock screen while task remains “In Progress” #15431: opencode session freezes after macOS lock screen while task remains 'In Progress' (same macOS sleep scenario)
• Bug - TUI - Application Gets Stuck When Computer Sleep Occurs #16954: Application Gets Stuck When Computer Sleep Occurs (same root cause)
• [FEATURE]: Block suspension/hibernation while processing #13656: [FEATURE]: Block suspension/hibernation while processing (related feature request)
• Sessions permanently stuck after server restart or stream interruption — no startup recovery for orphaned messages/tool parts #19023: Sessions permanently stuck after server restart or stream interruption — no startup recovery (related recovery issue)
• [FEATURE]: Runtime watchdog for stuck tool/session recovery (complements #19023 startup recovery) #20099: [FEATURE]: Runtime watchdog for stuck tool/session recovery (related recovery feature request)

If your issue is distinct from all of the above, please clarify what's different. Otherwise, consider adding a "+1" reaction or comment on the most relevant existing issue.