Bambu Lab disputes AGPL claims as OrcaSlicer fork fight intensifies

If your slicer talks to a printer cloud the wrong way, the fight stops being abstract fast. That is exactly where Bambu Lab and parts of the OrcaSlicer community landed as the dispute over Bambu Studio, AGPL obligations, and fork rights hardened into a broader question about who controls the 3D-printing workflow once the file leaves the desktop.

Bambu Lab said it fully supported the open-source community, respected the AGPL license, and had no issue with modifying, forking, or redistributing Bambu Studio code, including OrcaSlicer and other projects. But the company said the current dispute was not about fork rights. Its complaint centered on an OrcaSlicer fork that it said impersonated the official Bambu Studio client when connecting to Bambu cloud services, using a hardcoded version number and presenting itself as Bambu Studio.

That argument matters because Bambu Studio’s own GitHub README says the slicer is licensed under GNU AGPL v3. It also says the bambu networking plugin is based on non-free libraries, is optional, and adds extended networking functionality, while SD-card printing remains available without the plugin. In practice, that means Bambu users are already dealing with a split stack: one path for local slicing and SD-card output, another for cloud-connected features that shape day-to-day convenience, remote control, and workflow speed.

The pressure point sharpened further when the Software Freedom Conservancy said on May 18, 2026 that Bambu Lab had ongoing AGPLv3 violations and that it had started a project to recover the missing source code for Bambu Studio. The group specifically thanked Paweł Jarczak, the developer whose OrcaSlicer fork helped trigger the escalation. Bambu Lab also asked for Jarczak’s repository to be removed from GitHub, pushing the conflict beyond a routine licensing argument and into a public fight over what a manufacturer can police when its software touches community forks.

For users, the stakes are concrete. OrcaSlicer users, Bambu Studio users, and plugin developers are not just watching a license quarrel unfold. They are watching whether updates will stay portable across forks, whether experimental features can survive if cloud access gets tighter, and whether community support will keep flowing into multicolor and networked workflows that have made Bambu one of the most influential names in desktop printing. If the dispute chills fork development, the ecosystem gets narrower. If it forces clearer compliance, the message to the rest of the stack is sharper: build on open source, but give the community code it can actually keep using.