Curator

Your reading firehose,
filtered by your prompts.

Readwise Reader collects everything. Curator decides what is worth your attention right now — evaluating every incoming item against AI filters you author, tagging what survives with curator/<why>, and serving it as a fast, installable magazine feed.

Sign in

Curator reads and mutates your Reader account, so it's locked to its owner.

Single-user app — only the configured owner account can get in.

How it works

Filters are the product

Write filters in plain language — “pass significant CA/US politics, archive the horse-race noise” — and paste in your own context, like an artist list. No integrations, no rules engine: your prompts decide.

Every survivor explains itself

Anything that makes it into the feed is tagged with the filter that passed it — curator/music, curator/claude-news — in Curator and back in Readwise Reader. Segment the feed by tag; audit any verdict.

Safe by default

New filters run observe-only: test them against your recent items and watch would-be verdicts before anything touches Reader. Destructive actions are opt-in, per filter, once precision is proven.

Summaries & the Daily Brief

Survivors get a 2–3 sentence AI summary so you can triage from the card. Once a day, a push notification links to a brief: everything that survived, grouped by tag, with a short overview on top.

Under the hood

  1. 1 · ObservePolls Reader's API for new feed items — deduplicated into one event log.
  2. 2 · JudgeCheap heuristics first, then one batched Claude call across all your filters.
  3. 3 · ActSurvivors tagged in Reader with provenance; enforced failures archived.
  4. 4 · ReadA magazine-style PWA feed, tag segmentation, and the once-daily brief.