Omniscio

Stop, restart, pause, archive, or message many sessions at once

The Bulk session manager window: one list of every session in scope with a sidebar of filters, an action bar that offers only what fits the sessions you ticked, and Queue and Automation pages beside it. Covers where to open it, what each filter and count means, what is undoable, and the safer narrow rules Stop and Restart follow.

On this page

What it is

A Bulk session manager window for when you have lots of sessions and want to act on a hand-picked set, not all-or-nothing. A sidebar down the left picks one of three pages (the arrow keys move between them):

  • Sessions — one list you tick, with filters and an action bar.
  • Queue — what is restarting or about to start, and what the auto-restarter would restart next.
  • Automation — the settings that decide what comes back on its own.

The Sessions page

One list holds every session in scope: the ones that need you, the live ones, the interrupted and paused ones, and stopped ones that still have a conversation. There are no per-action tabs. You pick the rows first, and the action bar then shows what you can do with them.

What each row shows. One line per session: a tick box, the status dot, the title, any markers, and on the right the project, the engine's logo and when the session was last active — "13m ago" with Working, Waiting on you, Paused, Stopped or Failed underneath. That word is the same state the dot and the Status filter use, so an interrupted session says Stopped and never hides behind a stale green dot. Hover a row to open a preview with its full title, the prompt that opened it, its latest reply, where it runs and when it started — the list itself stays one line, and the long text lives in the preview. A row from the Queue page that the app built by hand has no timestamp and shows an empty time cell rather than claiming "just now".

Filters (the sidebar). Each group narrows the list, and the groups combine:

  • Status — All, Needs you, Live, Interrupted, Paused, Archived. These are the same groups as the main sessions sidebar, so a session sits under the same heading in both places. All never includes archived sessions — choose Archived to see them.
  • Where — Anywhere, This computer, Cloud. Cloud matches the cloud marker you see on a session row.
  • Owner — Anyone, Overseer crews, Not an overseer's. Overseer crews matches the crown marker in the sidebar (the overseer lead counts). This group is hidden while Omniscio does not know the crew roster yet (crews off, or still loading), so a saved choice can never empty the list.
  • Started by — Anyone, You, An agent or The system. You means you opened the session: you typed into it, took a Start session card, picked an Automation Helper preset, or sent it from Telegram, SMS or a bookmark. An agent means another session or an agent tool opened it. The system means a schedule, an automation, the auto-lander or the app itself opened it — and anything Omniscio does not recognise lands here rather than being guessed as yours.
  • Started — a From and a To date. Both ends are inclusive, and you can leave one blank for an open range. A session with no recorded start time drops out while a range is set, and a From later than the To tells you so instead of silently showing nothing.
  • Engine — All, plus every engine the list actually contains (Claude, Codex, Gemini, DeepSeek, GLM, Kimi and so on). A session with no engine recorded only appears under All.
  • Filtering guide — the ? button beside the Filter heading opens a short reference: the title-box syntax, one line per group, what the numbers do and do not include, and the reminder that filters reset each time the window opens.
  • Title filter — a search box above the list. Type part of a title; -word leaves out sessions containing the word, and "quoted phrases" match as one. Case and accents are ignored.

Filters start fresh every time you open the window. A choice you click (or tap on a phone) lights up at once; the list updates a split second later, and the action buttons always count the rows you can see.

Which hub. A hub picker sits in the window's header, beside the close button, on desktop and on a phone. The window opens on the hub you are on (from the Inbox, or with no hub open, it opens on All hubs). Tap the picker to search for and choose another hub, or All hubs to see everything; the list, the filter counts, the Queue page and the archived sessions all switch to that hub, and anything you had ticked is cleared. With All hubs chosen, each row shows which hub it belongs to. When a hub has nothing to show, Clear filters also widens back to All hubs. The picker is hidden on Automation, because those settings apply to every hub.

