Omniscio documentation
Browse all documentation
  1. Getting Started13
  2. Sessions & Agents115
  3. Inbox & Notifications59
  4. Projects & Tasks95
  5. Automation & Scheduling75
  6. Knowledge & Memory26
  7. AI Features60
  8. Integrations100
  9. Plugins & Marketplace33
  10. Cloud & Teams56
  11. Settings & Customization58
  12. Account & Billing28
  13. Troubleshooting84
  14. CLI & API Reference22
  15. Legal & Policies4
  16. Uncategorised22

Mobile network priority

An active authenticated phone receives the highest connection priority across Omniscio-managed network activity. It is always on and has no setting to configure, and it applies to both the normal off-loop mobile transport and its in-process fallback.

What it is

Yes. An active authenticated phone now receives the highest connection priority across Omniscio-managed network activity.

This is always on; there is no setting to configure. It applies to both the normal off-loop mobile transport and its in-process fallback.

What it does not do

This is cooperative admission inside Omniscio, not operating-system packet scheduling. It does not cancel a transfer that already started, reorder packets already on the network, control a third-party webview, or throttle arbitrary sockets opened by an external child process.

Those boundaries are deliberate: mobile gets first access to capacity Omniscio controls without risking partial uploads, corrupting work, or starving background jobs indefinitely.

Where to find it

Nothing to open or configure — network priority is always on and has no setting. It applies wherever an authenticated phone talks to Omniscio, and the neighbouring systems it complements are described under Related.

How it behaves

How it works

Omniscio uses three admission lanes for managed network work:

  1. Mobile-critical — phone connection activity and phone-triggered actions start immediately.
  2. Interactive — ordinary user-facing work may yield for at most 150 milliseconds while a phone is active.
  3. Background — lower-urgency work may yield for at most 2 seconds while a phone is active.

A phone keeps priority for 15 seconds after authenticated activity. If it disconnects, Omniscio keeps a 10-second reconnect grace window so background work does not rush into the recovery gap. An idle browser tab cannot hold priority forever, and a desktop browser cannot claim the mobile lane.

What it protects

  • Web Access requests made by an active phone.
  • Omniscio HTTP work that uses the shared managed client.
  • Background AI-provider calls that Omniscio explicitly marks as background.
  • Both Web Access server transports, so fallback behavior matches the default path.

Related

Last verified 2026-09-23