Omniscio

Toolchain Updates (background checks + native-installer notifications)

How Omniscio keeps the command-line tools it depends on up to date: a background version check, a one-click Update that runs that tool's own update command in the background on your computer, and the silent npm path kept for the pure-npm tools. Covers the two settings that control it, which tools never update silently, how a stuck install reports itself, and the inbox cards with a one-click Update now when Claude Code, Codex or another recommended tool falls behind.

On this page

What it is

Omniscio periodically checks whether the CLI tools it depends on (Claude Code, Codex, gh, git, …) have newer versions available, then makes it easy to update each one yourself, outside Omniscio. The core model (2026-06-29): every recommended tool you have installed gets a one-click Update that runs that tool's own update command in the background on your computer — Omniscio installs nothing in-place for this path, and since 2026-09-30 no window appears while it runs. The command is derived from how each tool was installed (TOOL_PROVENANCE): npm tools → npm install -g …, winget tools (git, github-cli) → winget upgrade …, Go tools → go install …@latest, GitHub-release tools → their own installer, and Claude Code → claude update against the actual binary Omniscio runs (or npm, if that's how it was installed, or winget upgrade --id Anthropic.ClaudeCode --exact when winget installed it — on a winget copy claude update only prints "Claude is managed by winget" and changes nothing). Claude Code used to sit in the silent-npm bucket, which ran npm install -g against a copy that often wasn't even on your PATH — so the Claude Code you actually use never moved. That was the bug; it now updates the real binary, in a background run you trigger. One convenience is kept for the pure-npm tools (playwright, agentmail, repomix): the Auto-update Tools toggle (off by default) silently npm install -gs them in the background when you turn it on, since npm needs no admin and that path has always worked. Every other tool — claude-code, codex, git, github-cli and the rest of the notify-only list — is never silently updated; it always notifies, and your click runs the update in the background. A second toggle, Tool update reminders (toolUpdateNotificationsEnabled, default off), is the master switch for the proactive method — the scheduled background version check AND the single aggregated "N tools can be updated" nudge. Leave it off (the default) and Omniscio won't nudge you; the one-click Update buttons and the Connected Tools panel's on-demand "Check for updates" stay available so you can update by hand anytime. The scheduled check runs when EITHER this toggle or Auto-update Tools is on (so the silent-npm path keeps its detection with reminders off); when only the update-card toggles (below) are on it still runs, scoped to the tools those cards cover; only with all four off does Omniscio stop background-checking entirely. Turn it on to opt into the proactive check + toast. Periodic checks run at startup + every 6 hours on a fixed cadence (module constants, not user-facing settings).

Where to find it

Everything lives in Settings → Connected Tools: the Auto-update Tools, Tool update reminders, Update alerts for Claude Code and Codex and Update alerts for your other tools toggles (under Update settings), a Connected Tools panel carrying each tool's one-click Update button and an on-demand Check for updates, and a Developer section with Run check now, Clear cache, and Simulate update. The aggregated N tools can be updated nudge opens the Tools view, which is where those Update buttons live.

How it behaves

