DocsAI Readers › Reading history & revisit

Reading history & revisit

Last updated June 1, 2026 · 3 min read

Slima keeps every reading — revised a book three times? You can compare three reports side-by-side.

AI Beta Readers "Reading History" view: the left list shows two saved runs, each with its continue-reading and Kindle-rating scores; the latest run is tagged with its change versus the previous run (−2.7). The right pane shows that run's Reading Report overview.

Where reading history lives

Two entry points:

  1. AI Readers home list — newest first
  2. Inside a work's workspace — switch the left panel to the "Reading History" tab (next to "Select Content") → all readings for this book; on mobile it's a bottom-nav tab

Reports persist

Status Retention
Completed reading Permanent (unless deleted)
In progress Until done
Failed Permanent (unless deleted)
Deleted Hidden from the list (soft-deleted); no user-facing trash / restore yet

See: Trash & restore

Compare two reports

Each row's automatic score change

Every row in the reading history is auto-tagged with its score change versus the previous run (a +/− on continue-reading intent and the estimated Kindle rating). If a run regresses noticeably, that row gets a red left border to flag it.

Full side-by-side — open two tabs

To line up two complete reports, the simplest way is to open each one in its own browser tab and place them side by side.

History strategies

Strategy 1: rerun after every major revision

Build a clean progress timeline.

Strategy 2: quick reading after each chapter

Low cost, dense feedback.

Strategy 3: periodic baseline check

E.g. every 5 chapters → one full reading to confirm you're on track.

Want to run again with new readers / a different service?

To run the same book with new personas / a different service, go back to the "Select Content" set-up screen and start a fresh reading. Each history row only lets you open its report or delete it — there's no "Rerun" action and no ⋯ menu.

Related

Was this helpful?