A conversation with the Divi AI Agent is a working session, not a scratchpad you can only add to. It's worth managing the same way you'd manage any other tool: start a fresh one for a new job, keep track of what's queued up, watch how full it's getting, and know how to roll back a step if something goes wrong.

Click the New Chat icon whenever you're moving on to a different task. A new chat starts with no prior context, so the Agent isn't carrying assumptions from the last request into this one.

Chat history lists your past conversations so you can find and reopen one. From that list, each conversation has its own menu with four actions:

Both Duplicate Chat and Delete Chat are unavailable while the Agent is generating a response in that chat - stop the response first, then duplicate or delete it.

You don't have to wait for the Agent to finish before typing your next request. Send a message while it's still working, and it goes into a queue above the composer to run once the current one finishes.

Anything sitting in the queue can still be changed before it runs: edit it back into the composer, duplicate it, or delete it. Once the Agent picks it up, it's part of the active request, not the queue.

While the Agent works, it posts a running log of what it's doing. Longer or more complex requests also get a Todos list - the steps the Agent has planned out and its progress against them, so you can see the shape of the whole task rather than just the current step.

If the Agent hands part of the work to a sub-agent (it can run up to ten at once on a single request), you won't see that as a separate reply. The sub-agent's output folds into the same Working notes as everything else in the log, rather than appearing as its own message.

The AI Agent's chat window shows a Context Usage meter as a percentage - a rough read on how much of the conversation's working memory your chat history, attachments, and other context are taking up.

When it gets close to full, the Agent switches to an Optimizing Context state to summarize and make room before it can keep going.

Two habits keep this from becoming a problem.

For more details, check out the How to Add Context to the Divi AI Agent article, which covers how context is attached and removed in more detail.

Every one of your own messages in the conversation carries a restore option. Click the Restore icon and confirm in the Restore to This Point dialog to return the page in the builder to how it looked right before the Agent acted on that message, undoing what it changed afterward.

Restore isn't always available. It's grayed out in five situations:

In each case, wait for the blocking condition to clear, then try again.

Keep in mind what restore does and doesn't do: it reverts the working canvas, not a saved page, and it doesn't save your page for you afterward - that's still a separate, approval-gated step.

And because manual edits made after the restored point are lost right along with the Agent's own changes, it's worth pausing before you restore if you've been making hand edits alongside the Agent's work.

Any of your prompts used in any chats with the AI Agent can be copied to your clipboard.

This can be a very quick way to create new rules from existing prompts.