If you've connected an AI assistant to your Flashcloud account and turned on action permissions, you can ask it to update WordPress core, update plugins and themes, or create a staging copy of a site, in plain language. The assistant proposes exactly what it's about to do, you confirm, and only then does anything change.
What you can ask for
The assistant has separate tools for each part of WordPress maintenance, so you can be specific: update WordPress core, update plugins, update themes, or create a staging site before you touch anything. Some things to try:
- "Update WordPress core on example.com"
- "Update all my plugins on example.com"
- "Create a staging copy of example.com so I can test a plugin update"
- "Turn on maintenance mode while I update"
- "Check WordPress site health for example.com"
Each of these maps to its own action: core update, plugin update, theme update, staging creation, maintenance mode toggle. The assistant can check your site's current state, including WordPress version, active plugins and themes, and site health, if you ask it to, so the proposal reflects the site's actual condition rather than a guess.
The confirmation step
Every action, not just WordPress ones, follows the same two-step pattern. The assistant sends a proposal describing exactly what it's about to change, naming the specific action and target. You read it and say yes or no. Only after you approve does the change execute. If you don't like what's proposed, say no and nothing happens.
This matters most for updates, because plugin and theme updates are the one place where doing it without a check can break a site. A major version bump on a page builder or an incompatible plugin combination can take a site down. The confirmation step exists so you see what's about to change before it changes, and you can ask the assistant to create a staging copy first if you want to test the update without touching the live site.
Staging before you commit
Asking for a staging copy is often the safer first move, especially before a core update or a batch plugin update. The assistant creates the staging environment, and you can point it there to test the same update before running it against the live site. Once you've confirmed the staging copy behaves the way you expect, ask the assistant to run the same update on the production site, or delete the staging copy if you decided against the change.
What's off limits
The assistant can update WordPress core, plugins, and themes, manage staging, toggle maintenance mode, reset a WordPress admin password, and run site health checks, along with account-level tasks like DNS edits, mailbox creation, and opening a support ticket. It can't touch billing, your Flashcloud account password, or two-factor settings, and it can't cancel a service or transfer a domain away. Those stay in the portal by design.
Reviewing or disconnecting
Open Goodies → AI Agents in your portal to see which assistants are connected, review their permissions, check when they were last used, or disconnect one to pull access. See connecting Gemini or connecting Cursor for setup steps if you haven't linked an assistant yet.
When to open a ticket instead
If an update goes wrong and the site won't load, don't keep retrying updates through the assistant. Open a support ticket from the portal (Support) or use live chat. A real person can restore from backup and dig into the error log directly, which is faster than troubleshooting a broken site through conversation.