Omniscio

Keep computer awake while sessions are running (cross-platform)

A setting that asks the operating system not to sleep for exactly as long as at least one session or plugin job is actively running, then lets it sleep normally the moment the last one finishes. It exists because a sleeping computer suspends running work mid-turn, silently stalling a job that was meant to finish unattended.

On this page

What it is

What problem this solves

Omniscio runs Claude CLI sessions that can work for many minutes — or, with cron jobs, recipe runs, and overnight batches, for hours — without anyone touching the keyboard. If the computer follows its normal power settings and goes to sleep while a session is mid-turn, the OS suspends the CLI child process and freezes the in-flight request: the session stalls, and the user comes back to a job that quietly stopped making progress instead of one that finished.

The usual workaround is to dig into the operating system's power settings and disable sleep globally — which then keeps the machine awake all the time, even when nothing is running. That wastes power and is easy to forget to undo.

What Omniscio does

When the user turns on Settings → Performance → "Keep computer awake while sessions are running", Omniscio asks the operating system not to go to sleep for exactly as long as at least one session or plugin job is actively running, and lets it sleep normally again the moment the last one finishes.

Concretely, Omniscio holds an Electron powerSaveBlocker('prevent-app-suspension') open while at least one session is in the running state or at least one plugin job holds a live run, and releases it as soon as that count drops to zero. It is fully automatic — there is no separate "start"/"stop" button; the toggle is the only control.

The toggle is on by default — Omniscio exists to run long, often unattended jobs, and a machine that sleeps mid-turn freezes them, so protecting that in-flight work is the behavior that matches what the app is for. It stays cheap: the blocker is only ever held while work is actually running and is released the moment the count hits zero, so an idle machine sleeps normally. A user who prefers their computer's normal power behavior can turn it off in one click.

Where to find it

Where to find the toggle

Settings → Performance section → "Keep computer awake while sessions are running" (on by default). It applies live — turning it off while sessions are already running releases immediately, and turning it back on takes hold immediately, with no restart required.

How it behaves

System sleep vs display sleep (the important distinction)

This feature blocks system sleep only — it does not keep your screen on. The display can still dim and sleep on its normal schedule to save power. That is deliberate: the work Omniscio is protecting is headless (a background CLI process), so there is no reason to burn power lighting up a monitor nobody is looking at. The machine stays awake and working; the screen behaves normally.

What counts as "running"

The blocker is held whenever one or more sessions are in the green running status — the same definition the rest of Omniscio uses for "a session is actively working." Sessions that are idle, waiting on you (needs you), ended, paused, or snoozed do not hold the machine awake. Snooze does not change this: a snoozed session that is still genuinely running keeps the machine awake, because real work is in flight.

Recipe and pipeline "lane" sub-sessions are covered too, transitively: every recipe run also has a top-level orchestrator session that stays in the running state for the entire run, and that orchestrator is counted — so while any lane is executing, the running count is at least one and the machine stays awake.

Plugin jobs

A plugin that declares a run, the same declaration that keeps its own screen alive, also holds the machine awake, because a plugin reading a long video or rendering in the background is exactly the unattended work this setting protects. A plugin with no run holds nothing.

Two limits are worth knowing. A run belongs to the plugin's screen, so closing that plugin's panel ends its run and releases the hold, and work that must outlive its panel needs its own signal from the plugin. A run is also bounded per working period: it is declared stale after three minutes without a heartbeat, confirmed stale a minute later, and force-ended at twelve hours, so a plugin that keeps declaring work can hold the machine across several periods. The toggle itself always wins: switched off, nothing holds the machine awake.

Cross-platform behavior

Unlike several neighboring Performance toggles (CPU cap, adaptive memory paging) which are Windows-only, this feature is not platform-gated:

  • Windows — reliable (backed by the Win32 SetThreadExecutionState API).
  • macOS — reliable (backed by IOKit power assertions).
  • Linux — best-effort. Electron implements sleep inhibition on Linux via the desktop environment's D-Bus idle-inhibition service, and not every desktop environment or headless session exposes one. On those setups the toggle is a no-op rather than an error. The user-facing helper text says so plainly ("on Linux it depends on your desktop environment") so a Linux user is not promised a guarantee the OS can't keep.

Why these defaults

  • On by default. Omniscio's whole purpose is running long, often unattended jobs; a mid-turn sleep freezes them, so keeping the machine awake while work is in flight is the behavior that matches what the app is for. Because the blocker is held only while a session or plugin job is running and released the instant the count hits zero, an idle machine still sleeps normally — the cost when nothing is running is zero. Users who prefer their normal power behavior can turn it off. (Laptop note: while a session runs on battery this also holds off sleep, so a user who runs unattended jobs on battery and wants them to sleep should turn it off.)
  • System sleep only (not display). Keeping the screen on would waste power for headless work and surprise users who expect their monitor to dim normally.
  • Released at zero running work (not on a timer). The machine returns to normal power behavior the instant the last session or plugin job finishes, so it is never held awake "just in case."

The other reliability guards Omniscio runs on your behalf — keeping panels warm, hiding panels you are not using, and pacing agent-initiated work so the machine stays responsive — are on the Low power mode page and under the app's Performance settings. Unattended work that would be worst hit by a sleeping computer is described on scheduled jobs.

Last verified 2026-11-19