You imported a section from our library, dropped it on a page, and now the real work starts: the headline talks about "Pagecraft", the button is our blue, and the testimonial quotes someone who does not exist. Divi AI Agents can take a good share of that cleanup off your hands, as long as you tell them exactly what to touch and check what they did. This guide walks through a practical way to do it, from the first plan to the phone-size check.
New to importing? Start with how to import a Divi 5 layout into your Divi Library, then come back here.
What Divi AI Agents are, in plain terms
The AI Agent is a chat panel inside the Divi 5 Visual Builder. You open it from its icon in the builder's left toolbar, describe what you want, and it works on the page you have open: it can add or move modules, change their settings, replace text, and propose Design Variables and Presets for you to approve.
It has two modes, and the difference matters:
- Ask explains and plans. It does not change your page.
- Build makes the changes.
What you need Divi 5 and an active Divi AI subscription, which Elegant Themes includes with Divi Pro. Agent requests are paid from a monthly usage allowance that is separate from Divi AI's other tools. At the time of writing (November 2026), Elegant Themes lists that allowance at $5 a month, and it does not roll over. Check their current terms before you rely on it for client work.
Why our layouts are a good match for the agent
An agent works best when a page is built from named parts instead of loose values. Every layout on Divi Design Kit uses native modules, global colors with plain names (Ink, Body, Blue and so on), number variables for repeated spacing, and presets for headings and buttons. That gives you something specific to point at. "Make the Blue color variable our brand green" is a clear instruction. "Make it greener" is not.
One thing to keep in mind before you begin: global colors, variables and presets are shared. If the agent changes one, every page that uses it changes too. That is usually what you want, but it is worth knowing before you approve the save. Our guide on rebranding a Divi 5 layout with global colors, variables and presets explains how those pieces fit together.
A five-pass workflow for one imported section
Doing everything in one long request is tempting. In practice, smaller passes are easier to check and easier to undo. Work on a draft page or a staging site, and do one section at a time.
Ask for a plan first
Switch to Ask, add the section as context (use the Context picker or type @ in the chat), and ask what it would change to fit your business. Nothing moves yet, so this costs you nothing but a read.
Example: "This hero is for a bakery called North Loaf in Leeds. List the text you would change and anything in the layout that does not suit a bakery. Do not change anything yet."
Replace the copy
Switch to Build, keep the same section as context, and give the agent the facts it cannot know: your name, your offer, your tone. Say what must stay as it is.
Example: "Rewrite the headline, the paragraph and both buttons for North Loaf. Short and friendly, no exclamation marks. Keep the layout, the images and every style exactly as they are."
Bring in your brand colors through variables
Point the agent at the global colors rather than at individual modules. Type @ to attach the color variable you mean, then ask for the change. Saving shared variables needs your approval, so you get a chance to read the proposal first.
Example: "Change the Blue color variable to #2F6B4F and the Ink color variable to #1C1A17. Do not create new colors."
Restyle headings and buttons with presets
If you imported the layout with its presets, attach the heading or button preset as context and ask for the font or shape you want. Afterwards, check that the preset itself changed: a module can look right because of a local override while the preset stays the same.
Check tablet and phone
New copy is rarely the same length as the old copy, so line breaks shift. Look at the section at tablet and phone width yourself. If a heading wraps badly, ask the agent for a smaller phone size on that one module, then check again.
Save your standards as Rules and Commands
If you customize layouts often, you will find yourself typing the same instructions again and again. Two features save that effort.
- Rules hold standing guidance, such as your brand voice or "use existing variables instead of typed values". A rule set to Always Use applies to every conversation; one set to When To Use applies only when its description fits the task.
- Commands store tasks you repeat. Type
/to insert one, adjust it, and send. Good candidates: an alt text check, a scan for hard-coded colors and sizes, or a short review before you publish.
Rules shape how the agent works, but they are not a guarantee. You still review the result.
Approvals and undo: what you can take back
The agent sorts its actions by risk: Safe, Moderate and Destructive. Destructive actions always ask first. Saving the page, changing publish status, and saving shared variables or presets also wait for your approval, while most everyday layout edits run straight away.
To go back, use the restore control on one of your own earlier messages. Know its limits before you need it:
- It returns the canvas to that point, including removing any edits you made by hand after it.
- It does not reverse things that were already saved at site level, such as an approved variable or preset change.
- Wait until the agent has finished and any approvals are answered before you restore.
Good habit Before you approve a change to a shared color, variable or preset, note the old value. If you change your mind later, restoring the chat will not bring it back, but typing the old value will.
Where to keep your own hands on it
The agent is fast at the repetitive parts. It is not a replacement for looking at the page. Elegant Themes' own guidance on steering the agent makes the same point, and these are the spots where a quick manual check pays off:
- "Done" is not proof. The completion message tells you the agent finished, not that every setting landed. Open the module and look.
- Long requests may finish partly. If you asked for five things, check all five.
- Vague targets get misapplied. Name the element through context instead of describing it.
- Background images have no alt text. An alt text pass will skip them; that is expected.
- Colors from a screenshot are estimates. If you give the agent a reference image, check the hex values and the text contrast yourself.
- Long chats get crowded. When the Context Usage meter fills up, start a new conversation for the next job.
Try it on a small section first
A call to action is a good first test: a headline, a line of text and a button, so every change is easy to see and easy to check. Pick one from our call to action layouts, import it, and run the five passes above. Once you trust the routine, move on to bigger sections like pricing tables or heroes. Every layout in the library is free.