Omniscio

Plugin control of your sessions

A plugin you approve can message, pause, unpause, snooze, archive and unarchive the sessions you pick, even ones it did not start, but never more than you could do yourself and never your private AI Coaching or Journal sessions. It asks you first before messaging, pausing, archiving or reopening a session, and you can turn each of those asks off in Settings → Plugins. It is off until you turn on Plugin control of your sessions in Settings → Labs.

On this page

What it is

A plugin asks for one permission, shown on its install card as an elevated permission:

Permission What it lets the plugin do
Manage your sessions (sessions.control) List, message, pause, unpause, snooze, archive and unarchive the sessions and projects you choose. It never sees what they say.

Starting new sessions in your real projects is a different, stronger permission (sessions.launchAny) and is not part of this one.

Where to find it

  • The switch: Settings → Labs → Plugin control of your sessions.
  • Sharing: when a plugin asks, the session picker opens titled Let (plugin) manage sessions. Tick projects or single sessions. Picking a project covers its sessions, including ones you start later. Your AI Coaching and Journal projects are never listed.
  • The asks: Settings → Plugins has five toggles, all on at first: Ask before a plugin messages a session, pauses a session, archives a session, unpauses a session and brings back a session. They apply to every plugin.
  • Review and revoke: Settings → Plugins → the plugin's card lists every session and project it can manage, marked "(can manage)", with a Revoke button, and every action it took. This panel is on the desktop app only.

How it behaves

  • Nothing is shared until you pick it. A plugin asking about a session you did not share gets the same "not found" answer as for one that does not exist. Letting a plugin read a session's history never lets it manage that session, and the other way round.
  • Never offered and always refused: private AI Coaching and Journal sessions, hidden and review sessions, sessions another plugin runs for itself, and sessions running on another computer.
  • With an ask on, Omniscio shows its own dialog naming the plugin, the session and what will happen, with the whole message for a message. Saying no, closing the dialog or not answering means nothing happens.
  • Turning an ask off removes only that dialog. Your picks, the privacy rules, the session's own rules, the log and the speed limit still apply. A session you closed yourself always asks before a plugin unpauses or brings it back, whatever the toggle says. Snoozing never asks.
  • The session's own rules still apply: a plugin cannot pause an ended session or unpause one that is not paused, and it never archives a session that has an answer you have not read, unfinished work or a live share.
  • A plugin's message is labeled with the plugin's name, goes to one session only, is at most 4,000 characters, and never wakes an archived session or reopens one you closed. A plugin can never message every session at once or speak as you.
  • A plugin can make at most 60 reads and 10 changes a minute, shared with its board and task changes.
  • A plugin never spends Omniscio's money or sees passwords, keys or tokens. A message you approve is your own action on your own session.
  • Revoking, turning the plugin off or uninstalling it stops its very next action, with no restart.

Speed cost

Not measured yet. The feature adds no background work of its own (no timer, poller or watcher); it only does work when a plugin calls it, each call is capped by the shared 60 reads and 10 changes a minute, and listing reads at most 200 sessions. The off-and-on measurement in the shared Speed Cost Format needs a plugin that actually uses this permission, and is owed before the feature goes to dogfood.

Plugin access to boards and tasks explains the sibling permissions for your boards and task lists, the Plugin Marketplace page covers installing plugins and the consent card, and Plugin Developer Mode explains how a self-built plugin can use this permission before the marketplace lists it.

Last verified 2026-11-09