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

Update everything (one-click updates + automatic mode)

One control updates everything Omniscio keeps up to date — the app, the command-line tools, the installed skills and the marketplace plugins — instead of four separate trips. The same sweep can run by itself in the background, and it ships switched on. Automatic mode is deliberately quiet: a run that changed what it could, and has nothing for you to decide, shows nothing at all.

Where to find it

  • Toolbar → Update everything — the button. It opens a dialog that first looks (nothing is installed by opening it) and then applies everything when you press Update everything.
  • Settings → Toolchain → Update everything — the switch that shows or hides the toolbar item.
  • Settings → Toolchain → Update everything automatically — the background switch, on by default.

What the dialog tells you

One row per source, always all four, in the fixed order the sweep runs:

Row What it covers
Omniscio The app itself
Command-line tools The tools Omniscio installs and keeps current
Skills Your installed skills
Plugins The marketplace plugins

Each row ends in one state, and the states are not decoration — several exist to stop the dialog telling you something untrue:

  • Updated — something was brought up to date.
  • Ready to install — an Omniscio update has downloaded and installs the next time you restart. This is the only state that exists because of a safety promise (see below).
  • Up to date — checked, and there was nothing to do.
  • Needs you — something is waiting on your decision, such as a plugin asking for a permission you have not granted.
  • Left alone — deliberately not changed. A skill you edited yourself is never overwritten.
  • Not checked — the source could not be checked at all. It is never shown as "up to date", because that would be a claim the app cannot support.
  • Failed — the source errored; the message carries the reason.
  • Skipped — a source was already busy in the background, so the sweep stayed out of its way.

Automatic mode

With the switch on, the sweep runs shortly after Omniscio starts and then every six hours while it stays open. It runs the same four sources with the same promises, and it is built to be invisible when nothing is wrong:

  • A clean run says nothing. No toast, no alert, no inbox card. If everything was already current, or everything updated cleanly, there is nothing for you to do and you are not interrupted.
  • It speaks up only when it must. A plugin held back for a permission review uses the same plugin-updates card the marketplace's own check uses. Anything else that could not be updated or checked raises exactly one warning naming the sources — one, however many are affected, and repeats collapse onto the same warning rather than stacking.
  • It never asks for a password. A background run cannot raise an elevation prompt, because there may be nobody at the machine to answer it. Those updates wait for you and are reported as needing your attention.
  • It does nothing while you are offline — every source would only come back unreachable.

To see what it has been doing, open the dialog: a line under the four rows reads "Last automatic check finished … — N updated." That line is the answer to "what happened while I was away", which is why a silent success is still inspectable.

The safety promises

These hold identically whether you pressed the button or the timer fired. They are the reason this feature reuses the four existing update paths instead of building a fifth one.

  1. A plugin update that wants a new permission is never applied. It is held for your review and named in the dialog, exactly as the plugin's own update surface would do. An automatic sweep is not allowed to become a silent permission grant.
  2. Omniscio never restarts under you. An available app update is downloaded and staged — the dialog shows "Ready to install" — and it installs the next time you restart. The existing update banner still owns the restart; this feature never takes it.
  3. One source failing never stops the others. Every leg is independent. A tools registry that cannot be reached is reported on its own row, and the skills and plugins sweeps still run.
  4. A skill you edited yourself is never overwritten. If a skill's files differ from the catalog copy because you changed them, the sweep leaves it alone and says so. The catalog copy is different, not newer.

Asking for it from an agent or the command line

The same sweep is reachable as one approval-gated call, POST /updates/update-everything. It enqueues an approval rather than acting immediately, because the sweep legitimately touches skills and plugins and both already sit behind an approval boundary for a command-line caller. One approval covers the batch, and it cannot be un-gated by a setting or an "always allow" grant.

Related

  • App Update Notifications — the banner, the 4-hourly silent download, and rolling back a version. That page owns the restart; this one never takes it.
  • Toolchain update (v3) — the per-tool update flow this feature drives for its tools row.

Last verified 2026-10-06