WordPress Developers Oppose AI Feature Integration into Core

Image credit: Search Engine Journal

WordPress developers are largely opposing a proposal to integrate a new AI-focused Knowledge Custom Post Type directly into WordPress Core, citing concerns over software bloat and misplaced priorities.

The resistance marks the second time in WordPress version 7 that a proposed core feature has faced significant developer questioning, following previous debates over Real-Time Collaboration.

A proposal circulated in February 2026 suggested bringing the “Knowledge Custom Post Type” into WordPress Core. The feature, currently an experimental component of the Gutenberg plugin, aims to centralize guidelines and foundational context for human users, AI agents, tools, and plugins, according to the public proposal.

Its intended function is to store site-specific information such as goals, tone, image styles, and block rules. However, developers have overwhelmingly argued that the feature should remain a plugin rather than becoming a permanent part of the core software.

Critics contended that the proposed integration adds unnecessary bloat to WordPress Core and primarily serves AI applications rather than directly benefiting human users. Namith Jawahar, a developer, highlighted the discrepancy between the public proposal’s stated purpose for both humans and AI, and the GitHub repository’s positioning of the feature as purely for AI.

Developers also cited a perceived lack of necessity for the feature within the core system, suggesting it does not address more pressing needs. Aaron Jorbin, another developer, emphasized that other features, such as native multilingual support, should take precedence in development efforts.

Concerns were also raised that the Knowledge Custom Post Type primarily benefits Automattic’s enterprise users, including those utilizing WooCommerce, rather than the broader WordPress community. mrwweb, a prominent voice in the developer community, noted that the feature’s utility for general users appeared limited.

The strong pushback underscores a perceived disconnect between official proposals for WordPress Core and the priorities articulated by many developers.

Source: Search Engine Journal