Omniscio

Briefings (AI briefing of what happened)

Briefings — the sidebar's Daily Digest — is the once-a-day AI-written recap of everything that happened across your sessions, mail, calendar, SMS, Slack, Telegram, RSS and GitHub. Covers what it includes, how to tune its hour and sources, follow-up questions, alert triage, hidden sections, the per-day usage ledger behind its token and cost figures, and excluded projects.

On this page

Shipped display name is Briefings (renamed from "Daily Digest" 2026-09-01 — it covers the weekly review too). The persisted sentinel __daily_digest__, the dailyDigestEnabled flag, the integration id daily-digest, and this file name all stay byte-stable.

What it is

Briefings is a once-a-day AI-written briefing of everything that happened across your Omniscio sessions, Gmail, Calendar, SMS, Slack, Telegram, RSS, and GitHub — generated by Claude Haiku, stored as a first-class sidebar entry under Briefings, and conversational: you can ask follow-up questions in a chat panel that runs against the same summary. Good for catching up after a day off, a trip, or just a long weekend. Unread digests carry a count badge on the sidebar entry so you can tell when the overnight summary is waiting. The digest is also customizable — you can dismiss alerts you've handled, permanently suppress alert topics you don't want to see again, hide whole sections you don't care about, and exclude specific projects from being summarized at all. Keyboard hotkeys triage the alerts list at the speed of typing.

Not the RSS Feed digest. Settings → RSS has a separate once-a-day summary of your feeds, called Feed digest (rssDigestEnabled) and titled "Feed digest" in the inbox. It curates your RSS subscriptions only and shares nothing with Briefings; see RSS integration.

Default-on: a fresh install generates the briefing without opting in, because the digest is the app's one recurring "here's what happened" reason to come back on day 2 and it previously shipped off. The flip reaches new installs only — an existing user's stored choice always wins, because a fresh install persists every default to disk and config load merges stored-over-default, so anyone who already had the digest off (explicitly or by never touching it) stays off. There is deliberately no force-enable migration here, unlike Weekly Summary's one-time weeklySummaryDefaultOnMigrationDone flip. Turn it off any time below; once off, it stays off.

Default-on cannot quietly bill the company. Generation stops at a tier-aware credential gate before any model call: a free (or signed-out / unresolved) user must bring their own key — the embedded key and the signed-in company gateway are paid-plan benefits — and an unresolved plan fails safe to free. With no usable credential the run raises the deduped "Couldn't generate your daily digest" card and returns, spending nothing. Details in daily-digest-credential-contract.md.

The Briefings sidebar entry also hosts Weekly Summary rows (as of 2026-05-14) — the Monday-morning ISO-week recap with the same stats-card + AI-written-paragraphs + suggestion-cards shape. Both cadences share the same Active/Snoozed/Archived buckets, the same context menu, and the same triage hotkeys. Weekly Summary has independent enable/schedule/cap controls — see its sub-section at the bottom of the Daily Digest settings panel.

Where to find it

Briefings is a built-in tool: find it on the Installed Plugins page (bottom of the side nav), whose In side nav switch adds a row to the side nav — it is always there, so nothing has to be open for it to appear. Click it to open the date list beside the briefing viewer — the viewer opens your most recent briefing for you, so the pane is never a bare "Select a briefing to view" beside a full list (until 2026-10-13 it was, because nothing set the selection on entry). The newest row is the one already open when you come back, and opening the panel does not mark it read. The controls for it live in Settings → Email & Summaries → Briefings (expand the card): the master toggle, the generation hour, the source toggles, and the Customize digest card that holds the section visibility, project exclusions and suppressed-alert list. The Weekly Summary controls sit at the bottom of that same settings panel.

How it behaves

