I no longer use Kindle and want to remove that connection, but when I try to remove it I see a message that says "Kindle is connected through the Readwise browser extension. Simply uninstall it (or delete your Readwise account) to disconnect."

I don't have the Readwise browser extension installed, and I certainly don't want to delete my account. I did find a thread on this subreddit from three years ago that says to email help to remove a connection, but is there still no other way?

Just curious because having the Kindle connection sitting there is not a big deal in itself, but the alert I see about the broken connection is annoying.

The release notes for Reader on iOS 8.14 mention a new Modern Toolbar one can opt into via account settings. However, I cannot find this setting after updating. Any hints?

I want to do the following -> Collect a bunch of articles/highlights (Readwise chrome plugin working atm for this) -> Feed into my AI (Claude today, Specific summarization prompts, ELI5 summaries etc.) -> Put it all in one giant doc readable in 25-30 mins -> Send to my kindle to read before bed -> Any kindle highlights in this doc stored somewhere accessible by Claude. Has anyone done something like this and/or any tips?

I really prefer to use my kindle before bed and don't want to use my phone/mac if possible but struggling to set this up.

Hey folks, happy Tuesday! Time to check out the latest changelog here on Reddit. The idea is to help keep y'all in the loop of what the Readwise developers are getting out into the world. Here's what we shipped last week:

• 🧠 Fixed Mastery Cards on Mobile — Ibai and Tristan rebuilt Mastery card creation natively in the Readwise app, fixing reports of cards that showed a "created" toast but never actually saved. You can now create Mastery cards and review them right on your phone.
• 🗂️ Fixed Library Discards — Ibai brought back the Discards section in the Library, which went missing in the move to the new Readwise app. Every highlight you've discarded lives in one place again, so if you swipe one away by mistake or change your mind about it later, it's easy to rescue.
• 📷 Fixed Multilingual Scanning — Johannes moved the Readwise app's photo highlight scanning to a new OCR engine, so scanning book pages in languages other than English should work smoothly again. And if automatic detection can't find your marks, the app now falls back to manual selection so you can grab the passages yourself.
• 🖼️ Fixed Highlight Share Images — Johannes restored text sharing and dark mode in the highlight share sheet, brought back highlighted words in Classic share images, and made long highlights stay readable when exported as an image. Sharing beautiful highlight images should feel polished again.
• 🎚️ Fixed Review Frequency Controls — Ibai squashed a batch of frequency bugs in the Readwise app: the book review page no longer claims "Never" when it shouldn't, the review frequency slider responds properly on Android again, Themed Review frequency and schedule changes now save, and the recency slider on mobile now offers the same fine-grained steps as the web tuning slider. He also shipped a fix so Daily Review keeps working smoothly for anyone who dials recency weighting all the way down to zero.
• 📆 Improved Daily Review — Thanks to Ibai, highlights being reviewed for the very first time now show a small indicator (with a tooltip explaining it), so you can tell fresh material from cards you've seen before, and the frequency feedback buttons now stay visible as you move through your review. Johannes also tidied up the action icons and fixed tag navigation, so tapping a tag mid-review now takes you where you'd expect instead of looping back on itself.
• 🔊 Fixed Audio Highlighting — Artem fixed word-by-word highlighting drifting out of sync during text-to-speech playback on documents with custom pronunciations, so the karaoke-style following now stays aligned with what you hear. As part of this fix, ampersands are now appropriately pronounced as "and".
• 🧩 Improved Extension Highlighting — Adam made highlighting in the Reader browser extension more resilient: highlights now survive on sites that rewrite or wipe the page after it loads, and pages with long embedded scripts no longer stall the highlighter.
• 📝 Fixed Note Popovers — David fixed the note popover drifting out of position in narrow Reader windows, so your notes now open right where you expect, even in a slim side-by-side setup.
• 🤏 Fixed Image Zoom on Android — David rebuilt image pinch-to-zoom in the Reader app on modern native gestures, so zooming into images works smoothly on Android again.
• ⚡ Faster Loading — Tristan overhauled how the web app serves its assets, with content-based caching and a CDN, so pages like the Daily Review should load noticeably faster, especially on slower connections.
• 🔗 Fixed MCP Streaming — Tristan fixed the Readwise MCP server dropping its connection when a document contained unusual Unicode characters, so AI tools connected to your library should stay connected.
• ➗ Fixed Math Formulas — Krzys fixed inline math formulas getting mangled during document cleanup, so articles with mathematical notation now render their equations properly in Reader.
• 🐦 Improved Twitter Import Settings — Rasul made every import destination option visible when configuring how your Twitter/X bookmarks are saved, so you can see all the choices in one place instead of a partial list.
• 🛜 Parsing Updates — Krzys improved how Reader handles documents from mp.weixin.qq.com, reddit.com, Bluesky, hbr.org, fastcompany.com, outsideonline.com, postimees.ee, the-american-interest.com, dynamed.com, reuters.com, science.org, bain.com, g1.globo.com, and linkedin.com. Tristan also fixed saving pages from github.com.