Counts. Every Status, Where and Owner option shows how many sessions sit behind it, and each number already respects your other choices (the Cloud count covers the cloud sessions inside the Status and Owner you picked). The numbers are worked out by the app itself, not by your screen, so the desktop and a phone always show the same figures. While they load, or if the read fails, an option shows no number rather than a guess. Started by, Started and Engine carry no number on purpose: a date range cannot be part of a fixed count grid, and numbering only some of the newer groups would put two meanings in one rail. They narrow the list exactly as the title box does. The list header says Showing X of Y; when nothing matches it offers Clear filters.

Sessions this device never loaded. To stay fast, your device holds only a recent slice of stopped sessions. When the window opens (and when you change project) it also fetches the stopped sessions your device never loaded — other projects, or older than the recent window — up to 1,000, newest first. They appear in the list, count in the filters, and can be restarted, paused, archived or messaged like any other row. They are held only while the window is open and released when you close it. If there are more than 1,000 the list says so ("Showing 1,000 of 1,240") and you narrow the filters to reach the rest.

Picking. Tick a checkbox on each row, use the Select menu (Select all shows how many you ticked of how many are visible, e.g. Select all (2/5)), or use the first / last dropdown with a number to tick the first or last N from the top or bottom of the list. The number is applied when you press Enter or click away; a number larger than the list ticks everything, 0 clears, and an empty box leaves your picks alone. The window opens with nothing selected. Picks apply only to what is visible: a row a filter has hidden is never acted on, even if you ticked it earlier. A row whose automatic restart is switched off shows a Won't auto-restart pill, and you can sort the list.

The action bar. The footer shows only the actions that fit the rows you ticked and can see, in a fixed order, each with its own count:

Action Key What it does Undo
Restart R Relaunches the picked interrupted, stuck, paused or stopped-with-a-conversation sessions, resumed with --resume, top to bottom in list order No
Pause P Parks live sessions where they are (including ones waiting on you); unpausing picks up the same conversation Ctrl+Z or the toast's Undo
Message M Opens a composer for one message sent to every picked session No
Archive A Files the picked sessions away, stopping a running one first Ctrl+Z or the toast's Undo
Stop none Ends the picked running sessions, each left as "ended" No

The letter keys work while the list or a row checkbox has focus, and are ignored while you type in a box. Stop deliberately has no key: one stray keypress must never end work. A button disappears when none of your picks can use it, so ticking one interrupted session and two running ones offers Restart 1, Pause 3, Message 3, Archive 3 and Stop 2. The count on each button is the number of picked, visible sessions that action can touch, and pressing it acts on exactly those.

Stopping or restarting more than one session asks first — one question naming the count, warning that a Stop cannot be taken back and that each Restart is a new paid run. It is the same question the right-click menu asks, and it appears whether you click the button or use the key. A single session goes straight through.

Message. The Message button opens a composer above the footer: type once, then press Send to N (or Ctrl+Enter; plain Enter adds a new line). Send stays greyed out until the message has text. Each recipient gets it as a real turn in its own conversation, clearly labelled as coming from you, sent to up to 10 sessions at once on the desktop app (one at a time from a phone or browser, where the connection is rate-limited), so one slow session never holds up the rest; one failure never stops the rest (the toast says, e.g., "Sent to 11 of 12 sessions; 1 couldn't be reached."). A recipient that is mid-turn is interrupted so your message goes in now, as the Send button in a session does; a session on an outside engine (Codex, Gemini, Cursor, Grok and friends) cannot be interrupted, so it waits for its turn to end. Message reaches running, waiting-on-you, stalled, paused, stopped and errored sessions, but never one parked on a usage limit, a brand-new blank session, one already shutting down, a session you closed, or a background automation session. Archived sessions can only be messaged: choose the Archived status to see them, and know that messaging one reopens it and starts its agent back up, which costs tokens. Because All never includes archived sessions, Select all can never sweep an archive in by accident. Leaving Archived turns that view off again.