How to use it

  1. Default behavior — nothing to configure. autoUpdateTools is off by default; turn it on and the pure-npm tools (playwright, agentmail, repomix) install silently in the background. The notify-only tools (claude-code, codex, git, github-cli and the rest) have no silent path — they run their own updater (and, for winget/brew tools, sometimes need admin), so they're never auto-installed regardless of autoUpdateTools; each surfaces a one-click Update instead, plus an inbox card when it falls behind (below). Whether anything toasts is governed by the master kill-switch below: out of the box (toolUpdateNotificationsEnabled off) updates stay quiet and only surface in Settings → Connected Tools and the Tools view.
  2. Silent installs are opt-in. With Auto-update Tools off (the default), npm updates show an aggregate info toast with Update + Review buttons instead of installing silently — but only when notifications are on (see step 3) — and the npm trio gets update cards like every other tool. Turn it on in Settings → Connected Tools to install them silently instead. Native-bucket behavior is unaffected by this toggle: it never had a silent install path, and its toasts remain gated by toolUpdateNotificationsEnabled either way.
  3. Default is silent — opt into popups. Out of the box, Omniscio suppresses every "update available" toast (npm aggregate AND per-tool native). Background detection still runs — updates appear in Settings → Connected Tools where you can install them by hand — but nothing pops up to interrupt you. To opt in, Settings → Connected Tools → toggle Tool update reminders on. Independent of autoUpdateTools: with auto-update on, npm tools still install silently in the background regardless of this toggle; flipping notifications on just adds the "update available" toasts back for the cases where auto-update can't act (npm subset when autoUpdateTools is off, native subset always).
  4. Update a tool in the background. When a notify-only tool is behind, or when you click Update on any tool in the Tools view, Omniscio runs that tool's own update command in the background on your computer — no window opens: claude update for Claude Code (against the real binary Omniscio runs), winget upgrade Git.Git / winget upgrade GitHub.cli (Windows) or brew upgrade git / brew upgrade gh (macOS) for the native tools, and npm install -g … / go install …@latest for the rest. Claude Code installed by winget is the exception: its own update command merely prints "Claude is managed by winget … run: winget upgrade Anthropic.ClaudeCode" and exits 0, so a click on it changed nothing at all — Omniscio asks winget itself which version it installed (winget list --id Anthropic.ClaudeCode --exact) and, when that matches the copy it runs, uses winget upgrade --id Anthropic.ClaudeCode --exact instead, parked exactly like the npm case while sessions hold the executable open (winget's package is portable, so it replaces that file in place). Asking winget rather than reading the file's path is what makes this hold wherever the copy actually sits, and the same answer stops an update card offering a version winget does not list yet — when winget is simply behind the project's release, the card says so and the failure card says the store has not published it yet, with nothing to close. A hand-installed tool (RTK, gog) opens its download page instead. Bun is updated through whatever installed the copy on your PATH, because it arrives from npm or its own installer as often as from winget: an npm install runs npm install -g bun, a winget one winget upgrade Oven-sh.Bun, a Homebrew one brew upgrade bun, and anything else Bun's own bun upgrade. Codex works the same way, because OpenAI's own installer (and a Homebrew cask) puts it on your PATH as often as npm does: an npm install runs npm install -g @openai/codex, and any other copy runs Codex's own codex update, which knows how that copy was installed — so a Mac with a standalone Codex first on the PATH and an older npm copy behind it updates the Codex your sessions actually run. pnpm and opencode work the same way — a Homebrew copy runs brew upgrade pnpm / brew upgrade opencode, an npm copy runs npm, a pnpm that came with Node's Corepack runs corepack install -g pnpm@latest (pnpm refuses to update itself under Corepack), and anything else runs pnpm self-update / opencode upgrade — and every other tool also updates the copy your computer runs: Omniscio's own command wrappers in ~/.amc/bin are skipped, because each one hands the command to the next copy on the PATH, and the update goes through whatever installed that copy. When nothing Omniscio can run reaches it (a repomix installed with Homebrew, the kubectl that comes with Docker Desktop), nothing starts, and the button says the tool was installed some other way and should be updated the way you installed it. What the updater prints goes to Omniscio's log file rather than to a console you have to close, and a click that reaches an updater says "Update started on your computer — you'll be told if it doesn't finish" so it is never silent. The card that was clicked goes with the launch, and the follow-up watch clears the row itself once the new version shows up — or reports, in its own card, that the update did not take. Every Update button says what happened: the update started, an update for that tool is already running, a download page opened, or nothing could start. A tool with no working binary left is a special case (an install interrupted part-way can delete a package's launcher files and leave the package half-unpacked): its own updater cannot run, because the binary it would run IS what is missing, so the click reinstalls the package instead — but only where that package manager owns the copy. Where it does not, the click runs nothing rather than leaving a second copy beside a working one, and points you at the one-click install. An update that finishes and leaves no working binary behind says so in its own card, with a Try again that runs that same reinstall.
  5. Recover from EBUSY. If a silent npm update (playwright, agentmail, repomix) runs while another process holds a lock on the tool's files, npm fails with EBUSY: resource busy or locked. Omniscio's INSTALL_ERROR_PATTERNS safety net translates that to the friendly message "A process is using this tool. Close any running sessions or terminals using it, then try again." (tool-agnostic) instead of showing raw npm output. Close the offending session/terminal and retry from Settings → Connected Tools.
  6. Developer tools. Settings → Connected Tools → expand Developer to run a manual check, clear the update cache, or simulate a fake update without waiting for a real remote release.

Update alerts for Claude Code and Codex

When a real check finds Claude Code or Codex CLI behind its latest release, Omniscio puts one durable card per tool in your inbox — "Claude Code needs an update", naming the installed and latest versions — with a one-click Update now. The button runs that tool's own updater in the background on your computer, exactly what the Update button in Settings → Connected Tools does; from your phone it still runs on the computer, and the card says so. Omniscio never starts the update itself. Pressing the button is the answer to the card, so the card goes as the update starts — it does not sit there still asking for the version you just ordered — and the toast says you will be told if the update does not finish. If the update really does not take, a different card appears: "<tool> update didn't finish", naming the version you are still on, with a Try again button that runs the same updater. That verdict is never a guess from a timer: it is raised only once the update process has actually finished and the tool is still behind, so a slow install is never reported as a failure, and a version that could not be read reports nothing at all. Make sure nothing is still using the tool before trying again — though Claude Code no longer asks you to: an update that cannot run while its own sessions are using it is parked and starts by itself the moment they finish. When the update ran through a package manager (npm, winget, Homebrew) that did not install the copy your computer actually runs, the card says that instead: the tool is installed more than once, the update went to a copy it does not use, and Try again will not change that — update it the way you first installed it, or remove the copy you do not need. That card is for an update that finished cleanly and still left the tool behind; an updater that failed outright — a command it could not parse, no permission, a network drop — gets the ordinary "didn't finish" card instead, whose Try again really can fix it. And when the update ran cleanly through Homebrew (or winget) on the copy it installed but that store does not list the new release yet — Homebrew often lists a release a few days after npm does — the card says so and that nothing needs closing; the tool updates once the store catches up. A winget update that answers "nothing applicable" counts as that clean run too, so it always gets this card — even on a computer that holds more than one copy of the tool, where nothing tells you to remove a copy you do not need. Each new version is announced once: a card you dismiss stays quiet for that version, a newer release raises a fresh card, and the card also withdraws on its own once a check proves the tool current. A tool that is offline, mid-install, not installed, or whose version cannot be read raises nothing and withdraws nothing. The cards are on by default and independent of Tool update reminders; Settings → Connected Tools → Update alerts for Claude Code and Codex turns them off, and a brand-new install is not shown them during its first day. Developer → Simulate update for Claude Code or Codex raises the real card too (with no version watermark, so it clears on the next real check or when you dismiss it). If Claude Code's own background updater leaves the whole computer without a working CLI, every session's start is refused, and you get one card that says so: it names the tool, says it went missing on this computer while Omniscio was using it, and its Try again reinstalls it. You get that card once per outage, however many sessions were affected, and it takes itself down the moment a working CLI is back. Nothing is installed unless you click.

Two things about that button are worth knowing. The version the card names is the version the update would really install, not simply the newest release published. npm can be told to wait before it will install a brand-new release, and it then installs the newest release that is old enough — so a card built on the newest one would advertise a version no click could ever install, and would never clear. Omniscio reads that wait from npm itself (its min-release-age, or the before date it is folded into) and names what npm would actually take; on a machine that has not set one, nothing changes. And updating Claude Code while Claude Code sessions are running asks first, because a running session holds the executable open and the update can fail part-way and leave the tool unusable. The question names how many sessions are using it, and its one answer is to update when they finish — the update is parked there and then runs by itself, nothing is ever closed, paused or killed for you, and with nothing running the update simply starts with no question. (Close your sessions first if you want it updated on the spot; that click then has no question to ask either.) Updating Git on Windows while sessions are running asks the same way, because Git's installer replaces the files every session uses to run commands — an update under a running session once left every session unable to run anything. It waits for your sessions to finish and for you to be at the computer, since Windows may ask your permission to install it, and afterwards Omniscio refreshes Git's shell setup (and does so again each time it starts). If you have both a Claude Code and a Git update waiting, they run one after the other.

And Claude Code never updates itself underneath Omniscio. Claude Code has its own background auto-updater, and it used to run inside Omniscio's own sessions: on 2026-10-13 it started a global npm install while about twenty sessions were live, npm replaced the package in place, and every one of those sessions lost its claude command for roughly 75 minutes. Every place Omniscio starts that command — a session, a Council or Writer run, a help-desk answer, the context readout — now starts it with that background updater switched off, so the only thing that updates Claude Code is the Update button and the inbox card described here, on your click. Your own terminal is untouched: run claude yourself and it updates exactly as it always did.

Update alerts for your other tools

The same card covers every other tool Omniscio recommends and can check reliably: Git, GitHub CLI, OpenCode, Pi, portless, agent-browser, pnpm, yt-dlp, Bun, gws, kubectl, RTK and gog — plus Playwright, AgentMail and Repomix while Auto-update Tools is off (with it on, Omniscio updates those three itself, so it never cards them). It works exactly like the Claude Code and Codex card: one card per tool per version, a one-click Update now that runs the tool's update in the background, the card coming down as the update starts, and the same "update didn't finish" card with a Try again button if it does not take; it also clears itself once a check sees the new version. It has its own switch, Settings → Connected Tools → Update alerts for your other tools (on by default); turning either switch off leaves the other family exactly as it was. RTK and gog are installed by hand, so their card says so and its button reads Open download page. A card only appears when the update can really be delivered: a release with no build for your computer never raises one, a release for a tool updated through winget or Homebrew (Git, GitHub CLI, yt-dlp, Bun, gws, kubectl) waits a day so the store has it before the card offers it, and when winget installed the copy you run the card names the version winget lists rather than the project's newest — winget routinely lists a release a little after the project publishes it, and a card naming a version winget cannot install could never clear (that was the report behind this fix). The AgentMail CLI is offered for install on macOS and Linux only: it publishes no build for Windows, so it is never listed as missing-and-installable there, and asking for it directly says plainly that it is not available for Windows rather than failing as "binary not found on PATH". A copy that came from somewhere else — kubectl bundled inside Docker Desktop, yt-dlp installed with pip — gets no card either, because the winget or Homebrew update the button runs cannot reach it (Docker Desktop updates its own kubectl when Docker Desktop updates); a card already up for such a copy is taken back. Bun is the exception: its button follows whatever installed your copy, so it keeps its card. A tool whose copy on your PATH belongs to a project gets no card and no Update button either: when you run Omniscio from its source code, the project's own pinned pnpm and its Playwright come first on the PATH, so their version is the project's to set and an update would only replace a different copy that nothing runs. And the version is always read the way a new terminal sees it — from your home folder — so a project that pins its own pnpm version (Omniscio's own source code does) never makes a card name the project's version instead of your computer's. Docker, Google Cloud SDK, Tailscale, AWS CLI, Python, FFmpeg and the security tools get no card, because Omniscio cannot read their newest version reliably. Developer → Simulate update raises the real card for any of these tools too.

Getting off a package-manager copy (Claude Code)

A winget or npm copy of Claude Code can only move as fast as that store's listing. When the store lags the real release, the copy reads as up to date, no card is raised, and the updater keeps finishing cleanly without gaining a version. The way out is the Claude Code row in Settings → Connected Tools: Use Anthropic's installer.

It installs Anthropic's own copy first, falls back to the npm package when that download cannot be reached, and verifies the new binary runs at a version at least as new as the one it replaces. Only then does it remove the old package — immediately when nothing is using it, at Omniscio's shutdown when a session holds it, and at the next start if that shutdown could not finish. npm is invoked through the command shell, where it resolves to npm.cmd; nothing here ever asks anyone to change a PowerShell execution policy.

Last verified 2026-10-16