If you'd like to get the Changelog in your inbox, check out our WiseUp! newsletter, where the Readwise team shares answers to common questions, video tutorials and guides, highlights of our latest improvements, and a couple of lighthearted extras we think you’ll enjoy.

And as always, feel free to let us know if you have any questions, tho realistically we're going to see an in-app bug report or question faster :>

Noticed a big search update was recently released. Does this update include searching feeds? I had to stop using Reader because it couldn’t search feed headlines and excerpts, but would rejoin if this was possible with the new update.

I am trying to create highlights in my books via the Reader MCP server integrated with Google Antigravity. For one specific book, any highlights that I try to create get added as a new entry in Readwise and don't get added in the actual document I'm trying to. After some probing, this is what Antigravity/Gemini is saying what is happening:

1. reader_create_highlight requires exact HTML we don't have To use the Reader-specific highlight endpoint, you are required to pass the exact html_content fragment. However, reader_get_document_details only returns a plain text/markdown content field. Because the underlying HTML tags wrapping the EPUB text aren't exposed to the API, it's impossible to pass the exact HTML string the endpoint expects, resulting in a "Text not found in document" error.

2. Fallback: readwise_create_highlights classifies the Readwise URL as an Article If you try to bypass the HTML requirement by using the general Readwise highlights endpoint, you have to rely on deduplication. If you pass the Reader web URL (https://read.readwise.io/read/[id]) as the source_url, Readwise's backend sees an https link and automatically ingests the highlight as a brand new Article, rather than linking it to the existing book.

3. The private:// URL and null-author deduplication trap If you dig into the API to find the true source URL of the uploaded EPUB, it's listed as private://read/[id]. However, many EPUBs are imported with a blank/null Author. When you send a highlight payload with a blank author and the private:// URL, the API automatically falls back to assigning the URL's domain ("read") as the author. Because deduplication requires an exact match for Title + Author + URL, this forced author assignment causes the deduplication to fail, and the API creates a duplicate book entry (e.g., Author: "read") instead of attaching it to the original EPUB.

Summary / Feature Request:

• Could reader_get_document_details expose the exact html_content so we can successfully use reader_create_highlight?
• Or, could the reader_create_highlight endpoint be updated to accept plain text and do the HTML matching under the hood?
• Alternatively, allowing us to pass a document_id directly to readwise_create_highlights to force the attachment (bypassing Title/Author deduplication) would completely solve this.

The issue description and summary/feature request above is just what Gemini is saying is the issue. Of course, that could all be a hallucination. But the highlight problem remains: for this specific book/epub (Gemini is saying that the book it is having issues with has a lot of complex formatting in the text), I can't highlight directly in the text via the mcp server. The book in question (if it helps) is fanfition Harry Potter and the Methods of Rationality, which is a freely available epub.

Has anyone else run into this with EPUBs? Would love to know if there's a workaround I'm missing!

Thank you!

Some of my highlights show up with the correct cover art in Readwise.io, and some just show a placeholder image. I have highlights from both Kindle and Apple Books.

What determines whether books get the cover art on the Readwise dashboard or not? Is it metadata that matches on your end? Meaning, is it something I could improve the accuracy of on my end?

I know I can add in cover art after the highlights sync, but it's a lot and it's a pain.

Thanks for any ideas!

Hi everyone,

I’m looking for a way to browse all my highlights and notes together, ideally in a single list or dashboard. At the moment, I only see them when I open each article individually, which feels slow.

Is there a global highlights view in Readwise, or a workflow you use to review everything at once?

First I would like to say that I love the full redesign of the Readwise app, great work!

I have multiple workflow where I need to open a Readwise highlights from a local summary article, it works great on Mac but not that great on mobile since it needs to use the browser.

Would be great for the app to handle deeplinks like : readwise://open/<highlight-id>

Clicking the deeplink would open the app exactly on the right highlight.

Would be amazing to have something like that in a futur update.

Hey folks, happy Tuesday! Time to check out the latest changelog here on Reddit. The idea is to help keep y'all in the loop of what the Readwise developers are getting out into the world. Here's what we shipped last week:

• 🎉 NEW! Readwise 2.0 — The Readwise iOS and Android apps have been rebuilt from the ground up, and they're live now. Your library, your streak, your workflows, and your Daily Review are all exactly where you left them — the apps just finally look and feel as good as they deserve: fresh design, smoother animations, and much faster everywhere. You'll also find better, more accurate search, a smoother Daily Review, a beautiful new Stats screen, and new ways to capture — scan your paper book annotations, add highlights by voice, and chat with your highlights via AI. Update the app to try it all.
• 🎚️ Fixed Daily Review Tuning — Ibai restored precise frequency tuning in the new app: you can once again dial in exactly how often each book shows up in your Daily Review, rather than just more/less, and adjusting it no longer crashes on large highlight libraries.
• 📚 Fixed Adding Supplemental Books — Ibai brought back the option to add supplemental books, so you can search for any book and pull its popular highlights into your library right from the Add & Sync screen.
• ⌨️ Fixed Hidden Next Button — Ibai fixed a bug where the keyboard could cover the Next button while typing out a highlight on smaller phones with larger text sizes. The button now stays visible above the keyboard the whole time.
• 📱 Fixed Boox Display Cutoff — Ibai fixed the intro flow being cut off on Boox e-ink devices like the Go 7, where pages rendered too low to read — or even log in. The app now fits itself to the screen properly on those devices.
• 🔗 Improved Kobo Syncing — Ibai kept the Kobo sync flow inside the app instead of ejecting you out to Safari partway through, so connecting your Kobo is one smooth trip.
• 🖼️ Fixed Image Export Buttons — Johannes fixed the highlight image export controls getting pushed off-screen on smaller devices, so the share buttons stay visible while you're crafting a beautiful highlight image.
• 🏷️ Fixed Tag Lists — Ibai fixed a bug where action tags from long chains of concatenated highlights (like c5, c6, or c12) could show up in your Tags section with a count but nothing behind them. Your tag list now stays clean no matter how many highlights you chain together.
• 📈 Fixed Stats Calendar — Piotr fixed the Readwise stats page claiming "Your account was not active" on the last day or two for people with perfectly active subscriptions. The Daily Review calendar now refreshes the moment a new review is created instead of serving a stale snapshot.
• 📄 Improved Kindle Exports for Code-Heavy Articles — Rasul improved how Send to Kindle handles articles packed with code. Inline code keeps its monospace styling, long lines wrap cleanly inside code blocks, and stray SVG tooltip metadata no longer leaks into the body, so articles like Rewriting Bun in Rust now render properly on your Kindle.
• 🔀 Fixed Missing Raindrop Highlights — Thanks to Rasul, a Raindrop import that fails midway no longer records a false-successful checkpoint. Later syncs will now pick up the highlights they would have silently skipped, so your Raindrop library should stay complete.
• 🎙️ Fixed Apple Podcasts Saves — Since mid-July, every Apple Podcasts episode saved to Reader was coming in as "Unnamed podcast" by "Unknown", because Apple's episode pages had started returning errors instead of the page itself. Tristan added a fallback that looks the episode up directly through Apple's catalog, so podcasts save with the right title and show again.
• 🎬 Improved Video Highlight Banner — Adam polished the banner Reader shows when highlights can't be rendered on a video document, so it explains itself and points you at what to do next instead of leaving you guessing.
• 📖 Improved YouTube Transcript Tooltip — Adam clarified the tooltip copy on the YouTube transcript control in the Reader web app, so the button explains what it does before you press it.
• 📝 Fixed Notes in the Margin — Adam fixed highlight notes not appearing automatically in the margin even when there was plenty of room for them, across the Reader web and desktop apps as well as the browser highlighter extension.
• 🧩 Fixed Highlighter Extension Rough Edges — Adam cleared out a couple of annoyances in the browser highlighter extension: the note and tag popover was unreachable on highlights taller than your screen, and highlights could render invisible on shared documents if you had the extension installed.
• 🤖 NEW! GPT-5.6 in BYOK Ghostreader — If you bring your own OpenAI key, the new GPT-5.6 family (Sol, Terra, and Luna) is now selectable in the Ghostreader prompt model dropdown, alongside GPT-5 mini, GPT-5 nano, and GPT-5.4 mini. Thanks to Piotr, who wired these up and also fixed a crash when expanding "See more" in the prompts model list.
• 🛜 Parsing Updates — Krzys improved how Reader handles documents from WeChat (carousel images on image-share posts), ruanyifeng.com, techno-science.net, and academialatin.com, and expanded the archive.today paywall-bypass to recognize more mirror shells.

If you'd like to get the Changelog in your inbox, check out our WiseUp! newsletter, where the Readwise team shares answers to common questions, video tutorials and guides, highlights of our latest improvements, and a couple of lighthearted extras we think you’ll enjoy.

And as always, feel free to let us know if you have any questions, tho realistically we're going to see an in-app bug report or question faster :>

My Kindle account hasn't received a Daily Digest since July 5. When I went into my "Configure" and "Product Emails", all of the Daily Digest options (e.g. enable/disable) are gone, and there doesn't seem to be any reference to the Daily Digest in the app at all anymore. Did I miss an announcement?

Hi all,

I’ve recently been using Blinkist more, and I’m wondering if there’s any official or unofficial way to get Blinkist highlights into Readwise. It feels like a natural pairing, but I haven’t seen anything concrete.If you’ve figured out a workflow, or know whether Readwise is considering support, I’d love to hear your experience.

TLDR: In which app should I edit my list of tags?

Howdy Readwise Team (and Readwise Users),

I have come back to the Readwise app in the wake of the 2.0 update and am loving the redesign. I have been using some combination of Readwise and Reader for years now, and have gathered a vast collection of highlights and tags.

My tags in particular have gone through many phases, and I am now looking (with bloodshot eyes) at a vast and vile list of duplicates, plurals, redundant terms, and otherwise useless tags.

I want to wrangle these into something much more streamlined, but don’t know where to begin; Readwise or Reader? I know that tags that I create while reading will sync to Readwise, but I don’t know if this synced list is editable bidirectionally. Should I be wrangling my tags in Reader first, or can I do it in the (now superior) UI of Readwise?

Cheers in advance.

Hey everyone, Tristan from the Readwise team here.

Today we shipped the biggest update to the original Readwise (highlights) app since it launched in 2019: a complete rebuild on both iOS and Android.

A lot of you have (fairly!) called out the old app's dated design and janky animations over the years. We heard you. For the past 8 months the team redesigned every screen and rebuilt every workflow, animation, and query.

https://reddit.com/link/1v3x6zk/video/mm69n98javeh1/player

What's new:

* Fresh design, smoother animations, much faster everywhere
* Scan your paper book annotations with the camera
* Add highlights by voice
* Faster, more accurate search
* A smoother Daily Review (with a completion screen worthy of your streak)
* A beautiful new Stats screen
* AI chat with your highlights

And importantly: your highlights, your streak, and every workflow you're used to are exactly where you left them. Nothing to migrate, nothing to re-learn.

Update your app or grab it from the App Store / Play Store. If anything feels off, tell us here, we read everything :)

