What the AI can and can't do

Handing an AI the keys to your site should make you a little nervous. That's healthy. So here's plainly what it can do, what it can't, and where the guardrails are.

What it can do

• Read and write inside your active theme and your plugins.
• Do the everyday WordPress work: posts, pages, media, menus, users, and WooCommerce.
• Edit pages and global styles in Divi, Bricks and Elementor.
• Read and write SEO titles and descriptions if you use Rank Math.
• Install, activate, update or remove plugins and themes, the same as you would in wp-admin.
• Scan for malware, check your scheduled tasks, and look at login logs.

What it can't do, ever

• Reach outside your theme and plugin folders, including by sneaking a path like ../ around the edges.
• Read or write wp-config.php or .htaccess by default.
• Run shell commands or get server-level access.
• Do a destructive action silently, without leaving a record.

The file tools are sandboxed on purpose. The AI gets real capability, not an open door to your server.

Confirmations

Anything that can't be undone asks for a confirmation first. Restoring a backup is one example.

The honest part

An AI can be confidently wrong. It can misread a request, or build something that isn't what you pictured. That's why PressConduit takes a snapshot before it changes things and keeps an activity log, so you can see what happened and put it back. Read about that in Undo and the activity log.

Treat the assistant like a fast new hire. Give it clear instructions, and check the work before you tell anyone it's finished.