Working through paused sessions
When you act on a session in a project's Paused Sessions section, Omniscio opens the next Paused session for you, so you can clear the pile without hunting for the next row. It never crosses into another section, and on the last row it steps back up. When that row is the only paused one, the action falls through to its ordinary rule: archive, snooze, restart and continue land on the on-screen neighbour, while a reply follows your "after I send" setting (a Needs-You row, or staying put).
On this page
What it is
Any of the ways you clear a paused session moves selection to the next paused session in the same project's Paused Sessions section, in the same top-to-bottom sidebar order:
- Archive it.
- Snooze it.
- Restart it.
- Continue it (the "Please continue" nudge).
- Reply to it.
The advance is section-keyed, not status-keyed: the gate asks whether the acted-on row's section is Paused, using the same predicate the sidebar splits its sections with, so the navigation pile and the rendered Paused section can never drift apart. That is the same mechanism the Interrupted and Needs You sections use — act on a member, land on the next member of that same section. Acting on the last row steps back to the previous one rather than wrapping to the top, and the walk never crosses the Interrupted ↔ Paused ↔ Live boundary.
What the past looked like, and what is still gone. A paused-only "work through the paused pile" rule was removed on 2026-06-19. The section-keyed pile came back on 2026-06-25 (user-confirmed) for every settled section, and on 2026-08-31 a reply to a Paused session was brought under it too — the user's report that "when I reply to a paused session I should be brought to the next paused session like any other status group". What stays removed is the OLD per-status helper pair and its oldest-Needs-You fallback: the paused pile itself never jumps you to a Needs You row. When the paused section has no other member, each action falls through to its ordinary rule instead — archive, snooze, restart and continue to the on-screen neighbour, a reply to the project's Needs-You walk (which lands on a Needs-You row when one is waiting and otherwise stays put).
Where to find it
There is nothing to switch on. The behavior belongs to the Paused Sessions section at the bottom of a project's sidebar: act on a session there and the next one opens by itself. The same auto-advance applies to the Interrupted and Needs You sections.
How it behaves
The order it picks the next session
- Next Paused session — the next member of that project's visible Paused Sessions section, in the same order you see in the sidebar. Start at the top, middle, or bottom; it never repeats or skips, and when you act on the last row it steps back up to the previous one (never wraps to the top).
- Section exhausted → each action's own fallback — when the row you acted on was the only paused row in its section, the pause pile has nothing to offer and the action falls through to its ordinary rule:
- Archive, snooze, restart and continue fall through to whatever sits next to the row in the visible list (the same "land on the row below" behaviour every non-attention row uses), with no jump to the oldest Needs You.
- A reply falls through to the project's Needs-You walk instead: it lands on a Needs-You row when one is waiting, and otherwise stays on the row you answered (the post-send path has no on-screen-neighbour fallback of its own).
When it does NOT apply
- The row isn't in the Paused section. A Live (running) row keeps its own on-screen-neighbour behaviour, an Interrupted row advances within Interrupted, and a genuine Needs You row advances within Needs You.
- You're not on that session. It only advances when the row you acted on is the one you're actually viewing. A background delivery landing on an off-screen row won't yank your view.
- You're in the global Inbox, or a special session area. It's scoped to a regular project's session list — the Inbox and the OpenClaw / Ask-Omniscio / Session-Search virtual areas are excluded, and the inbox advance stays status-blind.
- The paused rows aren't visible. If you've collapsed the Paused Sessions group, its rows — including the one you just acted on — are hidden from the sidebar and from navigation, so there is no neighbour position to fall to. The ordinary resolver takes over: a reply stays on the answered row, archive lands on the first visible row at or after its last-active time, and snooze / continue land at the top of the project list.
- The row belongs to an Overseer. An Overseer's session sits in the OVERSEERS section, never in a triage pile, so the walk never advances onto one.
Related
- Work through interrupted sessions — the same auto-advance for the Interrupted section.
- Pause or stop a session — how a session becomes paused, and what Unpause does per engine.
- Archive a session · Snooze a session — two of the actions that trigger the paused jump.
- Session stuck in Needs you — a session that landed in the attention queue instead.
Last verified 2026-10-18