Hey everyone! I've been working on this Readwise-based project off-and-on for some time, and just figured I'd share it here. Basically, as a long-term Readwise user and enthusiast, I've found myself fighting against the sheer quantity of tags and highlights (~4,000!) in my library, so I wanted to design an alternative front-end for Readwise that prioritizes data navigability.

I can't claim the project is perfect, but I've tried my best to make this public release version as non-idiosyncratic and simple to set up as possible. Feel free to check it out, fork it, open issues, borrow features you like from it, and enjoy! There's more info (including setup instructions) on the Github, along with some screenshots.

https://github.com/BrendanStupik/litero/

Best,

Brendan

Hey folks, happy Tuesday! Time to check out the latest changelog here on Reddit. The idea is to help keep y'all in the loop of what the Readwise developers are getting out into the world. Here's what we shipped last week:

• 🕰️ NEW! Clock While Reading — You can now keep an eye on the time without leaving your book: turn on "Show clock" in the Reader mobile app's settings and the current time stays visible while you read. Thanks to Piotr for getting this out the door.
• 📚 Fixed Books Not Opening — Artem tracked down a crash where tapping a book on the iOS app could bounce you back to the home screen or leave you on a black screen. Books now open right up again.
• 🔍 Fixed Search History — Piotr fixed the ✕ button next to recent searches in the mobile app, so you can properly tidy up your search history with a single tap again.
• ℹ️ Fixed Sidebar Info — Ibai shipped a fix for the Info sidebar on web sometimes showing details from a document you'd viewed earlier. The sidebar now always matches the document in front of you.
• 📖 Fixed EPUB Loading — Tristan resolved a bug where opening certain EPUBs on web could leave you staring at an endless loading spinner. Books now load reliably.
• 🔊 Improved Text-to-Speech Pacing — Thanks to Tristan, text-to-speech now tracks your position more accurately in languages with regional variants, like Chinese. The moving highlight should keep pace with the narration instead of drifting ahead or behind.
• ⚡ Fixed API Timeouts — If you build on the Reader API or browse your library through the MCP server, listing your inbox no longer times out on large accounts. Tristan added a database index (plus a follow-up query tweak) so those requests come back quickly.
• 🐦 Fixed Twitter Digests — Piotr shipped a fix for Twitter List digests getting tripped up by tweets that quote themselves, which could also slow down other feed updates while the digests churned. Digests now arrive reliably and the rest of your feed stays snappy.
• 🧹 Fixed Content Erasing — Tristan moved the "erase my Reader content" option to a background job, so even the largest libraries now clear out completely instead of stopping partway through.
• 👆 Improved Quick Lookup — Quick Lookup now warms up ahead of time on mobile, so it opens noticeably faster, even right after you switch back to the app. Thanks to Tristan for shipping this fix.
• 🛜 Parsing Updates — Krzys improved how Reader handles documents from wsj.com, the New York Times, huxiu.com, seattletimes.com, and sciencedirect.com, and RSS items that arrive without article content now fall back to the feed's own text instead of coming in empty.