The Queue page

Queue is what is coming back right now.

  • Restarting / waiting to restart — the sessions actually waiting in line, in the order they will come back, merging the ones resuming after an app restart ("Was running when the app closed") with the ones you queued yourself by restarting a batch ("You queued this restart"). The list shrinks live as each returns. Tick some and Cancel restart N pulls just those out of the line while the rest keep coming. A cancelled session is left stopped, restartable any time, with no nagging card; one that already launched in the meantime is reported as "already restarting, so there was nothing to cancel".
  • Stop all resuming — halts the whole resume wave at once. Shown whenever anything is still waiting to resume; the same action is one search away in the command palette and over the CLI as POST /recovery-queue/cancel.
  • Waiting to start — the new sessions that agents and automations have asked for and that are still waiting their turn, each with how long it has waited and which session asked ("Waiting 31m · asked for by …"), or "Starting now". These are the same requests the "Session-spawn queue is backing up" alert counts. They are read-only: cancelling one would leave the session that asked for it waiting for a session that never comes.
  • Up next for the auto-restarter — a read-only readout of the interrupted sessions Omniscio would bring back on its own to reach your target, each row saying why it qualifies ("Process stopped mid-work", "Automatic recovery gave up", "Interrupted when the app closed"), with how many sessions are running against your target and how many automatic restarts are left today. A long list with nothing happening is normal: when you already have more running than your target it holds back, and the readout says so. It works even with the auto-restarter switched off (then it is simply a list of what it would restart). A Change auto-restart settings link jumps to the Automation page. See session-refill-governor.md.

Queue refreshes itself every 10 seconds while the window is open, and an empty queue says which kind of empty it is (nothing waiting at all, the last few already starting, or nothing in this project while others are queued elsewhere).

The Automation page

  • Auto-restarter — the settings for bringing interrupted sessions back on their own (the Session Refill Governor). See session-refill-governor.md.
  • When the app restarts — including the "Auto-Resume Sessions on Restart" switch, the persistent off-switch for auto-resume (the same setting as Settings → Workflow → "Auto-Resume Sessions on Restart"). To halt a resume that is happening right now, use Stop all resuming on the Queue page.
  • Pull-request helper — developers only; nobody else sees it.

On a phone

The window is two steps. The first screen lists the three pages (Sessions, Queue, Automation) with a count on each; tap one and it opens on its own screen with a back chevron. The hub picker stays in the header on both screens, so you can narrow to one hub before or after picking a page. On Sessions, one Filters menu holds all six groups and the filtering guide (the button shows how many filters are active) beside the title filter and Select menu, and the footer is a single Actions (N) button that opens a menu of the actions that fit your picks, each with its count. Stop and Restart of several sessions still ask first. The counts are the same numbers the desktop shows. Nothing was removed, only moved, so the list keeps most of the screen.

Where to find it

The window opens from two places and they differ only in where they start. A Bulk session manager item lives in the toolbar's More menu and opens on the hub you are on (switch to All hubs from the header picker); right-click it to pin it to the toolbar. Stop all resuming and a restoring session's Manage queue link open the Queue page across every hub, because that stop is app-wide. The same item sits at the bottom of a project's own three-dot (⋮) menu, where it acts on that project alone (it is greyed out, with a tooltip, when the project has nothing to manage). For a handful of sessions you need not open the window at all — select rows in the sidebar and right-click to Stop or Restart them.

How it behaves

