🚨 WordPress 7.0 & AI: What You Need to Know 🚨
WP 7.0 is bringing native AI write capabilities this Thursday (April 9). While it's an exciting leap forward, here are the 5 major safety risks you need to watch out for before giving AI the keys to your site:
🔹 Native AI Access is Here: WP 7.0 introduces an official MCP Adapter, allowing AI agents (like Cursor and Claude) to directly read and write to your site without clunky, bolted-on plugins.
🔹 Reckless Automation: AI is fast, confident, and incapable of second thoughts. A simple prompt to "update the About page" could accidentally rewrite other pages or replace images with placeholders without you noticing for weeks.
🔹 Dangerous Scope Creep: In production, AI is usually right about what needs changing, but it’s almost always wrong about how much to change, leading to massive unintended edits.
🔹 Page Builder Chaos: While native Gutenberg blocks might survive, letting generic AI tools touch complex layouts built with Elementor, Divi, Bricks, or WPBakery will turn them into broken HTML soup.
🔹 The Human Review Trap: Just like code reviews, manual oversight degrades over time. You won’t catch every AI error in real time, meaning we urgently need to build structural safety into these new workflows.
#Blog
WP 7.0 is bringing native AI write capabilities this Thursday (April 9). While it's an exciting leap forward, here are the 5 major safety risks you need to watch out for before giving AI the keys to your site:
🔹 Native AI Access is Here: WP 7.0 introduces an official MCP Adapter, allowing AI agents (like Cursor and Claude) to directly read and write to your site without clunky, bolted-on plugins.
🔹 Reckless Automation: AI is fast, confident, and incapable of second thoughts. A simple prompt to "update the About page" could accidentally rewrite other pages or replace images with placeholders without you noticing for weeks.
🔹 Dangerous Scope Creep: In production, AI is usually right about what needs changing, but it’s almost always wrong about how much to change, leading to massive unintended edits.
🔹 Page Builder Chaos: While native Gutenberg blocks might survive, letting generic AI tools touch complex layouts built with Elementor, Divi, Bricks, or WPBakery will turn them into broken HTML soup.
🔹 The Human Review Trap: Just like code reviews, manual oversight degrades over time. You won’t catch every AI error in real time, meaning we urgently need to build structural safety into these new workflows.
#Blog
👍2
WordPress is finally getting a "who's online" feature and honestly it's about time
1. The problem – In multi-author WordPress sites, editors often unknowingly work on the same post simultaneously or overwrite each other’s changes because there’s no real-time awareness of who is editing what.
2. WordPress has a post locking system, but it only warns you after you’ve already opened a post, by which time you may have already started making conflicting edits.
3. A feature plugin called Presence API was published to the WordPress.org plugin directory in April (not yet in core).
4. The plugin introduces a “Who’s Online” dashboard widget, an avatar stack in the admin bar, an Editors column in the post list (shows active editors before you open a post), and an “Online” filter on the Users list.
5. It uses the existing Heartbeat API and stores presence data in a dedicated table with a 60‑second TTL. A separate table was necessary because storing ephemeral data in shared cache tables was wiping site‑wide cache on every heartbeat tick (discovered during WordPress 7.0 development).
6. The plugin is still experimental (not recommended for production sites). You can try it via a Playground demo, and the core team is actively collecting feedback in the #feature-presence-api Slack channel.
#Blog
1. The problem – In multi-author WordPress sites, editors often unknowingly work on the same post simultaneously or overwrite each other’s changes because there’s no real-time awareness of who is editing what.
2. WordPress has a post locking system, but it only warns you after you’ve already opened a post, by which time you may have already started making conflicting edits.
3. A feature plugin called Presence API was published to the WordPress.org plugin directory in April (not yet in core).
4. The plugin introduces a “Who’s Online” dashboard widget, an avatar stack in the admin bar, an Editors column in the post list (shows active editors before you open a post), and an “Online” filter on the Users list.
5. It uses the existing Heartbeat API and stores presence data in a dedicated table with a 60‑second TTL. A separate table was necessary because storing ephemeral data in shared cache tables was wiping site‑wide cache on every heartbeat tick (discovered during WordPress 7.0 development).
6. The plugin is still experimental (not recommended for production sites). You can try it via a Playground demo, and the core team is actively collecting feedback in the #feature-presence-api Slack channel.
#Blog
👍4
WordPress: The Operating System of the Agentic Web — AUTOMATTIC
1. WordPress’s 43% web share and 90,000+ plugins give it an integration surface no proprietary platform can replicate, making it the natural foundation for the agentic web.
2. Transparent, peer-reviewed code allows AI agents to learn securely from real-world patterns, unlike closed platforms where they work “in the dark.”
3. The Model Context Protocol (MCP) transforms WordPress from a passive CMS into an AI-operable platform, enabling agents to read, write, and manage sites via natural conversation – with human approval.
4. Humans shift from manual execution to strategic direction, orchestrating teams of AI agents for tasks like content audits, SEO, and social media campaigns – cutting process time by up to 75%.
5. Developers can build and sell specialized, subscription-based AI “Site Delegates” (e.g., continuous SEO, security compliance) that live natively inside the WordPress ecosystem.
6. Success requires standardizing messy data models, modernising the developer experience for machine readability, and resolving GPL licensing ambiguities around AI-generated code.
7. The vision depends heavily on Automattic’s services, potentially centralising the agentic layer; meanwhile, if AI agents consume sites as interchangeable data wells, unique brand identity may erode.
#Blog
1. WordPress’s 43% web share and 90,000+ plugins give it an integration surface no proprietary platform can replicate, making it the natural foundation for the agentic web.
2. Transparent, peer-reviewed code allows AI agents to learn securely from real-world patterns, unlike closed platforms where they work “in the dark.”
3. The Model Context Protocol (MCP) transforms WordPress from a passive CMS into an AI-operable platform, enabling agents to read, write, and manage sites via natural conversation – with human approval.
4. Humans shift from manual execution to strategic direction, orchestrating teams of AI agents for tasks like content audits, SEO, and social media campaigns – cutting process time by up to 75%.
5. Developers can build and sell specialized, subscription-based AI “Site Delegates” (e.g., continuous SEO, security compliance) that live natively inside the WordPress ecosystem.
6. Success requires standardizing messy data models, modernising the developer experience for machine readability, and resolving GPL licensing ambiguities around AI-generated code.
7. The vision depends heavily on Automattic’s services, potentially centralising the agentic layer; meanwhile, if AI agents consume sites as interchangeable data wells, unique brand identity may erode.
#Blog
👍3