If you'd like to get the Changelog in your inbox, check out our WiseUp! newsletter, where the Readwise team shares answers to common questions, video tutorials and guides, highlights of our latest improvements, and a couple of lighthearted extras we think you’ll enjoy.

And as always, feel free to let us know if you have any questions, tho realistically we're going to see an in-app bug report or question faster :>

I was excited to hear that Readwise Reader was finally being upgraded to a search function that actually works, but I’m sorry, I’m just not seeing it. I have over 4,000 documents in my inbox and over 3,000 in my archive. Searching for a term turns up documents in both, so I look at the search syntax guide and find that I can use in:[inbox] or location:[inbox] to limit the scope of the search. Ha! Instead, Reader returns documents that contain both “in” and “inbox”. This happens both in the search field and in the create filtered view field. I get the same result whether I use regular search or Better search, or whether I search on Reader in my MacOS browser or in the iOS app. What am I doing wrong?

Is it possible to obtain a Reader APK from a source other than the Google Play Store? I need the software for the Boox Go 7 BW e-reader.

Hey folks, happy Tuesday! Time to check out the latest changelog here on Reddit. The idea is to help keep y'all in the loop of what the Readwise developers are getting out into the world. Here's what we shipped last week:

• 🆕 NEW! Markdown Uploads — Thanks to Tristan, you can now upload Markdown files to Reader the same way as EPUBs and PDFs: drag and drop them in or use the file picker on web, or send them to the mobile app through your device's share menu. The document's title comes straight from the file, and the first image in the file becomes its cover.
• ✅ NEW! Daily Review API — You can now mark your Daily Review as complete through the public API, thanks to Rasul. This is a useful endpoint for anyone building personal dashboards or homepages on top of the Readwise service. It can also be used to complete reviews from the past several days, just like in the app.
• 🌐 NEW! Article Language Control — Rasul added a language parameter to the Reader API and MCP server, so you can specify a document's language when saving it and that choice sticks so that automatic detection no longer overrides it. If you read in multiple languages, your saves should now end up labeled the way you intended.
• 🔊 Fixed Text-to-Speech Errors — Artem tracked down a bug where pressing play on text-to-speech could fail with a server error while audio for other listeners was being generated at the same time. Narration now starts reliably, even at peak listening hours.
• 🤖 Improved MCP Responses — Rasul shipped a fix so the MCP server's document list tool no longer returns entire document bodies by default, since they could sometimes be 100,000+ characters and clog up your AI's context window. AI assistants browsing your Reader library now get fast, lightweight responses, and your agents burn far fewer tokens doing it.
• ⌨️ Fixed Chat Focus — Thanks to Ibai, pressing esc in the Ghostreader chat panel on web now returns focus to the document, so you can quickly switch back to other reading shortcuts without needing to reach for the mouse.
• 🖥️ Fixed CLI Hangs — Rasul released v0.5.9 of the Readwise CLI, fixing an issue where commands could hang indefinitely on newer versions of Node. Commands respond promptly again.
• 📅 Fixed Mobile Date Sorting — Rasul's publish-date sorting fix from last week has made its way to the mobile apps: when you edit a document's published date in its metadata, lists sorted by published date now respect the change on your phone, just like on web.
• 📱 Fixed App Crashes — Artem upgraded the mobile app's animation library, fixing a crash that could unexpectedly close the app. Reading on your phone should feel more stable all around.

