---
title: Daily Brief (what shipped, what is blocked)
---

# Daily Brief (what shipped, what is blocked)

## What it is

One calm inbox card a day telling you what the agents actually **shipped**, what could not merge,
what is **held waiting for you**, and how many dev-pipeline approvals Omniscio cleared on your
behalf. It is deterministic — assembled from your own landing records, with no AI call and no cost.

It exists because the approvals stream and the alert stream had grown past what one person should
read. Measured on a real install over three days: **394 inbox cards** were created (150 / 109 / 135)
and **368 were archived** — read and dismissed one at a time — with no single place to see what had
happened. The brief is that place.

**A quiet day sends nothing.** The card is raised only when something actually happened: work
landed, a merge conflicted, or something is being held for you. Sessions merely being busy is never
a reason to interrupt someone, so work-in-flight and the auto-advance count ride along as context
and never trigger the card on their own.

### Not the same thing as the Daily Digest

Omniscio has two once-a-day summaries and they do not overlap — worth knowing so you can pick, or
run both:

| | **Daily Brief** (this page) | **[Daily Digest](daily-digest.md)** |
|---|---|---|
| Answers | What shipped, what is blocked | What did I work on, and what came in |
| Sources | Branch landings, merge conflicts, held work, gate approvals | Sessions, Gmail, Calendar, SMS, Slack, Telegram, RSS, GitHub |
| Written by | Nobody — assembled from records | An AI model |
| Costs money | No | Yes, a model call per run |
| Where it lands | Your inbox, as one card | The **Briefings** sidebar entry |
| Default | Off | On |

The Daily Digest has no visibility into branch landings at all, so it cannot tell you what shipped
or what is blocked from shipping. That gap is what the Daily Brief fills.

## Where to find it

The Daily Brief has no panel and no sidebar row of its own — its whole surface is the switch that
turns it on, in **Settings → Features**, and the single card it raises in your **inbox** on a day
when something happened. That means there is nothing to open once it is on: you read it the same
way you read any other inbox item, and on a quiet day there is simply nothing there.

## How it behaves

### How to use it

1. **Turn it on.** Settings → Features → **Daily Brief**. It is off by default.
2. **Read it once a day.** The card names the branches that landed, anything that could not merge,
   and anything parked waiting on your decision — for example a branch that changes a dependency,
   which is never landed automatically ([auto-lander](auto-lander-dashboard.md)).
3. **Do nothing on a quiet day.** If nothing shipped and nothing is waiting, no card arrives.

### What the card tells you

- **Shipped today** — the branches that reached master, named.
- **Waiting for your OK** — finished work held back on purpose, most often a dependency change.
- **Could not merge cleanly** — conflicts, with a plain reassurance that nothing is lost.
- **Right now** — how many sessions are still working, how many are waiting on you, and how many
  approvals were handled for you. That last number is deliberate: work Omniscio does on your behalf
  should still be visible to you rather than invisible.

### Good to know

- **It never shows internal identifiers or file paths** — only branch names and plain counts.
- **At most one card per day**, even if the app restarts; a second raise the same day folds into the
  existing card rather than making a new one.
- **If the day's records cannot be read, no card is sent** rather than one claiming "nothing
  shipped" — a wrong summary is worse than no summary.
- **Turning it off** is the same toggle; nothing else changes.

## Related

The other once-a-day summary is the [Daily Digest](daily-digest.md) — the AI-written briefing of
what you worked on and what came in — and it does not overlap this one. The item the brief most
often parks in front of you, a finished branch that changes a dependency and so is never landed
automatically, is explained on the [auto-lander dashboard](auto-lander-dashboard.md) page, and the
wider approval machinery it counts against lives on the [approvals hub](approvals-hub.md) page.