Working through paused sessions (auto-advance removed 2026-06-19)

What it is

⚠️ REMOVED 2026-06-19. The per-status paused triage was DELETED from every production path (archive, snooze and post-send). The helpers it used — resolveNextPausedInProject and resolvePausedTriageTarget in session-navigation.ts — are dead code, and a guard test bans calling them. Everything below is retained for historical context only.

Paused sessions still exist — parking a session turns it paused and drops it into the "Paused Sessions" group at the bottom of that project's sidebar. What is gone is the special navigation rule: clearing that pile is now driven by the same advance behavior as every other kind of session.

What it used to do (removed). When you acted on a paused session — archived it, replied to it, or snoozed it — Omniscio used to open the next paused session in that project, in sidebar order; when the pile was empty it fell back to the oldest "Needs You" session, and when there was nothing to go to it stayed put. For a reply it also overrode your general "after I send, go to…" setting, but only for paused sessions. None of that happens any more.

Where to find it

This behavior no longer exists anywhere in the app. Paused sessions are still in the "Paused Sessions" group at the bottom of a project's sidebar; how your view advances after you act on one is now decided by the shared advance rule that applies to every status.

How it behaves

What happens now. Acting on a paused session advances exactly like acting on any other session: through the one shared action-advance resolver, with no per-status pile preference and no override of your post-send setting. The per-status "work through the paused pile" preference over a more-recent sibling is gone, and so is the post-send override for paused sessions.

When it used to NOT apply (historical). The removed rule was scoped: it fired only for paused sessions, only when you were viewing the session you acted on, only in a regular project's session list (not the Inbox or the OpenClaw / Ask-Omniscio / Search areas), and only when the "Paused Sessions" group was expanded. Terminating a paused session was never a trigger — that turns a session gray, which has its own interrupted-session auto-advance.

For agents

The removed rule lived in session-navigation.ts as the pair resolveNextPausedInProject(...) (walk the project's visible paused rows) and resolvePausedTriageTarget(...) (that next paused session, else the oldest attention session, else null), feeding computePostSendPatch / executePostSendNavigation and the shared resolvePausedAdvanceTarget guard in session-store.ts.

All of it is retired: those helpers are dead code, and session-advance-no-per-status-triage.test.ts bans any per-status paused advance from returning. The historical design is recorded in .claude/memory/contracts/paused-session-triage-nav-contract.md, marked SUPERSEDED.

Related

• Work through interrupted sessions — the live auto-advance for dead/finished gray sessions (this paused sibling was removed; that one remains).
• Pause or stop a session — how a session becomes paused, and how replying un-pauses it.
• Archive a session · Snooze a session — actions that used to trigger the paused jump.
• Session stuck in Needs you — one of the places the old rule used to land you.