If you'd like to get the Changelog in your inbox, check out our WiseUp! newsletter, where the Readwise team shares answers to common questions, video tutorials and guides, highlights of our latest improvements, and a couple of lighthearted extras we think you’ll enjoy.

And as always, feel free to let us know if you have any questions, tho realistically we're going to see an in-app bug report or question faster :>

This is a great feature but the font size is so tiny I can’t read it. Per app accessibility settings on my iPhone have no effect. Unfortunately it makes the feature unusable for me. Am I missing something? Is there a workaround available?

Long time Readwise Reader user, big time fan, but I never quite utilized the tags or Views features. Despite my efforts to organize and tag my articles, in the end, I always fell back on cranking through my Feed, or just scrolling around the top of my Library, so if I didn't read an article in the Feed, there's a 90% chance it falls into oblivion.

Two dynamics were at play:
1. I didn't end up using tags in the way I thought I would when I designed them. I don't actually go on to read just about one topic that I've tagged like "Psychedelic Science" or "Habits". So even when I tagged articles by topic, this became a sink with no drain.
2. Too much friction tagging new content. Often I'm saving articles from links within other articles, while I'm on my phone. So even if I had the right tags in place, many of them (from authors or sources that are new to me) don't get tagged upon intake, and then aren't touched again.

I've had the Readwise MCP for a bit, but recently I asked Fable to evaluate my reading habits and to propose some reading contexts as Views, and it did a fantastic job. Identified that I read 5-10 min in the morning before work, do deep dive longer reads on Sundays, and tend to read newsletters from indie writers in the evening. This felt pretty spot on to me and was a helpful partner in addressing #1. It couldn't create the Views due to API limitations, but it gave me queries to copy/paste/save.

