WordPress Core Faces Debate Over Adding AI Feature
Merge the wp_knowledge custom post type and Guidelines feature into WordPress core for 7.1.
Implement the wp_knowledge custom post type and Guidelines feature in your sites, register any needed types via wp_knowledge_types filter.
Summary
WordPress core developers are currently debating whether an artificial‑intelligence feature should be incorporated into the platform’s official codebase. A recent merge proposal, titled “Guidelines built on Knowledge,” outlines a framework for how AI tools could be integrated while maintaining the core’s stability, security, and quality standards. The proposal calls for clear documentation, testing protocols, and a review process that would involve the broader WordPress community.
The controversy stems from concerns that AI‑generated code might introduce bugs, reduce readability, or create maintenance challenges. Some developers argue that the feature belongs in a separate plugin rather than the core, citing the need for modularity and the risk of bloating the core with experimental technology. Others see the inclusion as a way to keep WordPress competitive and to provide users with powerful new capabilities directly out of the box.
The discussion has attracted attention from both the open‑source community and industry observers. While no specific quotes or numbers were provided in the available sources, the debate highlights broader questions about the role of AI in software development, the balance between innovation and reliability, and how large communities govern the evolution of shared code. The outcome of the merge proposal will likely influence how WordPress handles future AI‑related features and could set a precedent for other open‑source projects grappling with similar issues.
Key changes
- wp_knowledge CPT added with native revisions.
- wp_knowledge_type taxonomy and registration filter introduced.
- Built‑in types guideline, memory, and note defined.
- /wp/v2/knowledge REST routes for CRUD operations.
- Guidelines Settings page provides per‑scope guidelines and registry route.
- Capability namespace *_knowledge_item enforces access control.
- Plugin types can register via wp_knowledge_types filter.
- Merge replaces fragmented plugin‑specific storage models.