The safety rules

  • Stop and Restart never touch a live "Needs You" session — one waiting on your input (a question, an approval, a transient API-error or rate-limit pause) — so a conversation you are mid-way through is never ended or relaunched from under you. Stop reaches only running or starting sessions. Restart reaches sessions in error, stalled, that gave up recovering, that were interrupted when the app closed, that you paused, and stopped ("ended") sessions with a conversation to resume; blank never-used sessions and ones already closing are left alone. The buckets come from the true status, not the dot colour.
  • Pause and Archive are deliberately wider, because neither destroys the conversation: pause parks it and unpause resumes it, and archive is reversible from the Archived view.
  • A Stop sticks by default. Nothing automatic brings a stopped session back — not the auto-restarter, another agent, or the branch lander — until you restart or message it. The one exception is the Session Refill Governor's Also restart sessions I closed myself switch: with that on, a Stop is treated exactly like a plain close and may be restarted. A big batch answers at once and shuts down in the background.
  • Restarting a session whose last turn you stopped brings it back — without re-running what you stopped. Its whole conversation comes back and it opens on a stop-aware instruction: do not re-run the interrupted command, say where it stopped and what is left, then wait for you. You see where you got to instead of a silent no-op. Restarting it a second time reuses the same safe opener, so the stopped command is never re-run; once you type your own message, later restarts behave normally again. Automatic recovery never does this — only your own press.
  • Pause and Archive are undoable (Ctrl+Z or the toast's Undo): a paused batch unpauses exactly the ones you paused, and an archived session comes back in the state it was in (one waiting on you returns to Needs You). Stop, Restart and Message are not, because the only reversal is a paid re-spawn, or the message is already being worked on.
  • A cloud session whose machine is gone is restarted in the cloud, as sending it a message does, never on your own computer.

Restarting many at once

When you restart several sessions, Omniscio paces the relaunches (by default at most about 1.5 seconds apart — adjustable in Settings → Performance → "Spacing between sessions when many restart at once", or 0 to turn the gap off) so a big batch does not boot every agent in the same instant. That setting is a ceiling, not a fixed wait: the pace starts at the full gap while the app is still opening, then accelerates on its own, down to a quarter of it, once startup work is finished and your computer measures calm, and widens back out if the machine gets busy. That short gap is the only thing that holds a batch you asked for — it never waits for your computer to "calm down" or for a capacity limit — and it is counted only against your own batch, never behind background restarts. If a session in your batch comes back on its own before its turn, the batch leaves it running instead of restarting it twice and counts it as restarted. A single restart fires immediately.

What you see after

The moment you press an action, the work happens in the background and the window stays open: the ticks clear, so you can pick the next set and take another action straight away, or close the window and keep working while a big batch relaunches. A second Restart started while an earlier one is still going joins the same queue rather than replacing it. Stopped sessions turn grey ("ended") and stay in your list — send any message to start one again. Restarted sessions flip to "Starting" straight away and resume on their own. A brief toast tells you the outcome, and if some could not be acted on it says so honestly ("Stopped 3 of 4 sessions; 1 couldn't be stopped."); a Restart that half-failed adds why, e.g. "This session runs in the cloud and its cloud machine is gone — send it a message to start a new one." When the app itself stopped the restart, its own sentence is shown in full even when it is long — a batch refused because this computer's cloud connection was not attached says so, and tells you to restart Omniscio, instead of a bare "something went wrong".

The right-click shortcut

Select one or more sessions in the sidebar (Ctrl/Shift+click for several) and right-click → Stop or Restart to act at once on the eligible sessions in your selection. Both are narrow in the same way as the window's actions. One deliberate difference: the window's Restart includes the sessions you paused, because it is the one place whose point is putting a session back to work; the right-click Restart leaves paused sessions alone. Reach for the window when you want to pick from a list, filter, or act across all projects. See bulk-select-sidebar.md for the multi-select keys.

Restarting the one session you are looking at moves you to the next one. A single restart of the session in front of you — from the right-click menu, its own Restart button, or a recovering session's "Restart now" line — carries you to the next session to deal with, as replying, archiving or snoozing does. A deliberate multi-session restart leaves your place put. If a single restart fails, you snap back. See inbox-navigation-contract.md active-session-auto-eject.

Last verified 2026-10-27