# Refine a digest

> Tell the agent what the report got wrong — the bar, the point of view, the layout — and it rewrites the digest rather than you rebuilding it.

A digest is refined by talking to its agent, in the **Chat** tab beside the report. Say what the
report got wrong and the agent changes the digest to match: the criteria that decide what is kept,
the point of view items are judged from, the fields each row records, and the layout.

## Ask for a change in chat

Type into **Message the agent…** and be concrete about the outcome. Changes worth asking for:

- **What gets kept** — "Drop tutorials and webinar announcements. Keep pricing-page changes even
  when no article covers them."
- **The point of view** — "Judge everything from the side of an Acme product manager deciding what
  to build next."
- **What each row records** — "Add a column for the source's publish date, and cut 'what to
  inspect'."
- **The layout** — "Group the items by company instead of by date, newest group first."
- **Coverage** — "You're missing launch posts on company blogs. Add a rule for them."

The agent edits the report's own document, so the next refresh follows the new criteria. Changes to
what is kept apply to items the digest sees from then on; items already in the report stay until the
agent is asked to clear them.

## Tune digest rules

**Tune digest rules**, in the **Conversation** header, hands the agent the digest's match volume and
asks it to tighten or broaden the rules. Reach for it when the symptom is volume rather than
judgement:

- The report misses things you know were published — the rules are too narrow.
- A refresh reads only part of its window because the rules catch far more than the digest needs.

The button is offered once a digest has a published report, and is unavailable while the agent
already holds a turn.

## Update template

**Update template**, beside **Tune digest rules**, appears when the report was built on an older
version of the report layout than the current one. Press it and the agent compares the two, says in
the chat what would change, and applies the change once you agree. The digest's own items, criteria,
and point of view carry over as they are.

## Read the report's source

The **Source** tab shows the report document as markup, with line numbers and a **Copy** button. It
is the fastest way to see what the agent actually wrote — the goal, the criteria, the record fields,
and the items it is tracking — when the rendered report doesn't explain a decision.

## Clear the conversation

**Clear**, in the **Conversation** header, deletes the chat history and starts a new session on the
same digest. The digest is untouched: its report, the document it is built from, and its rules all
keep running on schedule. A clear stops the agent if it is working at that moment.

Clearing is the fix when a long conversation has drifted and the agent keeps re-litigating settled
decisions.

## Delete a digest

**Delete digest…**, in the report header's **⋯** menu, removes the digest. Deleting it also removes
the report, the document it was built from, its tap, and the rules the agent created on that tap.
Deleting the tap from the [Taps](https://firehose.com/taps) page removes the digest the same way. A
deletion cannot be undone.

<Callout type="tip">
  To stop a digest without losing it, use **Pause schedule** instead — a paused digest keeps
  everything and schedules nothing. See [Pause and resume](/smart-digest/reports#pause-and-resume).
</Callout>

## Next steps

<CardGrid>
  <Card title="Reports" href="/smart-digest/reports">
    Cadence, history, email notifications, and share links.
  </Card>
  <Card title="Rules" href="/stream/rules">
    The query language behind the rules the agent writes.
  </Card>
</CardGrid>
