errorHandle for WordPress

errorHandle is a free WordPress plugin. Describe the result you want in
plain English; it works out how, shows you exactly what will change, and waits
for your approval.

What it does

You type what you want. errorHandle turns that into a plan —
a specific list of operations, with the exact pages, posts or orders it will
touch. You read the plan. You can run it as a simulation that changes nothing.
Then you approve it, or you do not.

Nothing happens to your site until you say so, and most of it can be undone
afterwards from the History screen.

How it is built

The important design decision is this: AI is used only when you are
authoring something, never when it runs.

An AI model reads your request and produces a structured plan. That plan is
validated against a fixed list of operations the plugin actually supports —
anything outside that list is rejected before it runs. The work itself is then
carried out by ordinary, deterministic PHP.

So an automation you build today does not call an AI service when it fires,
however many times it fires. It does the same thing every time, and it costs
nothing to run.

What it will not do

Worth stating as plainly as the features, because it is a deliberate
boundary rather than a gap:

It does not store or run code. No CSS, no JavaScript, no
PHP, no raw HTML, no tracking snippets, no embeds. There is no capability for
it and no setting that enables one. For styling, use the Customizer or your
theme; for tracking and embeds, use a plugin built for that.
It does not touch your server. Nginx, Apache,
.htaccess, php.ini, DNS and file permissions are all
outside WordPress, and requests about them are declined with an explanation of
who can help.
It does not phone home. No telemetry, no licence check, no
usage reporting. On a fresh install it makes no external request at all until
you choose an AI option.

Choosing how AI reaches your site

You pick one, and the plugin asks on first run rather than assuming. The
default answer is none.

The offline planner

Runs on your own server and contacts nothing. It recognises common requests
by pattern rather than by understanding them, so it is less capable than a
model — but it is free, private, and always available.

WordPress AI — recommended on WordPress 7.0 and later

WordPress 7.0 added a built-in AI client. You add your API key to an AI
provider plugin once, and every plugin on the site can use it.
errorHandle stores no key at all on this path, which is strictly better than
holding one itself.

Your own provider key

Supported for Anthropic, OpenAI and Google Gemini, and the route to use on
WordPress 6.9, which has no AI client. Requests go directly from your server to
your provider; your key is encrypted in your own database, and errorHandle is
not in the path and receives nothing. Your provider bills you at their rates.

errorHandle hosted AI

We pay for a limited number of AI generations so you can try the plugin
without an API key: three commands immediately, seven more once
you confirm an email address, ten in total for the lifetime of the
site. Confirming your email does not reset the count.

When the ten are used, nothing you have already built stops
working. Automations, scheduling, history and undo never used AI. To
carry on creating with AI, connect your own provider — which we do not meter or
limit — or use the offline planner.

This is optional, opt-in, and asked for with a button rather than a
pre-ticked box. What it sends and what it keeps is set out in full in the
privacy policy.

What it can do

Content: create, update and search-and-replace across posts, pages and
custom post types; change publication status. Communication: send email.
Integration: fetch a URL, post to one, send a webhook. WooCommerce, when it is
active: order notes, order meta and order status. Plus anything another plugin
registers through the WordPress Abilities API.

Automations combine these: when a WooCommerce order over £1,000 comes
in, email the administrator with the customer name and order total. Nine
triggers are available, including a recurring schedule and an incoming webhook.
Automations are saved switched off until you activate them.

Safety

Every plan is previewed before it runs, with the specific items named.
Test mode simulates the whole plan, changing nothing and sending
nothing.
High-risk changes require you to type APPLY, so one cannot be
approved by a stray click.
After applying, the result is verified independently and reported as done,
partly applied, or failed — never as a success it cannot confirm.
Reversible changes can be undone from History, individually or as a
whole.
Outbound requests refuse private, loopback, link-local and cloud-metadata
addresses, so an automation cannot be pointed at your internal network.
Provider API keys are encrypted at rest and redacted from logs.

Requirements

WordPress 6.9 or later
PHP 8.1 or later
An administrator account — every screen and every operation requires the
manage_options capability

Licence and source

errorHandle is free software under the
GNU General Public License,
version 2 or later. You may use, study, modify and redistribute it,
whether or not you ever use our hosted service.

Support

Email [email protected].
Please say what you asked errorHandle to do and what it did instead; the
History screen records both.