WordPress Core

WordPress Core gives your AI real control of the site itself, not just the page builder. It creates pages and posts, registers custom post types and taxonomies, builds menus, uploads media, changes site settings, and reads its own error logs when something breaks. It is always on.

What it does

This integration covers the parts of WordPress that sit underneath any builder. Ask your AI to handle the structural work and it reaches for these capabilities:

• Pages: create, edit, and delete standard WordPress pages.
• Posts: write and manage blog posts.
• Custom post types: register your own content types (for example Treatments, Properties, Projects).
• Taxonomies and terms: add categories and tags of your own, then attach and fill them.
• Menus: build navigation menus and assign them to theme locations.
• Media: upload images and files, including straight from a URL with alt text.
• Site settings: change core options, including setting the static homepage.
• Diagnostics: probe a page's live URL to see what actually rendered, and read PHP error logs when a page fails.

When your AI registers a custom post type or a taxonomy, it writes that registration into a persistent runtime registry that re-registers on every load. That detail matters: it means archives keep working and do not start returning a 404 after a cache clear or a deploy.

How it works

Your AI does not guess at the current state of your site. It reads site info first to learn what is already installed and configured, then uses a dedicated typed tool for every write. After each write it verifies by reading the result back, so a tool call that returned success is never treated as proof the change actually landed.

1. Read site info to learn what post types, taxonomies, menus, and pages exist.
2. Use the dedicated typed tool for the specific write (create a page, register a post type, set a menu).
3. Read the result back to confirm the change is really there.

This is part of the wider render verification approach: your AI checks its own work instead of assuming it. For pages with visible output, that includes a live HTTP check of what rendered.

Trigger the AI

You drive all of this in plain English. Paste any of these to your AI:

• "Create a new About page, set it as the site homepage, and add it to the main menu."
• "Register a 'Treatments' custom post type with an archive, plus a 'Treatment Category' taxonomy, and flush permalinks."
• "The homepage is showing a 500 error, check what's wrong and read the error log."
• "Upload this logo from [URL] with alt text 'Acme logo'."

Requirements

Nothing beyond a working WordPress install. You need WordPress 6.5+ on PHP 8.1+, the same baseline BuildPress requires everywhere. This integration is always on, so there is no toggle to enable and no extra plugin to install.