Omniscio

Memory reclaim (free RAM automatically when the machine runs low)

When your computer's free memory runs low and stays low, Omniscio frees some up so the machine does not start swapping to disk and feeling slow. Two levels of aggressiveness — a safe one on by default and a powerful one you opt into — triggered by a free-memory percentage you set.

On this page

What it is

What it does

When your computer's free memory runs low and stays low, Omniscio automatically frees some up so the machine doesn't start swapping to disk and feeling slow. It works in two levels of aggressiveness — a safe one that's on by default, and a powerful whole-computer one that's off by default and opt-in.

  • Tier 1 — tidy Omniscio's own idle sessions (on by default, safe). Every running Claude session holds a chunk of memory even while it sits idle waiting on you. When free RAM drops below your threshold and stays there, Omniscio "trims" the memory of its own idle sessions — it asks Windows to move their unused pages out of RAM (the pages come back automatically the instant that session is used again). It only ever touches sessions that are not mid-reply and not waiting for your answer to a question, so it can never interrupt work. This is a Windows effect; on macOS and Linux the trim does nothing (the app just skips it).

    It does the same for the process that runs Omniscio's own scheduled jobs — but only while that process has been completely idle for two minutes and is holding enough memory to be worth it. Nothing is ever shut down: the pages simply come back the next time it runs a job. The helper that serves every agent tool call is deliberately never trimmed. Trimming raises the free memory available at that moment; it does not reduce how much Omniscio has committed overall.

  • Tier 2 — reclaim across your whole computer (opt-in, advanced, Windows only). The stronger option clears Windows' standby/cached memory across the whole machine — a system-wide cleanup, the same thing tools like RAMMap's "Empty Standby List" do. It deliberately does not empty every program's working set: that would push each running program's pages out to disk and hard-fault them all back in, making the machine feel worse, not better. Because that touches the whole system it needs Windows administrator rights, so Omniscio installs a tiny helper once, with your approval (a single Windows admin prompt), and then runs it on demand without prompting again. It ships off and hidden until it's fully hardened.

Both levels share one trigger: your computer's free memory staying below a set percentage. Omniscio does not react to a single brief dip — memory has to stay low for a few readings in a row, and there's a cool-down between reclaims, so it never thrashes (repeatedly trimming would itself make the machine feel slower, the opposite of the goal).

Where to find it

Settings → Performance, where the on/off switch and the free-memory trigger point live. Tier 2 sits behind the app's unreleased-feature gate.

How it behaves

How to turn it on or off

Tier 1 lives in Settings → Performance:

  • "Reclaim RAM automatically when memory runs low" — the on/off switch (on by default).
  • "Reclaim when free memory drops below ___ % free" — the trigger point. When free RAM stays below this percentage of your total memory, the automatic tidy-up kicks in. Higher = reclaims sooner; lower = only under real pressure. Default 15%.

No restart is needed — the setting applies live.

Tier 2 is an in-development feature, hidden by default. It appears only when you enable it from Settings → Lab (or launch with AMC_SHOW_MEMORY_RECLAIM_ADVANCED=1). Turning it on triggers a one-time Windows administrator prompt to install the elevated helper. Turning it back off uninstalls that helper (one more admin prompt) so nothing elevated is left behind; while it's off, no system-wide reclaim runs. Day-to-day use never re-prompts — only the install and the uninstall do.

When it applies

  • Your computer's free memory has stayed below the threshold for a few consecutive checks (Omniscio checks about once a minute), and the cool-down since the last reclaim has passed.
  • Tier 1 trims two kinds of session, and neither is ever one that is waiting on you: one whose turn has finished and has sat idle, and one that is parked waiting for the model to answer. A parked session is detected by measurement, not by its status — its whole process tree has used almost no processor time and it has written nothing for 20 seconds — so a session that is genuinely working, even a long silent build, is never touched. A session parked on the model is the shape a busy computer spends most of its memory on: on a measured 16 GB machine, 18 such processes held 4.3 GB between them while using a fifth of one core.
  • Tier 2 additionally requires Windows and that you've opted in (the elevated helper is installed).

When it does NOT apply

  • On macOS or Linux, the memory-trim is a Windows-only system call, so Tier 1 runs but has no effect and Tier 2 is unavailable. (Omniscio's primary platform is Windows.)
  • On a brief memory spike — a single reading below the threshold won't trigger anything; pressure has to be sustained.
  • Right after a reclaim — the cool-down prevents back-to-back reclaims of the same tier.
  • On sessions that are working or waiting on you — Tier 1 skips them by design. A session is "working" when its process is using processor time or it is producing output, never merely because its status says it is running.
  • On a session trimmed in the last ten minutes — a trimmed working set refills to about half its old size within 90 seconds, so trimming more often than that would pay a re-fault for nothing.
  • On more than six parked sessions at once — one reclaim trims at most six, longest silent first, so the machine never has to page a whole fleet back in at the same moment.

Why a percentage, not "number of sessions"

Most slowness while running Omniscio is RAM exhaustion → disk swap-thrash, not "too many sessions." Reacting to actual free memory targets the real cause directly, and a percentage generalizes across machine sizes — "15% free" means the same kind of danger on a 16 GB laptop and a 64 GB workstation. (On a 64 GB box, Tier 2's default 25% ≈ 16 GB free.)

How it relates to the other memory features

Omniscio has a few overlapping ways to keep memory healthy; this one is the pressure-triggered reclaimer:

  • Memory reclaim (this page) — fires when free memory runs low. Tier 1 trims Omniscio's idle sessions; Tier 2 (opt-in) reclaims the whole computer.
  • Release idle sessions — a time-based reaper: fully releases (closes) the background process of a session that's sat idle for many minutes, re-opening it transparently on your next message. Harder reclaim, different trigger. See slow-computer.md.
  • Working-set trim scheduler — the older idle-time-based trim of Omniscio's own sessions; memory reclaim reuses the same safe trim primitive but drives it off memory pressure instead of idle time.

New work waits while the computer is out of memory (Windows)

When the computer is truly out of memory, Omniscio does not start new background work on top of it. Two kinds of work wait:

  • New background sessions (restarts after a rate limit, sessions started by an agent, a schedule or an automation) wait instead of starting. Your own new session, and a message you send yourself, always start at once.
  • Heavy local runs (typecheck, tests, lint, builds, installs) started by an agent wait too. A run you start yourself in your own terminal never waits.

"Out of memory" means free memory is under the larger of 4 GB or 5% of the computer's memory, or the space left to promise to programs is under 3 GB while memory is also tight. Work starts again only when the computer is back to twice that, and then one piece at a time (sessions at least 10 seconds apart, heavy runs a minute apart), so everything does not wake at once. Nothing already running is stopped. A heavy run that has waited 30 minutes is recorded in the storm-hold ledger and keeps waiting.

It is on by default. Turn it off with the out-of-memory hold setting (Settings → Performance), or AMC_DISABLE_CRITICAL_MEMORY_HOLD=1; AMC_DISABLE_MEMORY_RESUME_HOLD=1 turns off only the heavy-run half. If the reading is missing or unreadable, nothing waits. Contract: memory-pressure-wait-contract.md.

For a full "my computer feels slow" walkthrough, see slow-computer.md.

  • slow-computer.md — the free-first "my computer feels slow" guide.
  • Omniscio’s unreleased-feature (“Lab”) gate — how Tier 2 stays hidden until it ships.

Last verified 2026-11-03