Omniscio

Toolchain, provenance and platform tools

These six things are separate tools rather than one feature, but together they are the machinery under the app: the external command-line tools Omniscio installs and drives, the trace from any inbox action back to the session that did it, your own workspaces, a functional check of a web app an agent built, encryption for your local database, and a prompt to clear out share links nobody has opened. Each is documented in full on its own page; this page is the map.

On this page

What it is

  • Tools view — the catalogue of external CLIs Omniscio can drive (29–31 of them across ten categories): what is installed, what is missing, and an Install button for each. Closely paired with Toolchain updates, which covers keeping them current.
  • Session provenance — every inbox row an agent raised and every session an agent spawned carries a line naming its origin ("Generated by …" / a pinned "Spawned by …"), so any action can be walked back up the chain to where it started.
  • User management — the self-serve workspaces layer: the workspace list and switcher, so you can create a workspace and move between the ones you belong to.
  • Web-app verification — Obscura, the tool that functionally checks a web app an agent just built: it loads the app, confirms the elements are there, and reports console errors.
  • Database encryption — encrypting your live local database at rest, in two tiers: a transparent one that seals the key in your operating system's keychain, and a zero-knowledge passphrase. Off by default.
  • Shares view — the shares list, including the Smart Share Reaper: an opt-in sweep that finds share links over a year old that were never viewed and gives each a grace expiry rather than deleting it.

Where to find it

  • Settings → Connected Tools (and the Tools view) for the CLI catalogue and its install state.
  • A session's or an inbox row's own page for provenance — the "Generated by" line sits with the item, not in a separate panel.
  • Settings → Workspaces for the self-serve workspace list and switcher.
  • The verification tool's own entry point when an agent builds a web app, and Settings → Database Encryption for encryption.
  • The Shares panel for the reaper's Keep / let-expire card when it has something to ask about.

How it behaves

Nothing here acts silently on your data. The two that touch things you cannot easily recreate are the careful ones: encryption is off until you turn it on and hands you a one-time recovery code it insists you keep, and the reaper never deletes on its own — it asks, with a Keep button that clears the expiry and returns the link to permanent. Its Delete button only runs when you press it, and on a screen recording that deletes the recording itself, not just the link.

They work on demand, not in the background. The toolchain is a catalogue you install from, verification runs when an agent has built something to check, and provenance is a label on the work as it happens. Only the share sweep and (once enabled) database encryption run on their own.

Each is complete on its own page. This page deliberately does not restate them: follow the link for the behaviour, the settings and the troubleshooting of whichever one you came for.

When setup fails

The setup check is the one screen that can stop a first run, and its Get help button comes here. Its own copy is plain on purpose; this section explains what each message means and the one step that clears it.

  • "Setup Check Failed" with nothing more specific — Omniscio could not finish looking for the tools. Press Try again. Continue anyway leaves setup and installs nothing; you can install tools later from Settings → Connected Tools.
  • "Installation failed. Please try again, or install it manually from the tool's website." — the installer stopped and Omniscio cannot say why. Install retries; the external-link icon on the tool's row opens the publisher's own download page if it keeps failing.
  • "Network error. Check your internet connection and try again." — the download could not start. Check the connection and retry. A company proxy or an HTTPS-inspecting firewall can produce the same message; the next row is the one that names it.
  • "SSL certificate error. Check your network or proxy settings." — something between you and the download replaced or refused the certificate. On a work machine the fix is usually the proxy trust setting, not a retry.
  • "Permission denied…" (or "Windows would not let Omniscio install this.") — the operating system blocked the write. Omniscio installs per-user, so a managed PC that forbids that is the usual cause; the row's external link installs it by hand.
  • "A process is using this tool. Close any running sessions or terminals using it, then try again." — a running copy holds the files. Close it (or wait for those sessions to finish) and click Install again.
  • "The install finished, but Omniscio could not find the tool yet. Try again — it often appears after a moment." — the files are there but not on the path the app reads yet. A retry re-probes; it usually clears on its own.
  • "npm is not installed. Install Node.js first from nodejs.org." — the npm-installed tools need Node.js. Install it, restart Omniscio, and retry.
  • "Not enough disk space. Free up some storage and try again."
  • "The install was cancelled before it finished. Try again when you are ready." — a password dialog was closed or the download stopped. Nothing is broken.
  • "The installer wasn't from the publisher we expected, so it wasn't run. Try again, or install it manually from the tool's website." — a safety check refused the download. Use the tool's own website rather than working around the check.
  • "Claude Code needs Git on this PC before your agents can run." — Claude Code runs shell commands through Git Bash on Windows. Install Git from Settings → Connected Tools, then try again.

Keeping the installed tools current is a different surface with its own failures (EBUSY updates, a version that did not take, a tool installed twice) — see Toolchain updates.

Last verified 2026-10-06