Daily report

A weekly briefing on your product, written every morning.

A built-in agent reads the last seven days and writes what changed.

Read the daily report docs
7 vs 7
Days compared each run
Midnight
In the owner's timezone
Cited
Claims carry their evidence
No setup
Bootstrapped on connect
  • Clado
  • Olive
  • Codebuff
  • Attensira
  • Assemble
  • Opennote
  • Stratify
  • Gatekeep

What it covers

Eight sections, and evidence under each one.

The default instructions ask for a full briefing, not a metrics dump. Every claim is expected to carry the analytics, issue, or recording it came from.

Headline

The single most important change this week, and the most likely reason for it.

Traffic and engagement

Users, sessions, and pageviews week over week, with the charts behind the movement.

Pages and paths

Top routes, plus the ones rising and falling — which is usually where the story actually is.

Conversion and funnels

Where people are dropping out and how that shifted against the prior week.

Issues and errors

Spikes, the routes they hit, and how many people they affected.

Session replay evidence

It watches real sessions and attaches them inline, so a claim about confusion comes with the confused person.

How it runs

It sets itself up.

  1. 01

    Bootstrapped on connect

    The first report is kicked off as soon as the SDK starts reporting. There is nothing to configure to get one.

  2. 02

    Runs at your midnight

    An hourly cron fans out to each project at the project owner's local midnight, so the briefing is waiting rather than mid-generation.

  3. 03

    Lands on the dashboard

    The Daily Report card carries the summary and its timestamp. Expand in Chat opens the full conversation, tool calls and all.

Details

It is a real agent, not a report pipeline.

Same stack as your agents
It reuses the normal run loop, toolboxes, and chat UI. What it did is inspectable the same way any other agent run is.
Hidden from the agents list
A system agent that cannot be deleted and is excluded from Manage Agents, so it does not clutter the list of agents you built.
Instructions stay yours
The default prompt is seeded once. Edit it and re-provisioning will not overwrite what you wrote.
Revenue only when real
The monetization section is written only when Stripe is connected. Otherwise it is omitted rather than padded.
Refresh on demand
Refresh summary forces a new run from the dashboard card when you do not want to wait for tomorrow.

Keep going

The rest of the platform.

Everything here reads from the same recorded session — there is nothing to stitch together between surfaces.

Stop guessing what happened.

One SDK, one afternoon. We will walk your team through it on a call and leave you with the recording of your own product.