The Divi AI Agent isn't limited to the page you have open. From the same chat, it can create and manage pages and posts, build and rearrange navigation menus, work with Theme Builder templates, pull items from the Divi Library, and read or change your site-wide Theme Options - all without you leaving the Visual Builder to go dig through separate WordPress screens.

Before you try any of it, please note that almost every action in this article is tagged Destructive, which means the Agent stops and shows you an Approval Required message before it runs, every single time, with no exceptions and no setting anywhere in Divi that turns it off.

A few of the remaining actions are tagged Moderate but were still built to always ask first, because what they create tends to stick around and get used elsewhere. For more details, check the Approvals and Risk Levels in the Divi AI Agent article.

The Agent can search your pages, posts, and custom post type items by title, status, or slug, and hand back a clean list of published titles and permalinks - all read-only, so there's nothing to approve.

Creating a page or post asks for confirmation before it goes ahead, and you can set its status to draft, pending, private, or scheduled for a future date in the same request.

Once something exists, the Agent can update its title, slug, or written content directly, change its publication status (which is how you publish, unpublish, or reschedule something already made), or move it to Trash, and each of those always asks first.

It can also apply an already-built Divi layout to a page or post other than the one you're looking at, which replaces whatever Divi content that item already had, so that one always asks too. It can also read a post's custom fields, including ones added by a plugin, without changing anything.

The Agent can create a menu, look up an existing one by name or by the theme location it's assigned to, and list every item inside it. Adding several menu items at once, removing several at once, and reordering or re-nesting items are all handled as a single batch request rather than one item at a time.

Assigning a menu to a theme location, or clearing whatever menu is currently assigned there, works the same way, and the Agent can delete an entire menu outright when you no longer need it. Creating a menu and adding items run right away without a prompt; removing items, reordering, deleting a menu, and both sides of a location assignment are Destructive and always ask first.

The Agent can list your Theme Builder templates, create a new one with a blank header, body, or footer layout to build into, update an existing template's title or layout assignments, set the display conditions that decide where a template appears, and delete a template, which trashes it and detaches it from the Theme Builder.

Creating a template asks for confirmation because it's a lasting addition to your site; updating, assigning conditions, and deleting are Destructive and always ask.

The Agent can list what's saved in your Divi Library, save a module, row, or section to it, insert a saved item into your page, replace your entire current page with a saved Library layout, and delete an item from the Library. Saving, inserting, and replacing the page you're currently on are Moderate but run right away; deleting is Destructive and always asks, since it's the one step here you can't undo yourself. For more details about Divi Library, check the Divi Library in Divi 5 article.

The Agent can read your site-wide Theme Options and change one at a time, things like your logo, navigation behavior, and other settings that apply across the whole site rather than to one page.

It only sees and changes an allowlisted subset of the full Theme Options panel, not everything in it, so if you ask for a setting it can't reach, expect it to say so rather than guess.

Changing a Theme Option is Destructive and always asks first. The panel itself is covered in Divi 5 Theme Options.

At the site level, the Agent's toolkit is narrower on purpose.

Inside a page, it can reach into individual modules, settings, and design values in fine detail. At the site level, the tools above work on the whole item rather than its parts, and a few things have no dedicated tool of their own: there's no single action that duplicates a page in one step, though asking it to look at one page and create a new one from what it finds will often get you close.

There's no tool for managing WordPress users, plugins, comments, or widgets, and reading or changing Theme Options is limited to an allowlisted subset rather than the whole panel.