A Picture of Unity
To the outside world, the Krita project looks more unified than ever. As a free, powerful alternative to paid software like Adobe Photoshop, it has cultivated a fiercely loyal following of artists and illustrators. The Krita Foundation has a long history
of engaging with its community to define its vision, moving from a Photoshop-like clone to a dedicated tool for creating art from scratch. Their 2026 roadmap, announced in March, lays out a clear and ambitious path, with developers planning major initiatives like a refreshed user interface for tablets, a new, faster file format to make saving seamless, and enhanced color management capabilities. These plans were decided upon in developer meetings, suggesting a collaborative and consensus-driven process aimed at keeping the software competitive and user-friendly. This apparent harmony, however, masks a deeper, more philosophical debate.
The AI in the Codebase
The core of the disagreement isn't about a new brush engine or a user-facing feature. Instead, it’s about how Krita itself gets made. The debate centers on whether the project's developers should be allowed to use AI-powered coding assistants—tools like GitHub Copilot that suggest lines of code—to build and maintain the application. According to an official statement from the developer community, the team could not find a consensus on the issue. This isn't a simple argument over efficiency. It strikes at the heart of the project's open-source ethos and its relationship with a user base that is often wary of AI's role in the creative space. The conflict isn't about adding AI image generation into Krita; it's about whether AI should have a hand in writing the DNA of the program artists use.
A Moratorium on the Future
Unable to find common ground, the Krita team made a decisive move: they placed a temporary ban, or moratorium, on using AI tools for Krita development until at least October 2026. This decision to press pause was driven by several key concerns. First, they acknowledged that allowing AI into their development process right now could trigger a "furious" backlash from users and financial supporters, many of whom value Krita as a human-centric creative tool. Second, Krita is part of the larger KDE software community, which has not yet established its own policy on AI use; the Krita team wanted to avoid a situation where their contributions might later conflict with broader KDE rules. Finally, they recognized that the technology, and public acceptance of it, is in constant flux. The moratorium gives them time to see how the landscape of AI ethics, environmental impact, and legal precedents evolves.
A Microcosm of a Larger Tech Debate
This internal struggle is the "real reason" for the disagreement, and it's not unique to Krita. The project has become a small-scale case study for a massive debate happening across the entire technology and creative world. On one side, proponents see AI coding assistants as the next logical step in developer productivity, a tool that can accelerate bug fixes and feature implementation. On the other side, skeptics and critics raise profound questions about the ethics of training data, the potential for deskilling developers, and the philosophical implications of automating the craft of software engineering. For an open-source project that runs on the passion of its contributors and the trust of its community, these are not abstract questions. The disagreement among Krita's maintainers reveals that the project's future direction is not just about what features to build, but about the principles that guide how they are built.
