Omniscio

Stay alive (sessions that survive crashes and a full memory)

Any session can be marked to stay alive. A marked session comes back on its own after a crash, is never archived by an app sweep, and when its memory fills it hands over to a brand-new session that opens with its hand-over note and every message the owner sent it. Crew leads and foremen are marked automatically. The owner, or a session above it, can replace one with a fresh session at any time.

On this page

What it is

Some sessions should never quietly stop: a long mission, a lead that other sessions report to, an overseer. Marking a session to stay alive keeps it going through the two things that end a long session: a crash, and a full memory.

What a marked session gets

  • It comes back after a crash. If its process dies in the middle of a turn, the app starts it again on the same session, with its history. It backs off between attempts (5 seconds, doubling to 8 minutes, at most 5 a day) and raises one card if it keeps failing.
  • It stays down when that was the point. It is never brought back if you stopped it, archived it, a spend cap stopped it, or it crashed so often that recovery gave up.
  • No sweep archives it. Idle sweeps and cleanup rules leave it alone. You, its own self-archive, its hand-over, or ending its group can still close it.
  • It hands over before its memory is squeezed. At about 450,000 tokens it is asked once to write a hand-over note. At about 500,000 a new session starts in its place. The new session opens with: why it was started, its place in its group, the note, the brief the work started from, every message you sent it (word for word), and its last few turns. Earlier turns that only said "still waiting" or "nothing to do" are left out of those; the very last turn is always kept. If the old session kept working after it wrote the note, a line above the note says when the note was written and how many turns came after it, and tells the new session to trust the later turns where the two disagree. Its group place, the sessions under it, its unanswered messages, wake schedules, folders, permissions, cards and review panels move to the new session. The old one is archived once you have read its last report.
  • The new session says it was started by the app. Its opening message is shown as coming from Omniscio, never as something you typed, and its agent is told the same. A "Spawned by" link at the top of it opens the session it replaced.

The two points are the settings stayAliveNoteTokens and stayAliveHandOverTokens. They have no screen of their own yet; ask an agent to change them, and the note point must stay below the hand-over point.

Who is marked

  • Crew leads and foremen are marked when they take their post, and unmarked when they leave it. When one hands over, its crew seat moves to the new session. Mission V3 crews and the always-on overseer keep their own path for now.
  • A crew member's seat follows a hand-over too. When a marked session that is a plain member of a crew hands over, the new session takes that seat with its label and its task text and its own new title number, on a crew off the mission loop and on one that is on it. A lead seat on a mission-loop crew moves through the mission loop's own seat hand-over, so the crew is never left with an archived lead. A seat that cannot move is never silent: the new session is told what went wrong and how to fix it, and the old session's record keeps the problem. The old session's record is also kept whole after any seat moves — its successor, its lineage and its steps — so the history of a hand-over survives the stand-down.
  • The seat still moves when the roster has already let the departing row go. The crew's own record names the post, and the successor is seated straight into it — the same crew, the label and the task, and its own new title number, because the crew's numbering gives every membership its own. A session that left a crew on purpose is not a post to hand on.
  • Any session can mark itself, or be marked by a session above it in its group, or by you.
  • Only engines that report their conversation size can be marked: Claude and the Anthropic-compatible models (DeepSeek, GLM, Kimi).

Replacing a session

You, or a session above it, can hand a session to a new one at any time with a short note. A turn that is running is stopped first, then the hand-over runs. A session cannot replace itself, and a session can be replaced at most three times an hour.

A replace can also name the engine the new session starts on, so a session that came up on the wrong model can be moved without losing its place. The engine is checked first: it has to be one that can be kept alive and that can start on this computer, and if it is not, nothing is changed. With no engine named the new session stays on the old one's engine.

What it never does

It never replaces a session because it looks slow, quiet or stuck. Only a crash, a full memory or a replace does anything.

Last verified 2026-11-13