Learn (every feature, explained, in one place)

Library page — describes what users see and how to use it. Self-contained so an outside AI (with no repo access) can read this and answer "what is Learn and how do I use it?"

What it is

Learn is a built-in Omniscio virtual project that collects the app's feature explainer pages into one browsable place, grouped by what you are trying to do. Each row opens a short, self-contained page that introduces one feature and shows it working. It lives in the Insights group of the sidebar, alongside Stats and Shares.

Why it exists

Omniscio already ships these explainer pages, but until now they arrived only through the Feature Discovery Nudge: a card that appears in the Inbox at most once every ~24 hours, showing one feature. That card is good at catching you at the right moment and bad at everything else — dismiss it and the page is gone, with no way back to it and no way to look ahead.

So a user who dismissed a nudge while busy, or who remembers reading about something and wants it again, or who simply wants to see what else is there, had nowhere to go. Learn is that place. The nudge still does its job of introducing features one at a time; Learn is the shelf they all sit on afterwards.

Where to find it

1. Open Omniscio.
2. In the sidebar, find the Insights group.
3. Click Learn (compass icon).

How it behaves

What you see

Eight sections, grouped by use case rather than by subsystem — you look for "I keep getting interrupted", not for "notification services":

Section	What it covers
Attention and triage	Getting interrupted less, and only for things that matter
Hands-off automation	Work that runs without you starting it
Steering your agents	Giving agents the context and abilities they need
Ask and understand	Getting answers out of the app, and replies you can follow
Talk and listen	Speaking to Omniscio, and hearing replies read aloud
Mail, texts and mobile	Reaching your sessions when away from the desk
Speed and search	Getting somewhere faster
Capacity and sharing	Doing more at once, and showing others

Each card shows the feature's icon, its name, a one-line hook, and up to two short lines:

• Whether you actually use it — see the next section. Absent entirely until you have opened that feature's page, so a fresh board is clean rather than covered in markers meaning "no".
• Whether it is switched on, and what sort of feature it is — one grey line, the same shape on every card. It reads like On · Automatic: first the switch — On or Off when the card can read the feature's switch, Always on when the feature has no switch and nothing to set up, Needs setup when it has a switch or a setup step the card cannot read (FlowVoice until it is on, Email Cleanup until Gmail is on and connected) — then whether the feature is Automatic or Manual. A card never prints a state it cannot check. Clicking that line opens the feature's own control, on the tab that holds it, scrolled to and highlighted: in Settings, or in the feature's own panel (AI Suggestions and Zap open Quick Replies on its Settings tab). A feature that is a place opens its panel.

Two ways to arrange them. Everything opens all eight sections at once; By group shows eight group tiles and opens one at a time. Four views narrow which features are shown: All, Your setup (switched on), Not turned on (switched off, or still needing setup, so not usable yet), and Explore (features you are not using yet and have not read, in the order Omniscio would introduce them). A feature that is Always on has nothing to turn on, so it sits in neither switch view.

The reader. Clicking a card opens that feature's page inside the panel, full-bleed, using the same embed the Inbox nudge uses — so a page reads identically wherever you open it. "All features" returns you to the grid.

How Learn measures progress

Learn tracks one thing: whether a feature actually gets used. Not whether you read about it.

The first time you open a feature's page, Omniscio quietly notes how many times you have used that feature so far. Everything after that is a comparison against that starting line. The card then says one of:

On the card	What it means
(nothing)	You have not opened this feature's page, so there is nothing to compare against
Opened, not used yet	You opened the page and the count has not moved
Used 14 times since you read this	You picked the feature up after reading about it
Already in your rotation	You were already using it before you opened the page. That is a success, not a miss

Section headings carry a small counter drawn from the same numbers, and it flips at the halfway mark: below half it counts up ("you use 2 of 6"), at or above half it counts down ("2 left") — whichever number is smaller. A section where you use everything shows no counter at all and drops to the bottom of the board.

Under the header there is a plain dated list, "What you started using" — "You first used Zap on 12 Sep", newest first, capped at five with an expander for the rest. It appears only once something has actually happened; an empty list is not shown at all.

What it does not do

• There is no streak and no score. Nothing counts how many days in a row you have opened Learn, and nothing awards points, XP, levels, badges or tiers. A day-counting streak measures showing up, which you can run up without ever using a feature — a number you can raise just by visiting a page is a reward for visiting, not a record of anything you did. Every number on this board can only move because you used a feature, and none of them can be raised in advance. (Learn did briefly have a five-tier streak badge. It was removed in September 2026, along with the code behind it, for exactly this reason.)
• It never shows a score out of 24. A surface like this realistically moves a handful of features into genuine use, so "3 of 24" would render a success as an 87% failure. The only denominators on the board are per-section, where they run from one to six and are actually finishable.
• It does not nudge, notify, or nag. No banners, no unread counts, no inactivity reminders, no countdowns. You come here when you want to.
• It does not mark a feature as already pitched. Browsing here never tells the daily nudge "this one has been shown" — otherwise reading about a feature in Learn would quietly stop it from ever being introduced to you properly.
• It shows only features that have a published page. The catalog carries more features than that; the ones without a page are not listed rather than shown as empty rows.

What it records

Opening a page writes three small things to your own machine, and nothing leaves it:

• the day you opened it — a plain activity log,
• how long the reader stayed open, and how many times you opened it,
• on the first open only, that feature's usage count, as the starting line described above. It is written once and never revised, because a starting line that moved would erase the very difference it exists to measure.

Reading time is recorded because it is honest and costs nothing, but it is not scored and it is not shown to you. Its only job is to stop Explore from suggesting a page you have already been through. Omniscio cannot see how far you scrolled a page — each one renders in a sandboxed frame it deliberately has no way to read into — so time-in-reader is the most it could ever know, which is part of why it is not treated as progress.

Related

• The Feature Discovery Nudge — the Inbox card that introduces one feature at a time. Learn shows the same pages; the nudge decides when to interrupt you with one.
• Stats → the feature-usage counts, which are the same real numbers Learn compares against.