Omniscio documentation
Browse all documentation
  1. Getting Started13
  2. Sessions & Agents123
  3. Inbox & Notifications65
  4. Projects & Tasks96
  5. Automation & Scheduling84
  6. Knowledge & Memory26
  7. AI Features66
  8. Integrations102
  9. Plugins & Marketplace34
  10. Cloud & Teams57
  11. Settings & Customization64
  12. Account & Billing28
  13. Troubleshooting86
  14. CLI & API Reference24
  15. Legal & Policies4
  16. Uncategorised17

Sessions — the lifecycle and its controls

A session is one Claude run inside one project folder. It starts, it works, it stops and waits for you, and then you park it one of several ways — pause, snooze, save, archive, stop or move. This page is the map of that life: one line per step, each linking the page that owns it.

What it is

The life of a session, in order:

  • It starts. Pick a project and start a new session: Omniscio spawns a fresh claude CLI inside that project's folder on your active account, and the row appears in the sidebar as starting and then running. See Start a new session.
  • It works, and it stops to ask. While the agent is working the row is running. When it finishes a turn, or needs a decision from you (a question, a plan to approve, a permission), it parks itself in needs_you and waits — that is the amber dot, not a failure. See Session statuses.
  • You can pause it. Pause kills the running CLI and parks the session in paused. Nothing is lost: your next message respawns the CLI with the conversation resumed, exactly as if it had never stopped. Pause is mutually exclusive with snooze. See Pause or stop a session.
  • You can snooze it. Snooze hides a session that needs you until a time you choose, then brings it back to your attention. Unlike pause, snoozing does not kill the process. See Snooze a session.
  • You can save it. Saving is a bookmark, not a state: the session keeps whatever status it had and moves into the collapsible Saved section, so finished or valuable work stays findable. See Save a session.
  • You can archive it. Archiving files the session away into the project's Archived section without deleting anything, and it can be restored again. See Archive a session and Browse archived sessions.
  • You can stop it. Stopping ends the process — and a session you stop this way stays stopped: the auto-restarter, other agents' messages and the automatic lander all leave it alone until you restart it or send it something yourself. See Pause or stop a session.
  • You can move it. A session can be re-filed under a different project, one at a time or several at once. See Move a session between projects.
  • You can act on many at once. The Manage sessions modal groups the bulk actions — Stop, Restart, Pause, Archive, Message, Refill — into one picker with a view per action. See Stop, restart, pause, archive, message, or refill many sessions at once.

Two things happen to a session without you asking:

  • Recovery after a restart. Sessions that were still running when the app closed are brought back automatically a few seconds apart — and only genuinely active ones (running, starting or stalled) are eligible, so a session you had stopped or finished is not revived. See Auto-restart stuck sessions.
  • Hibernation. A session that wakes on a schedule just to find nothing to report can stay quietly running instead of landing in your inbox every beat. See Session hibernation.

Where to find it

  • The session row in the sidebar carries the status dot, and right-clicking it opens the actions (Stop, Restart, Pause, Save, Archive, Move and the rest).
  • The session's ⋯ menu in its header carries the same actions, with each one's keyboard shortcut shown beside it.
  • The Manage sessions modal is where whole sets of sessions are actioned at once.

How it behaves

  • No status blocks a message. Sending to a paused, ended, error or archived session respawns the CLI and continues the conversation — the status only decides what the row looks like and whether the session is asking for you.
  • Pause and snooze do different things. Pause stops the agent from working; snooze only hides a session that is already waiting on you until a chosen time.
  • Stop sticks. A session stopped from the sidebar or the bulk picker stays stopped — nothing revives it on its own until you restart it or message it.
  • Recovery is narrow on purpose. Only the active statuses come back after a crash; a session you deliberately parked or finished does not.
  • Every state is one of eleven words with one meaning each — see Session statuses for the list, the colours and what each one asks of you.

Related

Last verified 2026-10-06