AI Chat Inside WordPress Admin: Using GoBuildWP Chat

What AI chat inside WordPress admin needs first

GoBuildWP Chat is built on the AI Client that WordPress added in version 7.0, while the MCP server itself runs on older supported releases. On a site without that client, the Chat screen says WordPress 7 is required and stops there; every external MCP connection keeps working, because Chat failing never disables the server.

With WordPress 7 in place, Chat still needs an AI provider connected to WordPress itself, and that provider needs at least one model that supports native function calling, since Chat works by letting the model call GoBuildWP's abilities as tools. If no provider is connected, the screen offers a button, Set up a provider in WordPress Connectors, which opens the Connectors settings page where you add your provider and its API key. Reload GoBuildWP, Chat afterwards. If a provider is connected but the model list reports no native tool-call models available, the provider is there and none of its models can call tools; choose or enable one that can.

The first time you open Chat, a Before you start notice explains the billing model: every message and tool call is charged to your own provider key, not to a flat subscription. Select I understand to continue. That acknowledgement is recorded against your WordPress user, so each person who uses Chat sees it once.

• WordPress 7.0 or newer, so the AI Client is available
• A provider added under Settings, Connectors with a working API key
• A model that supports native function calling
• The billing notice read and accepted by each user

Running a conversation

Open GoBuildWP, Chat, in the Studio section of the GoBuildWP menu. Choose a model from Select model; the search box looks across every connected provider, and models can be kept in a favourites list. Type a request in the message box, or use voice input if your browser allows the microphone. Each conversation is saved with its history, and deleting one is permanent.

Images can be attached to a message: up to four per message, each 3 MB or smaller, in JPEG, PNG, WebP or GIF. That only works with a model that accepts image input; with any other model the attach control says image input is unavailable for it. An image you attach is sent to the provider with the message, so treat a screenshot of an admin screen as site data.

Keep requests small. Chat is suited to a quick change you can check immediately: retitle a draft, add a menu item, find the page that uses a shortcode. A long build that runs dozens of tool calls costs real money on an expensive model, and the screen itself suggests connecting an external client over MCP for heavier work, where a subscription you already pay for carries the cost.

The four approval buttons, and when to use each

Chat sorts every tool call before it runs. A call to an ability marked read-only runs without asking. Anything else waits: a write, a destructive call, code execution, a filesystem write, or an ability whose risk is not declared. A waiting call shows its arguments, with a control to expand them in full, and four buttons.

• Approve Once runs this one call. Use it by default.
• Deny Once refuses this call, and the refusal is returned to the model instead of a result.
• Allow This Tool approves the call and lets that same ability run without asking for the rest of this conversation only. Use it for a repeated, low-risk edit you have already checked once.
• Allow Everything turns on automatic approval for all of GoBuildWP Chat, not just the conversation in front of you, including PHP execution and file changes where the safety profile permits them. It asks for confirmation first, and after fifteen automatic steps it stops to ask whether to continue. Switch it off when the task is done.

Where Chat conversations are kept

Two copies of a conversation exist, and they are governed by different people. One is on your site: GoBuildWP stores each user's Chat sessions in its own table in the WordPress database, so they are included in your database backups and removed when the free plugin is deleted. Deleting a conversation from the Chat sidebar removes it from that table. The other copy is whatever the provider keeps of the prompts, attachments and tool results it received, under that provider's retention terms, which GoBuildWP cannot reach or delete.

Decide what belongs in a conversation with both copies in mind. A conversation about a page layout is ordinary site data; a pasted customer email or an exported order list is personal data that has now been sent to a third party and saved in the site's database as well.

Chat errors and what they mean

Most Chat failures name their layer in the message, and the fix depends on which layer it is.

• WordPress 7 required: the site's WordPress has no AI Client. Update WordPress, or use an external MCP client.
• Connect an AI provider to start: no provider is set up under Connectors, or the page was not reloaded after adding one.
• No native tool-call models available: the connected provider has no model that can call tools. Pick another model or provider.
• This chat model does not support image input: remove the image or switch to a model that accepts images.
• Each image attachment must be 3 MB or smaller, or only JPEG, PNG, WebP and GIF are supported: resize or convert the file.
• Tool execution was denied by the user: someone selected Deny Once. Nothing ran.
• A call refused after you approved it: GoBuildWP's server checks still apply. Read the refusal; the safety profile, the WordPress user's capabilities, the write rate limit or a Pro approval hold decided it, not Chat.
• A provider error such as a quota or authentication message: it came from the provider. Check the key and plan with that provider.