Omnivore users save articles, newsletters, PDFs, and highlights because the detail may matter later. Strawberry can help decide what deserves attention now, retrieve the useful claims from a pile of saved reading, and connect those claims to the decision or project that prompted the research.
01
A saved article is not yet usable knowledge.
Reading queues become archives when no one reconnects them to the question that caused the save. Strawberry can inspect the items around an active project and prepare a short, sourced answer from the passages that bear on it.
02
Sort the queue by the decision it can change.
Unread count is a poor priority signal.
Strawberry can compare saved material with your deadlines, open tabs, and active work so tomorrow’s reading supports a real decision rather than a guilty browsing session.
03
Keep disagreement visible in the notes.
A synthesis becomes misleading when it treats all highlighted claims as settled fact.
Strawberry can group supporting and conflicting passages, preserving author, date, and source context for the person making the call.
04
Reset the queue before a new week adds more.
A weekly Omnivore pass should look for saves tied to imminent work, stale items that can be archived, and highlight clusters worth turning into a brief. Save that triage as a skill and prepare it before the weekly plan is finalised.
It can use the saved reading and highlights visible in the Omnivore browser context you provide.
It can prepare a sourced synthesis and retain conflicting passages for your review.
Yes. Save your preferred queue triage as an Omnivore skill and prepare it before the planning session it supports.
Open the relevant saves and highlights. Strawberry can prepare a sourced synthesis that keeps the author, date, links, and conflicting passages visible for your review.
It can review the browser-visible queue and propose groupings, duplicates, stale items, and reading tied to upcoming work. You decide what to archive, tag, or change in Omnivore.
Omnivore Strawberry