[Feature] Snooze a session — hide it from the sidebar until a chosen time, then resurface it (optionally with a stored resume prompt)

[randypitcherii]

Problem or use case

I've gone as far as I can on a task right now — blocked on someone else, waiting on a build, or just parking it until tomorrow — and I want it out of my active sessions so the sidebar reflects what I'm actually working on.

Archiving is the wrong tool. Archiving says "this is done"; it's a terminal state I have to remember to go dig out of. What I want is "this is not done, just not now" — and crucially, I want it to come back on its own. If I have to remember to un-archive it, I've just moved the tracking burden into my head, which is the thing I was trying to offload.

So today the choice is: leave it cluttering the active list where it competes for attention with live work, or archive it and risk it silently falling off the map. Neither is right, and the sidebar's signal degrades either way as parked work accumulates.

Proposed solution

Snooze a session until a chosen time. While snoozed it leaves the active sidebar list; when the time arrives it comes back.

• Snooze from the session row's context menu and from the session header, alongside Archive. Sensible presets (later today / tomorrow morning / next week) plus a specific date-time.
• While snoozed, the session is hidden from the default sidebar list but is not archived — a "Snoozed" filter/section lists them with their wake time, and un-snoozing is one click.
• On wake, two modes:
  1. Just resurface (default) — it reappears in the sidebar, ideally flagged as newly woken so it's distinguishable from sessions that were there all along. This is the low-risk default: nothing runs without me.
  2. Resume with a stored prompt — I write the prompt at snooze time ("check whether the upstream fix landed and rebase"), and on wake the session sends it and starts working, so I come back to a result rather than a reminder. This is the one that makes snoozing an actual delegation rather than a deferral.
• Waking should surface through the same path other background completions do (Inbox / notifications), so a woken session isn't just silently back in a list I might not be looking at.

Snoozing a session that's currently running should either be blocked or clearly mean "snooze once it goes idle" — a session mid-turn disappearing from the sidebar would be alarming.

Alternatives considered

• Archive + remember to come back — today's workaround, and the reason I'm filing this. Loses the wake, and conflates "done" with "parked".
• Projects / filters — a "parked" project would hide it from a filtered view, but it's still manual on both ends and there's no wake at all. It organizes the clutter rather than removing it.
• An external reminder (calendar, todo app) pointing back at the session URL — works, but the state lives outside the tool and the resume prompt has nowhere to live. Also doesn't clean up the sidebar.
• Scheduled tasks / automations — these create new runs on a cron; snoozing is about deferring an existing session's visibility, carrying its full history and context forward. Related but not the same primitive, though they may share the scheduling substrate.

Harness

Not applicable — this is session lifecycle in the web UI, independent of which harness is bound.

Platform or device

Not platform-specific.

Harness mode

Not applicable.

Expected reach

A substantial user segment — anyone running more than a handful of concurrent sessions hits sidebar clutter from parked work.

Authentication type

Not applicable.