UI Usage Tracking — see which controls and integrations you actually use
Omniscio records on your own device which named controls you click and which sidebar integrations you open, then shows a used-versus-never-used report in Settings, with a Flow card for what you tend to do right after a control and an on/off toggle that stays separate from telemetry.
On this page
What it is
Library page — describes what users see and how to use it, then how it works under the hood. Self-contained so an outside AI (with no repo access) can read this and answer "what is UI Usage tracking and how does it work?"
Omniscio quietly records, on your own device, which named controls you click (buttons, links, toggles, tabs, menu items) and which sidebar integrations you open (Gmail, GitHub, SMS, Stats, KMS, and the rest). It then shows you a plain "used vs. never used" picture so you can tell what you actually rely on versus what you've never touched — the point being to decide later what to remove or auto-hide so the app stays uncluttered.
The "used vs never used" report is built on your own device — it needs no server. One honest caveat: Omniscio also folds anonymous per-control click counts into its daily diagnostics digest — the same anonymized fleet health summary that usage telemetry and crash reports ride. Those are counts only (a catalogued control's internal name + how many times it was clicked, filtered to Omniscio's known control list and keyed to a random install id) — never message content, file names, or anything that identifies you. Usage telemetry is always on and has no off switch (Settings → Diagnostics → Health says so on its own card, and the privacy policy states it), so this egress is not something you consent to or revoke. What you can control is the local recorder: turn off "Track which UI controls you use" and nothing is recorded, so there is nothing for the digest to send. (See "The on/off toggle, and how it relates to telemetry" and "Stage 2" below.)
Where to find it
- Open Omniscio.
- Open Settings (gear icon in the toolbar, or the Settings entry in the Omniscio sidebar group).
- Go to the Diagnostics section.
- Two things live there for this feature:
- A toggle, "Track which UI controls you use" (on by default). The report it builds is local; anonymous click counts also ride the always-on daily diagnostics digest (see "The on/off toggle" below).
- A "UI Usage" card below it that shows the report.
How it behaves
What the card shows
The UI Usage card has a small row of time-window buttons — Last 24h / 7 days / 30 days / All time (it opens on 30 days) — and a "Tracking since <date>" note so you know how far back the data goes. Under that, two groups:
- Controls — the named buttons / links / toggles / tabs / menu items in the app.
- Integrations — the sidebar integrations (the built-in virtual projects like Gmail, GitHub, SMS, Stats, Inbox, Settings, etc.).
Each group is split into two lists:
- Used (N) — the controls/integrations you've used in the selected window, most-used first, with a click count next to each.
- Never used (N) — the ones you've never used (in the catalogue of trackable things), listed alphabetically.
Switching the time window re-runs the report, so "Never used" under Last 24h means "you didn't touch it today", while "Never used" under All time means "you've never touched it since tracking began".
Under each Used list, a small mobile / desktop split shows how much of that usage came from a phone versus a computer (a phone icon and a monitor icon, each with a count) — so you can tell, for instance, that a control you rely on is mostly used on mobile. The split appears only once there's device-stamped usage to show; older data recorded before this was added simply isn't attributed to either device.
The "Never used" list looks huge on day one — that's expected, not a bug
When you first turn the app on, everything is unused until you click it, so the "Never used" lists start out long and the "Used" lists start out short. This is normal. As you use Omniscio over days and weeks, items move from "Never used" into "Used" and the lists become a meaningful map of your real habits. A long "Never used" list early on is not a sign that tracking is broken — it just hasn't seen you use those controls yet.
Off is left out of "Never used" — for both integrations and controls
If you've turned an integration off (so it isn't even showing in your sidebar), it is not listed under the integrations "Never used" list. The reasoning: off is not the same as unused. The "could be opened" universe is the set of integrations currently visible to you, so a feature you deliberately disabled isn't held against you as "never used".
Controls follow the same rule. A control that simply cannot appear in your copy of Omniscio is left out of the controls "Never used" list too — because you never could have used it. Three kinds are filtered out: dev-only controls (they exist only in a developer build, never in the shipped app), platform-specific controls (e.g. the Windows-only AutoHotkey manager, hidden on macOS/Linux), and controls behind an in-development feature you haven't turned on. As soon as such a control can render for you — you're on the right platform, or you enable the feature — it re-enters the "Never used" list until you use it. So the list stays a map of things you could use but haven't, not a pile of things that were never reachable.
The device you used something on is also recorded, so the card can show a mobile vs. desktop split (see below).
Flow — what you tend to do right after a control
On a developer build, below the UI Usage card sits a small companion, the Flow card (an installed copy never shows it — it is a navigation funnel for the product team). Pick a starting control (e.g. "Go to inbox") and it shows the controls you most often use right after it, within the same app session — a first look at your real navigation habits ("after I open search, I usually attach a file next"). Like everything above, it is 100% local and windowed by the same 24h / 7d / 30d / All time buttons. It's a rough picture, not an exact replay.
To make this possible, each recorded event now also carries two pieces of local-only sequence context: a run id (a fresh random id minted once per app launch — deliberately NOT the stable install id, so it can never link you across launches) and a step number (a simple counter within that launch). Together they let Omniscio reconstruct the order of your clicks within a single run, on your own machine. These two values never leave the device — the anonymous fleet rollup only ever sees per-control counts, never sequences (a build guard enforces that), and any future upload of flow data is a separate, reserved privacy decision.
The on/off toggle, and why it's separate from telemetry
The "Track which UI controls you use" toggle in Settings → Diagnostics controls this feature. It is on by default, and only an explicit "off" turns it off; flip it off and Omniscio stops recording new clicks and integration opens (the card then tells you tracking is off and to turn it on to start collecting).
This toggle is deliberately separate from usage telemetry. It is a local feature switch — "do I want Omniscio to keep this diary of what I use?" — and it gates whether clicks are recorded at all. There is no matching egress switch: usage telemetry (and crash capture) is always on with no setting that turns it off, as the Settings → Diagnostics → Health card and the privacy policy both state. The digest can only send what this feature recorded, though, so switching the diary off leaves it nothing to send.
Privacy — what is and isn't stored
Only two things are ever written for each event:
- Which control or integration it was — the control's internal anchor name (e.g. the catalogue key for the "New Session" button) or the integration's id — and
- When — a timestamp.
That's it. No message content, no file names, no folder paths, no contact names, no personal data is ever recorded. Per-instance things are never stored either: clicking a specific session row, for example, is ignored — only catalogued, named controls count, so a one-off id like a session id never enters the database (see "How it works"). Everything lives in your local Omniscio database; the only thing that can leave it is the anonymous per-control count (the control's internal name + a number, never the timestamp and never anything identifying), which rides the always-on fleet digest when this feature has recorded it — see "The on/off toggle" above.
There is also an anonymous install id — a random UUID generated and saved on your machine the first time it's needed. In Stage 1 nothing reads it and nothing sends it; it exists only so a future Stage 2 could count distinct installs without identifying anyone. It is deliberately a separate random value from the id Omniscio already uses to identify this install elsewhere, so future analytics can never be tied back to your identity by reusing an existing id. If the file holding it is ever lost, a fresh one is minted (counted as a new install), which is fine for anonymous aggregate counting.
Stage 2 — central rollup (partly superseded by fleet telemetry)
Since this feature was written, the anonymous click counts already leave the machine a different way: they ride Omniscio's fleet telemetry daily diagnostics digest, which is always on (filtered to Omniscio's known control list, keyed to a random fleet install id), and the maintainer sees them as aggregate product analytics. So a cross-user rollup of clicks exists today — through fleet telemetry, not through this feature's own pipe.
What is not built is the dedicated path once envisioned here: a ui-usage-specific opt-in upload (catalogue id + kind + count + timestamp + this feature's own install id) surfaced as an "all users" view inside this Diagnostics card. This feature's own install id (see "Privacy" above) is still dormant, and that "all users" tab does not exist. Either way, usageTrackingEnabled gates only local recording; the egress that DOES happen rides the always-on fleet telemetry digest and must never weaken the local guarantees above.
Related
Two neighbouring surfaces are worth reading next:
- Stats — the broader "how you use Omniscio" virtual project (cost, tokens, feature-event counts, trends). UI Usage tracking is narrower and local-only: it's about which named controls/integrations get clicked, surfaced in Settings → Diagnostics, not in Stats.
- Feedback channel opt-out — the neighboring Settings → Diagnostics toggles for silencing outbound feedback/telemetry email (a different, send-related consent).
Last verified 2026-09-28