Link: https://github.com/crocodilestick/Calibre-Web-Automated/releases/tag/v4.0.7

CWA is an eBook manager, and it is popular in the selfhosted book space. Please see the changelog link for the full summary, it is well organized and so I didn't copy it here.

If this project is closely based on Calibre it requires the [AIP] prefix.

Edit: Definitely needs it, Claude Code is in the contributor list.

Nice, I've been using this for a year or two now and it's become my main ereader server after a lot of time trying to land on one.

Will need to check if there's finally a way to sync read progress between different versions of the same library item (i.e. PDF & epub). One of my use cases is for storing magazines and being able to read the epub on my phone, but the full PDF on my tablet and have the progress sync properly is a personal holy grail

FWIW Claude seems to be involved in 9 commits

The maintainer alone has made nearly 900 and there are about 100 other contributors

This isn't a vibe coded project, it's been running for 2-3 years

OP did not make it and can't do a disclosure, its not required.

Noting it is because Claude is involved is a nice-to-have, not a requirement.

I don't have a use case, so I can't test. This looks promising, though:

Shared Progress Across Copies: Progress is now stored against the Calibre book rather than the file checksum, so different copies/formats of the same book on different devices stay in sync. (PR #1225)

!!!

Oh that's made my week and we're only about 2 hours in to it, will update my server test that out in the morning

CWA is the example I always point to as to why vibe coded software doesn't make sense for broad use. CWA updates are slow (but detailed) which inspires many folks to "fork" it with vibe coded apps, but since CWAs last update in Feb, several vibe coded "competitor" projects have risen and fallen.

I'm starting to say vibe code is write only.

Like they used to say about Perl, indistinguishable from line noise.

Basically unmaintainable without super strict coding conventions, submitters taking personal responsibility, a strong, well thought out overarching architecture, and most importantly, someone with a great knowledge of the project to approve merges. Vibe coded forks to add one or two features have none of that.

This is why GitHub is littered with slop projects that haven't been touched since they were made. This is why an ungodly amount of technical debt is accruing as managers with a hard on for lines of code or 'features' force devs to unwisely use AI coding tools all the time. There will be a reckoning, and it's not far off.

as an ignoramus what's the go with this?

I use Calibre with my ebooks on an SSD and just upload via USB to my Kobo Colour

I don't have many PDFs there be case they suck using them on my Kobo and I don't have a tablet or anything bigger screened to read them on besides my desktop (yet)

Calibre-web and calibre can share a library directory. You can edit the .kobo/kobo/Kobo ereader.conf file to wirelessly sync to calibre-web instead of kobo.com (while still using kobo.com to buy new ebooks)

That's a great way of putting it. I think in the future it will be helpful for when folks have some personal specific need. But for anything approaching even the simplest infrastructure it just doesn't work.

Small nitpick- this project isn't Calibe-Web, it's a fork with extra features; the idea being that you don't also need to be running Calibre.

I tried to give this a go and migrate my calibre-web data over, but CWA refuses to see any of my media files, it sees the all my config, but not any media.

Its a fork of Calibre-Web not Calibre

I'll have to check this out, I use Kobo sync extensively.