How to use it

  1. It's already on. Default-on for new installs since 2026-08-29 (see Default-on below) — a fresh install gets the morning briefing without opting in. Settings → Email & Summaries → Briefings (expand the card) to tune it, or flip the master toggle off. Pick a generation hour (0–23, defaults to 5 am local — the digest for yesterday lands in your inbox before you check email). Pick which sources contribute — toggles for Sessions, Gmail, Calendar, SMS, Slack, Telegram, RSS, GitHub. Gmail and Calendar are opt-in (2026-09-23, for Google's OAuth verification — their content is sent to the digest's AI model): a new install leaves both off, and even when their toggle is on the digest reads Gmail only while the Gmail integration (gmailEnabled) is switched on and Calendar only while the Calendar integration (calendarEnabled) is — the gate lives in digest-live-fetchers.ts, which both the main gather and the look-ahead use. Scroll to the bottom of the same panel for the Weekly Summary sub-section — independent toggle, independent schedule hour (default Monday 7 AM local), and an independent daily Haiku spend cap (default $0.10).
  2. Let it run. A periodic tick (every 15 minutes) checks the clock; once your chosen hour has passed and today's digest hasn't been generated yet, it runs. If a day genuinely can't be built — the AI keeps returning something unusable — it tries a few times and then waits for the next day rather than retrying all day on your API key. A day with activity is never left blank: whenever the AI write-up can't be made — no AI key, the day's spend cap reached, or an unusable reply — Omniscio saves a basic briefing straight from your activity (hubs with their session counts and cost, messages, calendar, feeds, to-dos and the finished-sessions list), marked with a notice that says why. If a later retry that day succeeds, the full AI briefing replaces it in place; a full AI briefing is never replaced by a basic one, an open briefing refreshes itself when the upgrade lands, and the optional briefing email goes out only for the full AI version (a basic briefing is never emailed, because its message snippets are not filtered by the AI). First launch: Omniscio generates up to 7 days of backfill digests in one shot so you don't start with an empty list.
  3. Read it. Click Briefings in the sidebar. The left pane lists digests by date — unread rows show a small amber dot to the left of the date (matching the amber "needs you" cue used elsewhere in the app — section header, unified inbox row, attention status). The newest one is already open in the viewer when the panel opens; clicking any row opens that one instead. Either way the briefing opens on tabs: Overview (greeting, headline numbers, alerts), your projects tab (named with your project word, e.g. Hubs), Finished (every session that finished on its own and left your board — the "Cleared for you" list — one row each with the summary it wrote), To do (action items and today's schedule), Messages (email, texts, Slack, Telegram, calendar and feeds) and Ideas (suggestions and feature ideas). Each tab shows a count, a tab with nothing in it is hidden, and Ctrl+Tab / Ctrl+Shift+Tab cycle the tabs (arrow keys work on the tab strip itself); the hidden-sections setting still applies inside the tabs. Briefings saved before 2026-10-16 carry the cleared list inside the project text instead and simply have no Finished tab. The stats row near the top renders four pills — N sessions, N projects, $N total cost, and a tokens chip showing the day's combined input + output token count (formatted compactly — 247 under 1k, 34k for thousands, 1.5M for millions, 1.8B for billions). That count includes every token the models processed, and on a coding day almost all of it is agents re-reading their own cached conversation on each step (98.7% on one measured heavy day), so hover the tokens chip for the breakdown — new input, cached for reuse, re-read from cache, and written by agents (briefings generated before that breakdown was recorded show only the input vs. output split) — and hover the total cost pill for the split between what your subscription plans covered and what was billed straight to your own API keys — the total is what the day's usage would cost at pay-as-you-go API rates, so only the API-key part is money you actually paid (briefings generated before that subset was recorded show the same explanation without the two figures). Below those volume pills sits an activity row — three chips showing how you (vs. automation) handled the day: N answered (genuine replies you sent agents), N archived (the sessions and inbox items you archived), and N automated (auto-replies + automation rules that acted for you, plus the sessions automation self-archived and inbox items it auto-cleared) — each chip is shown only when it actually happened that day, with a hover tooltip explaining it. Beneath the chips a Human vs. automated line totals your side (answered + everything you archived) against automation's and shows the automated share as a percentage — it counts session archiving, which dominates a heavy day, honestly on both sides instead of as an inbox-only sliver (an earlier version counted only inbox archives, which badly understated both sides). The viewer's bottom bar carries two actions — Share (export the briefing) and Start session: the same shared "Start a new session" button the alert / drip / scheduled-message cards use (keyboard N), it opens a launch dialog pre-filled with the briefing summary so you can spin up a Claude session to act on the day's briefing in the repo you pick (this replaced the older blank-session project picker).
  4. Ask follow-ups. Scroll to the bottom of the digest viewer — there's a chat input. Type "who asked me about the deploy?" or "what did I miss on the infrastructure project?" and Haiku answers from the digest content. The Q&A thread persists inside that digest.
  5. Generate or archive manually. The Generate now button in the sidebar forces a digest for yesterday (useful if you changed sources or want a re-run). Generation routes through llmProviderService.chat() pinned to provider: 'openrouter', so the embedded OpenRouter key handles the call by default — meaning the digest works for users who have never configured their own Anthropic API key, and keeps working when the user's Anthropic key is invalid or revoked. The user's Anthropic key (if any) is still passed as the circuit-breaker fallback for the rare case where OpenRouter is unavailable. If the whole chain fails — cheap provider down AND no working Anthropic fallback — a red toast surfaces the error message; on a 401-style key error the toast carries an Open Settings action that deep-links to Settings → Accounts so you can paste a fresh key. When generation produces nothing, the reason you are shown is the REAL one: the generator reports a named outcome, so a day with genuinely no activity says so, while no usable credential, the day's spend cap, a paused service, an in-flight run and an empty model answer each say what they are (before 2026-09-30 every one of them was reported as "No activity found", which sent anyone debugging it after a working query — Help Desk 28fd38bb). After three failed generations in a row the scheduler gives up and stops trying (2026-10-14): you get the "Your daily digest keeps failing to build" card, and the once-every-15-minutes background attempts stop so a digest that cannot succeed cannot keep spending your API credit. Generate now is never blocked by that — it is how you restart it, and one successful run clears both the card and the pause, after which the normal schedule resumes on its own. The streak is remembered across app restarts, so restarting does not quietly re-open the loop. Before this, an empty answer from the model was logged as ordinary non-JSON text and counted toward nothing, and one user's key was billed roughly $33/day for two days while the same unbuildable day was retried every 15 minutes — see the postmortem. To archive a briefing you no longer want in the active list, use any of the four sidebar archive paths described in the next section — middle-click, right-click → Archive, the E keyboard shortcut, or the X button on mobile. Archived briefings move to a collapsed Archived section at the bottom of the sidebar; they are never hard-deleted and a single Undo toast (or re-archiving the same row from the Archived section) restores them. Archiving an unread briefing also instantly clears its row from the unified Inbox view (the inbox unread-count is recomputed to exclude archived rows, so the row vanishes without waiting for a full reload).
  6. Dismiss alerts you've handled. Each alert row in the digest viewer's Alerts section has a small × button on the right. Click it and that alert disappears from the viewer immediately. Dismissals persist (they're stored per-digest), survive app restart, and are reversible — re-clicking the alert from another surface that exposes it brings it back. Useful for triaging the alert list down to just the things still on your plate.
  7. Dismiss every alert in one shot. The Alerts section header has a Dismiss all chip. Clicking it marks every currently-visible alert in this digest as dismissed at once. The chip only appears while there's at least one un-dismissed alert. The chip's hint text reflects your live key bindings (e.g. "Press X dismiss · Shift+X suppress · Shift+D all" by default).
  8. Suppress an alert topic so it never re-appears. Each alert row has a ⋯ overflow button next to the dismiss ×. Open the menu and pick Dismiss + don't show again. The alert disappears from the current digest AND its {type, text} is saved to a permanent suppression list — Haiku is told about that list when generating future digests, and a post-generation safety filter strips any alert whose text shares ≥ 1 distinctive token with a suppression. Useful for recurring noise you've decided is not actionable (e.g. "rate limit approaching" warnings on a project you don't manage). Suppressions are reversible from settings.
  9. Manage suppressed topics. Settings → Email & Summaries → Briefings → Customize digest card has a Suppressed alerts subsection listing every suppression you've created, newest first, each with a small Remove button. Removing a suppression makes the alert eligible to re-surface in tomorrow's digest. The list collapses if you have no suppressions yet.
  10. Triage with the keyboard. While viewing a digest, three hotkeys act on the topmost un-dismissed alert: X dismisses it, Shift+X dismisses + suppresses it (same as the overflow menu's "don't show again"), and Shift+D dismisses every visible alert in one stroke. The topmost target is highlighted with a brighter ring so you can see what your next keystroke will hit. Hotkeys only fire while the digest viewer is the active project — they don't collide with the same letters used in Gmail or diff-review. Bindings are user-customizable in Settings → Keyboard Shortcuts under the Daily Digest category.
  11. Hide sections you don't care about. Settings → Email & Summaries → Briefings → Customize digest card. Eleven toggle rows let you hide entire sections of the digest viewer: greeting, stats, alerts, projects, communications, calendar, feeds, action items, feature ideas, suggestions, and today's schedule. Defaults are all-visible. Toggling a section off filters it out of the rendered viewer immediately — the section is still present in the underlying digest data, so toggling it back on is instant with no regeneration needed. If you hide every section, the viewer shows an empty state.
  12. Exclude projects from generation. Same Customize digest card has a checkbox list of all your real projects (virtual projects and soft-deleted ones are not listed). Check a project to exclude it: tomorrow's digest will not gather any of its session activity, messages, or status, and previously-generated digests will hide its row from the projects-section breakdown at render time. Useful for projects that you want to keep around but don't need a daily summary for.
  13. Snooze a digest from the Inbox. Today's digest also appears in the unified Inbox as a row under BRIEFINGS. Right-click the row to open the same context menu used in the Briefings sidebar — Archive, Snooze, or Unsnooze — or press H while the digest row is the active inbox item to open the SnoozePalette. The same setDigestSnoozedUntil mutator drives both surfaces, so a snooze from the Inbox immediately moves the briefing into the Snoozed bucket of the Briefings sidebar, clears the row from the Inbox, and decrements the unread badge — with the same 5-second Undo toast.
  14. Share a digest as a public link. The share dialog lists all eleven sections; Action Items, Calendar Events and Today's Schedule start unticked, because they can name other people. A share never prints anyone else's words: Communications shows only how many messages came in per channel, an action item drawn from an email, text, Slack or Telegram message shows only as a per-channel count (your own session action items still show in full, and an item from any other channel is left out), and calendar events show their time and title but never their notes. The in-app digest keeps every detail. Built by generateDigestShareHtml in share-engine-digest.ts; the dialog defaults live in DigestShareDialog.tsx.

The Briefings sidebar splits the date list into three buckets so old briefings don't crowd out the recent ones you actually want to revisit.

  • Active sits flat at the top with no header — every unread or recently-generated briefing whose digestDate falls within the last 7 days. This is the only bucket that's always visible. Selection (arrow keys, click, the E shortcut) only walks rows in this bucket.
  • Snoozed (N) appears as a collapsed header below Active when at least one briefing has a snoozedUntil timestamp in the future. Expand the header to see the rows; each shows a small "snoozed until …" hint. When the snooze time passes, the row re-buckets passively at the next render — there is no notification or push.
  • Archived (N) is a collapsed header at the bottom, populated by anything you archived plus anything older than 7 days that was never archived (the 7-day cutoff folds naturally into archived). Expand to scroll the full history.

You can archive an active briefing five ways — and since 2026-10-05 all five, plus Snooze, land on the next item the same way the Inbox does. Archive or snooze the open item and the panel opens the row directly below it (briefings and weekly summaries alike, in the order the sidebar draws them); on the last row it opens the one above; when it was the only row the pane closes (on a phone it slides back to the Briefings list). Archiving a row you are not reading leaves the open one alone. Every one of these goes through one shared exit, briefings-panel-exit.ts, which walks the panel with the Inbox's own next-item resolver (findNextItem) — before it, the row X and the header button never moved the selection and E used a private "next active briefing" rule that skipped weekly summaries and stranded the last row. The paths (the keyboard path also registers a 5-second Undo, whose shortcut hint reflects your live undoLastAction binding):

  1. Middle-click the row in the sidebar (mouse button 1 on mousedown — Chromium eats auxclick inside scrollable ancestors, so auxclick won't work; this is desktop-only).
  2. Right-click the row and pick Archive from the context menu. The same menu also offers Snooze (opens the SnoozePalette modal) and, when right-clicking a snoozed row, Unsnooze.
  3. Press E while a digest is selected and the dedicated Daily Digest sidebar has focus. The same keystroke also dispatches when the panel is open and no input is focused. Ctrl+W mirrors E for parity with the close-panel binding used elsewhere.
  4. Tap the small X button that appears on the row at mobile widths (it's md:hidden — never shown on desktop).
  5. Click the Archive button in the top-right of the open briefing itself (the shared InboxArchiveButton, beside Snooze). Once archived, that same button reads Unarchive and restores the briefing — which is also how you can tell the click landed while you are reading the briefing full-screen on mobile and cannot see the sidebar row move. Opened from the Inbox it advances to the next inbox item; opened from the Briefings sidebar it advances to the next Briefings item (above). This button marked the briefing read instead of archiving it until 2026-09-12 — and because opening a briefing already marks it read, it did nothing at all in the Briefings sidebar. Until 2026-10-05 it then archived but left the pane on the archived briefing, its label flipped to Unarchive in the same spot, so a second tap undid the archive.

Snooze opens the same SnoozePalette used elsewhere in the app (sessions, emails) — pick a duration ("1 hour", "Until tomorrow morning", etc.) or a custom date/time. The briefing immediately moves into the Snoozed bucket with an Undo toast. There's no sound, no notification, and no "your snooze expired" badge — when Date.now() > snoozedUntil, the row simply re-appears in Active on the next sidebar render.

Opening the panel from the sidebar — why the newest item is selected on entry

Owner report 2026-10-13: "when you open briefings from the sidebar, it should have the most recent item selected in the main panel."

Opening Briefings mounts the panel's sidebar list beside the main pane, but the pane paints ONLY from the digest store's selectedDigest / the weekly store's selectedSummary — and nothing set either on entry to the Briefings project. The digest store's own auto-select is gated on the unified INBOX (activeProjectId === INBOX_ID), so it can never fire here, and the project-selection path clears the inbox slices without touching the briefing selection. The result: with rows listed in the sidebar, the main pane kept reading "Select a briefing to view" until the user clicked a row.

The specs render the REAL panel against the REAL stores, so they prove the panel's own entry behaviour — the newest row the sidebar draws is the one the pane opens — rather than asserting that a mocked callback was handed a call.

Their wait is the STORE'S OWN mark of a completed load, never a bare no-op: asserting === undefined would be vacuously true and let a broken landing pass. isLoading flips true during the panel's mount fetch and back to false once it answers.

The entry itself is desktop only: on a phone the list IS the landing screen and the detail pane merely follows the selection, so opening one would skip the list the user came for. Same split as Gmail's reading pane. An existing selection wins — returning to the panel resumes what was open, exactly as the rest of the app treats a selection that survives navigation.

Your other computers

When you link your own computers, the briefing counts the sessions every one of them ran that day: the session and cost headline, the per-project rows and the activity counts. A day whose only work happened on another computer still gets a briefing. Just before writing it, this computer collects fresh numbers from the others, waiting at most 10 seconds. Private projects and projects you left out stay out wherever they ran. With Combined, with a per-computer breakdown the briefing also gets one line per computer; This computer only leaves it exactly as before. See Other computers.

  • Briefings (part 2) — how a briefing is assembled: the sources, the prose pass and the schedule.
  • weekly-summary.md — the Monday-morning version of the same recap, sharing one sidebar entry and one shape.
  • automations-and-auto-replies.md — the machinery that acts on a single alert rather than the whole day.
  • gmail-integration.md — one of the most useful sources the digest draws on.
  • daily-brief.md — the other daily summary: a short, un-written inbox card of what shipped, what could not merge and what is held for you.

Last verified 2026-10-16