I built an Obsidian plugin that reads your web clipping backlog for you

I clip a lot of articles into Obsidian with the Web Clipper and then never read them. After a few weeks I had 40-something unread clippings in a folder and no idea which ones still mattered. The folder just sat there making me feel guilty.

I looked for something that could read the whole pile and tell me what was in there without me opening every note one by one. Everything I found worked on a single article at clip time, not on the backlog that had already piled up. So I built it.

It reads your clippings and writes a single Reading Synthesis note: a short summary and the key claims per article, cross-article themes that show where sources agree and disagree, a weekly digest of what you saved recently, and a list that flags clippings sitting untouched for months so you can decide whether to read them or drop them.

It runs on your own API key. No server in the middle, no database, nothing leaves your vault except the call to whichever model you pick. Works with Anthropic, OpenAI, or any OpenAI-compatible endpoint like OpenRouter.

It's the fourth Obsidian plugin I've shipped this way, all built with AI assistance since I have no coding background. Free tier covers a few syncs, and there's a one-time Pro license for unlimited use.

Plugin (Obsidian Community directory): https://community.obsidian.md/plugins/reading-inbox-synthesizer
GitHub: https://github.com/ibrh96-prog/obsidian-reading-inbox-synthesizer
Pro: https://ibrh96.gumroad.com/l/yeulsi

How do you deal with your own read-it-later backlog? I'm curious whether anyone actually clears theirs or if we all just keep clipping.