LibreOffice's No-AI Stance Faces Scrutiny Over LLM-Assisted Code
The Document Foundation maintains an AI-free product while community contributors utilize LLM coding assistants.
1Core Development Versus Community
The Document Foundation asserts that LibreOffice core developers avoid using LLMs, maintaining an AI-free codebase for the product. However, community contributors operate under different rules. Recent commits, including font size adjustments and screenshot dialog updates, explicitly acknowledge the use of Claude and GitHub Copilot, creating a visible tension between policy and practice.
2Specific Instances of LLM Usage
Three specific commits this year highlight the integration of AI-generated code. In April, two patches for Calc cell styles and paragraph font sizes credited Claude for identifying fixes. By September, the addition of a copy image button utilized GitHub Copilot to generate the BitmapTransferable class, while manual methods incorporated LLM-assisted code completion.
3The Strategic Marketing of AI-Free
The Document Foundation positions the absence of built-in AI as a core feature and a distinct selling point for LibreOffice. This stance serves as a strategic differentiator, particularly against former partner Collabora, which heavily integrated AI features into its CODE suite. TDF officially declared the software AI-free in a September blog post.
4Operational Growth Amidst Policy Debates
Despite the ongoing debate regarding AI, LibreOffice continues to see significant traction. The foundation announced 9.4 million downloads over an eight-week period ending in October. While TDF acknowledges that the specific drivers of this growth remain difficult to determine, the project maintains its status as a leading open-source office suite globally.
5The Debian-Style Pragmatic Approach
TDF’s internal policy resembles the Debian approach, where LLM usage is permitted for contributors provided there is full disclosure and rigorous human review. The foundation emphasizes that they do not explicitly list prohibited tools but require authors to understand their own code. Students, however, face a strict prohibition against using LLM coding assistants.
6Contradiction in Public Messaging
The admission that community code contains LLM-generated segments has sparked criticism from users who feel the public no-AI marketing is misleading. Developer Federico Schonborn compared the situation to a bakery claiming no asbestos in frosting while ignoring it in the filling. This highlights the gap between product-level features and development-level practices.
7Clarifying the AI Policy Scope
Spokesman Italo Vignoli clarified that public statements regarding LibreOffice 26.8 refer exclusively to end-user features, not the underlying development process. The foundation maintains that there is no departure from their stated goals. They continue to review all community submissions to ensure code quality remains high regardless of the tools used by authors.
8Future of Open Source Development
The LibreOffice situation reflects a broader industry challenge: balancing the pragmatic benefits of AI coding assistants with the ideological commitment to human-authored open-source software. As major projects struggle to define boundaries, the requirement for transparency and human oversight becomes the primary mechanism for maintaining trust within the global developer community moving forward.