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: it never shows a popup, and its report is waiting in the dialog the moment you open it.
On this page
What it is
Update everything is one control over the four things Omniscio keeps current: the app itself, the command-line tools, the installed skills, and the marketplace plugins. Before it, staying up to date meant four separate trips. It is an orchestration, not a fifth updater — each of its four legs calls the engine that already owns that source, so there is still exactly one place per source that knows how to download, verify and install.
The same sweep can also run by itself, on a timer, so the install stays current without anyone clicking. Both the button and the timer reach the identical walk, under the identical promises.
Where to find it
- Toolbar → Update everything — the button. It opens a dialog that shows the newest report at once (the last background run, or your last press) and quietly re-checks behind it — nothing is installed by opening it, and the rows never blank while it looks. Pressing Update everything applies everything.
- Settings → Connected Tools → Update everything — the switch that shows or hides the toolbar item.
- Settings → Connected Tools → Update everything automatically — the background switch, on by default.
How it behaves
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).
- Updating — tool updates were started and are still running in the background, one tool at a time. Nothing has finished yet, so it is neither "Updated" nor "Up to date".
- 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, either because a skill you edited yourself is never overwritten, or because the source was already busy and the sweep stayed out of its way.
- 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.
Before any check has ever finished (the very first open after launch), a row shows a neutral Checking… instead — never "Not checked", which means a check came back empty-handed.
What pressing the button does to your tools
Every pending tool gets its own updater — the same one its Update button in Settings → Connected
Tools runs (winget, npm, claude update, and so on). They run one at a time in the background, so
two installers never fight over the same folder, and the button answers straight away: the row
reads "Updating N tools in the background." A tool that only has a download page (rtk, gog) is
never opened in your browser by this button — the row says it needs a manual step instead.
The three small tools Omniscio updates itself (playwright, agentmail, repomix) install in the foreground, so the dialog waits for them. A slow download keeps the sweep working instead of reporting a failure — the wait is bounded by the install's own budget, not a short fixed timeout.
Claude Code updates even while sessions are running when it is the normal (native) install, which puts each new version beside the one in use. A Claude Code installed through npm is replaced in place instead, which this computer will not do while a session is using it, so that one update is parked until your sessions finish and then runs by itself — nothing is closed for you, and it is not left waiting on you either.
Git on Windows waits for your sessions too. Its installer replaces the files every session uses to run commands, so updating it under a running session can leave every session unable to run anything. While sessions are running, Update everything parks the Git update instead of asking you: it counts as updating, and it runs by itself once your sessions finish and you are at the computer (Windows may ask your permission to install it). A later sweep sees it is already parked and does not ask again or start it twice. The same waiting applies to Omniscio's own background shells, which also sit inside the Git folder while your sessions are open — they are the app's, not yours to close, so the update simply waits for a quiet moment and parks itself again if one is not there yet. If the update still fails, its card names the programs that were using Git; when they were Omniscio's own shells it says nothing needs closing and asks you to click Try again in a moment, rather than asking you to close the app's own shells. Afterwards Omniscio refreshes Git's shell setup itself, and does the same each time it starts.
Moving Claude Code off a package manager
If your Claude Code came from winget or npm, the Claude Code row in Settings → Connected Tools carries a second button: Use Anthropic's installer. It installs Anthropic's own copy (and falls back to npm when that download is unavailable), checks that the new copy runs and reports a version at least as new as the old one, and only then removes the old package.
Removing the old copy needs it to be free. When no session is using it, that happens straight away; when one is, the removal runs while Omniscio shuts down, and if the app is closed before it can finish, the next start completes it. Until then the old copy simply stays on disk — nothing your sessions run is taken away underneath them.
The button appears on the row rather than only on a card, because a winget copy that lags the real release reads as up to date and raises no card at all. One switch, Settings → Connected Tools → Offer to move Claude Code to Anthropic's installer, hides every surface; it ships on.
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:
- It never shows a popup. Not for a clean run, not for a source it could not check, not for tools still updating — on a machine where one of those is always true, a popup would fire at every launch and every six hours. The one thing it still raises is the existing plugin-updates inbox card, and only when a plugin wants a permission you have not granted, because only you can grant it.
- It really updates your tools. Every pending tool's own updater runs, one at a time — Claude Code and Codex included, even while sessions are open on a native Claude Code install.
- It never asks for a password. A background run cannot raise a Windows permission prompt or a password dialog, because there may be nobody at the machine to answer it. Tools whose installer can ask (Git and GitHub CLI) are left for the button, and the row says "waiting for you — press Update everything." The one exception is a Git update parked behind running sessions: it waits until you are back at the computer before it runs, so any permission prompt has someone to answer it.
- It does not retry a tool that keeps failing. Each tool version gets one background attempt per app session; a newer version is tried again. A failed background update still raises its usual "update didn't finish" inbox card.
- It never cuts an update off. Omniscio's own idle self-restart waits while any tool's installer is still running.
- It does nothing while you are offline — every source would only come back unreachable.
To see what it has been doing, open the dialog: it opens on the newest report, and a line under the four rows reads "Last automatic check finished … — N updated." That is the answer to "what happened while I was away".
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.
- 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.
- 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.
- 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.
- 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.
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-10