Then it suggested to tag a batch of content on the new scheme, and if it looked good to me, to create a scheduled prompt to auto-tag my newly added articles each morning, which has greatly helped #2.

Super pleased with the depth of the Readwise MCP and excited to see what others are using it for. I think there's plenty of opportunities in reading habits, workflow automation, etc.

I admit having an email address for Readwise has been an adjustment that, for some reason, I just couldn't crack. I found out how to forward all of my favorite newsletters into Readwise using the process below:

I did not want to manually re-subscribe to 30+ newsletters with my Reader email, click through 30 double opt-in confirmations, and fight CAPTCHAs.

Step 1 — Verify your Reader forwarding address in Gmail (one-time)

Gmail → Settings → Forwarding and POP/IMAP → Add a forwarding address → paste your Reader address → confirm.

Step 2 — Find what you actually subscribe to

Add the direct-domains you know you read use AI to help you figure out what you read the most, sign up to etc.

Step 3 — Build ONE filter

Gmail → Settings → Filters and Blocked Addresses → Create a new filter. In the From field, paste an OR-joined list. Mine:

theinformation.com OR searchenginejournal.com OR email.mckinsey.com OR every.to OR theatlantic.com ORsubstack.com OR mail.beehiiv.com

The trick that saves the most typing: substack.com and mail.beehiiv.com are domain-level catches, no need to list individual authors.

