When it arrives
The brief sends at 07:00 in your workspace’s own time zone — not ours, and not UTC. A customer in Auckland and a customer in Denver both get a brief that says “this morning” and means it.What it says, in order
1
The artifact, first — or not at all
The newest finished piece of work since the last brief: a page rewritten, a pull request opened, an outreach draft filed. If there is nothing to lead with, this section is absent — the brief does not manufacture a highlight.
2
What needs you
Up to three things waiting on you, oldest first. This is the same list as your Inbox; the brief is a pointer to it, not a second copy of it.
3
The numbers
Counts, with the sample size behind each one — never a percentage on its own, and never a day-over-day comparison. One day is too small a window to compare honestly; see How we collect data for why.
4
What re-reads when
What is scheduled to be checked again, and when, so you know what is still pending rather than assuming today’s numbers are final.
Quiet days send nothing
If there is no artifact, nothing needs you, and nothing has changed, no email goes out. A quiet day is not a failure to report on; it is the absence of anything worth interrupting your morning for.The Monday edition is the exception
The weekly edition always sends, even on a quiet week, with two things the daily edition does not carry:- One observation, stated as a count with its sample size — never a bare percentage.
- One verbatim answer quote from a real model response, word for word, never paraphrased.
The same brief, wherever you read it
The email, the app, and your own tooling all show the identical brief — composed fresh from the same data each time, not three renderings that can drift apart. Pull it yourself with theget_brief MCP tool or GET /v1/brief in the REST API.