AI plugins now want the keys to your whole site. Here's what to check first π
I read this week's WordPress news and one thing caught my attention: AI plugins used to be a small chat box in the corner of your dashboard, and now some of them ask to run your entire site.
Two launches pushed this forward: Angie, the AI assistant from the Elementor team, added a "Super Admin Mode." Turn it on and it can read and change your files, edit your database (where all your posts and settings are stored), and run code on your site. A second project called SproutOS does something similar, letting many different AI tools connect to your site with the same deep access.
For a beginner, the appeal is real. You type "fix the spacing on my contact page" in plain words, and the agent does it. No code, no developer, no waiting.
Here's the catch. An assistant that can run code can also break the site, or get tricked into it by a sloppy instruction or a hacked plugin. The same power that fixes your page can wipe it. Real example: you ask the agent to "clean up unused plugins," it reads that too literally, and it removes the plugin running your contact forms. On a live site, that's lost leads before lunch.
Back up before you switch anything on πΎ
Before you turn on any AI mode that can edit files, make a full backup. Duplicator (the free version is fine) copies your whole site in a few clicks. If you host on Site Ground, the daily backup runs on its own and you can roll back to yesterday from the dashboard. I do this on client sites before any big change, AI or not.
The rule is simple. A change you can undo is a change you can survive.
Give the agent the smallest role that works π
If more than one person logs into your site, don't hand admin rights to everyone. Most people who write posts only need an Editor role (which can write and publish), not a full Administrator account (which can change everything). An AI agent runs with the powers of the account that switches it on, so a smaller account means less damage when something goes wrong.
Keep a record of what changed π
When an AI agent edits your site, you want to see what it touched. A security plugin like WP Activity Logs or Streams logs activity and watches for changes, so if a page looks different on Monday you can check the timeline instead of guessing. On a site with more than one admin, this stops being optional.
Test on a copy first π§ͺ
Don't let a brand-new AI mode loose on your live site as its first job. Most decent hosts give you a staging site, which is a private copy where you can try things safely. Run the agent there, watch what it does, then move the change over once you trust it.
One small homework item β
Joost de Valk, one of the people who helped build modern WordPress, just released a free, open checklist of what a healthy site should cover, security and speed included. It's a clean way to score your own site before you let any agent near it. Worth 20 minutes this weekend.
A short personal note. I've run WordPress sites since 2011, and the pattern repeats with every new shortcut. The thing that saves you an hour today can cost you a weekend if you skip the backup. AI agents are the newest version of that trade.
Have you tried any of the new AI agents on your own site yet? And if you did, did you back up first, or learn the hard way like the rest of us? π
Posted Jun 10, 2026, 4:35 PM UTC