www.it-connect.fr
Jellyfin Faces Three Major Departures Amid Burnout and AI Tensions
In less than a week, Jellyfin lost its project lead, a long-standing member of its Core team, and one of its co-founders. Joshua Boniface cites severe burnout, Anthony Lavado personal priorities, and Andrew Rabert a negative and increasingly restrictive climate around his work on the desktop client. The most popular open source media server competing with Plex is now under strain. Here’s what we know.
Three departures in one week: Jellyfin loses its leadership
The first to leave is Andrew Rabert. On July 17, 2026, he opened a ticket titled "Rename the app" on his GitHub repository, with just one sentence of explanation: "This is no longer an official project of the Jellyfin organization. It needs a new name and a new identity." The desktop client he had been developing for several months has now moved out of the Jellyfin organization and is called jellium-desktop instead. Andrew Rabert also points to a broadly negative attitude that has become increasingly heavy and restrictive.
This desktop client was not a side project. In the blog post titled "State of the Fin" published on May 24, 2026, Rabert himself detailed the complete rewrite of Jellyfin Desktop: dropping Qt and QtWebEngine in favor of CEF (Chromium Embedded Framework), along with other improvements such as native HDR support on Wayland, macOS, and Windows. Two months later, this work will continue outside the main project.
That is not all. Three days later, Joshua Boniface published a message on the project’s official forum. He announced his departure as project lead as well as Anthony Lavado’s departure from the Core team, effective July 19, 2026. Joshua Boniface had been Jellyfin’s project lead since the Emby fork was created in late 2018.
To explain his decision, he cites burnout: "I simply could no longer provide the effort (mental or time) that the role required, and I was therefore no longer performing my duties at an acceptable level, while dealing with severe burnout and risks to my mental health. It was time for me to step away."
He also dismisses the risk of an impending hostile fork and says the transition happened under good conditions. He also states that "Jellyfin will continue for a long time, just not with me at the helm". In his message posted on the Jellyfin forum, he also reflects on the application’s success: "So here we are seven and a half years later: it is now the number one free media server, a truly viable alternative to Plex for millions of server administrators and probably ten times as many home users, and we have completely outgrown our original project. We have proven that free software works and that it meets a real demand."
AI-generated code, the backdrop to the unease
The tensions did not start this month. In the May 24, 2026 "State of the Fin" article, signed by the Jellyfin team, artificial intelligence was also mentioned. Jellyfin also announced the publication of a LLM/AI policy: using AI is not forbidden in code contributions, but the contributor must understand what their tool produces, and any message posted on an issue or pull request must be written by a human. No one is supposed to act as a simple relay between an AI and the maintainers.
The second AI-related section, titled "Burnout / Remember the Person", was even more explicit. I’ll let the following speak for itself: "The increase in support requests, combined with AI code submissions, has led to burnout at various levels of the development and administration team. Abuse from users when something does not work or a change is not accepted only increases the loss of motivation. This has already resulted in delays to client and server improvements."
Ultimately, this issue goes far beyond Jellyfin. Artificial intelligence is especially draining for open source project maintainers. Jellyfin is one example, there are certainly others, and unfortunately there will be more. For volunteer-driven free software projects, the flood of AI-generated contributions creates a triage workload that did not exist three years ago... which is prompting a response. The project Debian has also locked down its infrastructure against the appetite of AI bots, while criticizing AI-generated code.
Jellyfin should continue on its path because there is a solid team and it is a well-established project, despite the departure of three important people. Development of version 12.0 is currently ongoing: Jellyfin has more than 1,400 contributors on GitHub.
Timing-wise, though, this is unfortunate. Since July 1, 2026, the Lifetime Plex Pass has gone from $249.99 to $749.99. Plex is tripling down! A massive increase that will mechanically push some users toward a free and open source alternative. Jellyfin is the most obvious choice, even if Emby is also an option. When I say the timing is unfortunate, it’s because Jellyfin is seeing its governance shaken up right when its user base has the strongest reason to grow.
If you want to explore the solution, check out our tutorial for deploying Jellyfin on a Synology NAS.
