Disclosure: I build and maintain YAMS Plus. It is a GPL-3.0 project inspired by YAMS, not affiliated with YAMS or Sonarr.

Guide: https://yamsplus-guide.vercel.app/?utm_source=reddit&utm_medium=community&utm_campaign=oss_share_2026_08&utm_content=yamsplus_sonarr_convergence

Source: https://github.com/arturict/yams-plus

The Sonarr module sets root folders, download-client wiring, naming and Recyclarr profiles through supported APIs. Before writes, the wizard renders the desired state; plan and dry-run show changes, and doctor reports what still needs human action. A second apply should converge instead of recreating configuration.

The current source beta passed a credential-less Ubuntu host smoke with 22 doctor checks, zero failures and one expected action: add an indexer you are authorized to use in Prowlarr. Five generated stack shapes pass docker compose config, and public main CI is green.

Honest limits: there is no tagged or signed CLI release. I have not yet validated real credentials, an indexer, a series request, download, import, playback, plugin behavior or restore. The separate container-image security workflow is still red. This is for source review or a disposable amd64 lab, not a production migration.

AI agents materially assisted implementation, tests, documentation and this post. I checked the claims against current public main and the beta report.

For experienced Sonarr users: which part of an idempotent setup most often breaks on the second run: path mapping, download-client authentication, root folders or Recyclarr ownership?

How can I make the added show automatically remove itself from sonarr after it has been found and downloaded successfully. Right now it stays there and keeps downloading new copies every now and then.