Connecting an AI app to a live store is a bit like giving a new colleague a key. The risk is less about the colleague than about how much the key opens, how long it works and what you can do when something goes wrong. The settings below take a few minutes and decide most of the outcome. They apply to every AI app you connect with PowerWP AI.
Start with a Read-only connection
When you create a connection in PowerWP AI › Connections, you choose what the app may do. There are four levels, or you choose Custom and pick single permissions. The first level, Read-only diagnostics, is the one to pick when you are new to this. The app can look at settings, logs, health and orders. It can change nothing.
| Preset | What the app can do | Typical use |
|---|---|---|
| Read-only diagnostics | Look at settings, logs, health and orders. | First sessions, check-ups and reports. |
| Content manager | Also edit pages, posts, products, orders and media. | Texts, products and SEO fields. |
| Developer | Also change settings, plugins, themes, files and the database, and make backups. | Updates, fixes and backups. |
| Full access | Also manage users and see secrets such as API keys. | Only the jobs that need them. |
The Free plan allows only Read-only, so it is a safe place to start.
Stay on Read-only until you have seen how your AI app works: what it asks for, how it explains itself, whether its answers are right. You can change a connection later, so widening it is a quick step when you need it. Content manager is the usual next level, for texts and products. Developer is for plugin, theme and backup work.
One connection per app and per person
A connection is one AI app, with its own key or signed in with your WordPress account. If you use Claude Code on a laptop and Cursor on a desktop, make two. If a colleague or freelancer works on the store, they get their own. Your plan sets how many AI connections a site can have: one on Free (read-only) and on Solo, three on Team, ten on Crew. Revoked and expired ones don’t count, and connections you already have are never revoked because of the limit. If a site is over it, the oldest keep their permissions and the newer ones can only read.
This gives you two things. The activity log shows which connection did what, so you can tell your own work from someone else’s. And you can stop one without disturbing the others: revoke a connection and it loses access at once.
A key is shown once, and PowerWP keeps only a fingerprint of it. If you lose it, revoke the old connection, then create a new one. Treat the key like a password. Keep config files that contain it out of shared folders and repositories, and send the connect message only to your own AI app, in your own account.
Apps that sign in, such as Claude and ChatGPT, have no key to copy. You approve each one on a screen that names the app and shows who is signed in, you choose the preset, and you can revoke it in PowerWP AI › Connections.
Write your rules down once
Under PowerWP AI › Memory, add rules such as “Ask before changing prices” or “Never edit the checkout page”. Every connected app sees them. When a request conflicts with a rule, the app says so and asks before going ahead. Your apps can propose rules and facts, and you approve them. Passwords, keys and card numbers are refused.
Set an expiry and an IP allow-list
Under More options you can choose how long a key lasts: 7 days, 30 days, 90 days, a year or never. The default is 90 days. An expired key stops working by itself, so a key forgotten on an old laptop doesn’t stay valid forever. Use a short expiry for freelancers and trials, a longer one for your own daily tools.
An IP allow-list limits a connection to the addresses you list. Requests from anywhere else are refused. It suits a fixed address such as an office. At home your address may change, and a strict list then locks you out until you update it, so if an app that worked suddenly gets a 403 error, check the list first. Requests must also use HTTPS, so your site needs a valid certificate.
Create a checkpoint before bulk work
Before anything that touches many items, such as descriptions for 40 products, a price change or a round of plugin updates, ask your AI app to create a checkpoint. It is a marker in the change record, made with the checkpoint_create tool. If the result isn’t what you wanted, changes_rollback rolls back what was recorded after the marker in one step, instead of you hunting down 40 items. Snapshots are kept for 30 days by default, so check the result while you still can roll it back.
Create a checkpoint called “before meta descriptions”. Then show me the proposed text for the first three products and wait for my OK.
Ask for the plan before the action: what will change, on which items, with a preview. Name what must stay, such as product names, URLs and prices. Afterwards, PowerWP AI › Changes lists everything. You can roll back one change, a WooCommerce batch of up to 100 items, everything after a checkpoint, or a whole work session (kept for 30 days by default). If the same item was edited again since, the rollback stops and tells you instead of overwriting that newer work.
PowerWP also tests risky changes. After a plugin or theme is installed, updated or switched, after a code file is written or after a key setting changes, it loads your site and its admin again and reverts the change if either broke. Treat that as a safety net, not a reason to skip the plan.
Try big changes on staging first
A checkpoint protects your data. A staging copy protects the shop while you find out what a change does. Theme switches, mass price changes and anything that touches checkout belong on a copy first. PowerWP doesn’t build the copy for you: your host or a staging plugin does that.
What PowerWP does let you do is say what kind of site it is. In Settings you can mark a site as production, staging or development. AI apps are told, and on production they are told to take extra care. Give the staging copy its own connection, so a mistake there stays there, and repeat the change on the live site once you have seen the result.
Keep backups on your computer
PowerWP builds full, database-only or files-only backups on the server, downloads them to your computer with SHA-256 checksums, and removes the server copy once the checksums match (or after 48 hours). A backup that lives only on the server it protects is lost with that server, so this order is deliberate. To restore, you pick the files you downloaded.
How the download happens depends on the app. Claude Code can download backups to your computer by itself. In Claude, on the web, in the desktop app or on your phone, you get download links to click. Backups need the Developer level. Ask for a fresh one before any big job, and keep it where you will find it later.
What can’t be rolled back
Changes are recorded, so you can roll them back. Some actions can’t be undone by their nature, and the log marks them so you know which is which.
- Clearing caches and transients.
- Creating or restoring a backup.
- Running abilities that other plugins provide.
- Some database statements. One that can’t be snapshotted only runs when your AI app confirms it on purpose, so make a backup first.
- A WooCommerce batch of more than 100 items (up to 100 can be rolled back as one batch).
- Anything that already left your site, such as an e-mail or a call to a payment provider.
These often hide inside bigger jobs, like “clear all caches after the price update”. Reading is always safe. Before a job that includes any of the above, take a backup and read the plan.
The AI access switch
Sometimes the right answer is to stop everything. One switch in PowerWP AI turns off all AI access at once, and the screen keeps working so you can switch it back on. Read-only mode, a separate setting, limits every connection to reading, whatever its permissions say. If you can’t log in to wp-admin, adding define( 'WPAI_MCP_DISABLED', true ); to wp-config.php does the same. And if a plugin or theme crashes the site, rescue mode lets your AI app start without your other plugins and theme, so it can read the error and switch off the cause. Rescue mode works for apps that connect with a key and for apps that signed in, such as Claude and ChatGPT.
No AI app can change PowerWP’s own settings or connections, or switch the plugin off. Only an administrator in wp-admin can.
In short
- One Read-only connection per app and person.
- An expiry on every key, and an IP allow-list where you have a fixed address.
- Your rules in site memory.
- A plan first, then a checkpoint, then the change.
- Staging for theme switches and mass edits.
- A fresh backup on your computer before big jobs.
- Know where the AI access switch is.
The Safety page shows all the layers in one place. The docs cover working safely on a live site, rescue mode and the setup steps for each AI app.
Questions
Can an AI app break my site?
It can make mistakes, like a person with the same access. Start Read-only, ask for a plan first, set a checkpoint before bulk work and keep a fresh backup. Risky changes such as plugin updates are checked, and reverted if the site breaks.
Can I limit what an AI app sees?
Yes. Each connection has its own permissions, so you decide what it may change. Passwords and API keys stay masked unless you allow secrets, and order checks leave out personal details by default. Anything an app reads goes to its AI provider, so ask only for what the job needs.