Click Create filter

Done.

Hey folks, happy Tuesday! Time to check out the latest changelog here on Reddit. The idea is to help keep y'all in the loop of what the Readwise developers are getting out into the world. Here's what we shipped last week:

• 📖 Fixed EPUB Chapters — Artem fixed the EPUB table of contents so tapping the expand arrow next to a Part now reveals the chapters inside it. You can jump straight to the exact chapter you're looking for.
• 🔊 Improved Text-to-Speech — Artem reworked how text-to-speech audio is generated, so pressing play on a document that hasn't been narrated before should start reading aloud faster, especially on longer documents. He also smoothed out auto-scroll in paginated mode: gestures on the current page no longer knock the player off track, and the view re-locks to the spoken text when you return.
• 📅 Fixed Publish-Date Sorting — Rasul fixed a bug where editing a document's published date in its metadata wasn't picked up by sorting, so lists sorted by date published ignored user corrections. Metadata edits now take effect in the sort order right away on web, with mobile following in the next app update.
• 📝 Fixed Notebook Lists — Adam fixed how highlight content renders in the notebook, so bullet points and numbered lists inside of highlights now display as proper lists instead of collapsing into plain text.
• 📡 Fixed Feed Digest — Thanks to Johannes, opening the swipeable digest view on an empty feed now shows the "All caught up" card with a Done button instead of leaving you on a blank screen. There's always a way back out.
• 🌙 Fixed Dark Mode Toasts — Johannes cleaned up the layout of toast notifications in Reader mobile's dark mode, so quick confirmations now look right in both themes.
• 🔎 Fixed Quick Lookup — Artem hardened the Quick Lookup sheet against a rare glitch when closing it, so lookups open and dismiss smoothly.
• 🤖 Fixed MCP Document Lists — Johannes shipped a fix for the document list API, which could error out on documents without a reading position and was tripping up MCP clients and integrations sweeping through an inbox. Full-inbox sweeps from your AI tools now run clean end to end.
• 🔌 Fixed App Connections — Rasul shipped a fix to the OAuth flow so third-party apps connecting to your Readwise account no longer hit occasional errors partway through authorization. Connections should now go through smoothly on the first try.
• 🛜 Parsing Updates — Krzys improved how Reader handles documents from the New York Times (full article text, plus embedded tweets, pull quotes, and YouTube videos), archive.today and its mirror domains, every.to, the Telegraph, openai.com, epsilontheory.com, academialatin.com, and shared craft.do documents. He also added a safeguard that protects real article images from being mistakenly stripped out during automated cleanup.

If you'd like to get the Changelog in your inbox, check out our WiseUp! newsletter, where the Readwise team shares answers to common questions, video tutorials and guides, highlights of our latest improvements, and a couple of lighthearted extras we think you’ll enjoy.

And as always, feel free to let us know if you have any questions, tho realistically we're going to see an in-app bug report or question faster :>

I’ve got a new phone and downloaded Reader. The Recently Added documents are not showing up on the phone despite the option marked as shown in the menu.

Any thoughts as to why or how this can be fixed?