Review and apply Agent editor changes

Guide and Form editor Agent requests can save changes directly to the open item. A clear request does not always trigger a separate approval dialog.

Review before applying

1. Open the correct Guide or Form editor and select the intended destination.
2. Tell Agent what outcome you want and what must remain unchanged.
3. For review first, explicitly say “Describe a plan; do not apply it yet.”
4. Check names, ordering, required answers, deletion, and mapping consequences.
5. Request the agreed changes when ready.
6. Expand tool activity to inspect Input and Output, then check the actual editor and Preview.

Opening Agent does not authorize an edit by itself. Asking a question about content should read it; asking to add, change, or remove it requests a write.

How grouped edits save

Agent can apply an editing group containing up to 25 operations. One visible request may need several operations or several groups. For example, creating a page and adding three blocks involves multiple edits.

Within one group, the changes either save together or fail together. A failed group does not leave its first few operations applied. This protection does not cover the entire conversation: earlier successful groups may already be saved when a later group fails.

Read each result and inspect the Guide or Form before asking for remaining work. Do not repeat a whole multi-part request merely because its final answer was interrupted.

These edits affect current shared content. They do not create a separate draft that needs publishing. Normal access, storage, required structure, and content validation still apply.

Current item and selection

The editing group is tied to the open Guide or Form and its current saved version. It cannot silently switch to another item named in the conversation.

“Current page,” “current section,” or “this field” depends on the selected location supplied with the request. Name the destination when several items could match. If content moves or is removed while Agent works, the request may need a fresh read or a new selection.

A new editor visit starts a fresh chat. Closing and reopening the panel during the same visit retains its chat and draft message. Choosing an older chat does not change which Guide or Form the editor can modify.

Stopping and reversing

Use Stop CareMap response to stop the response. Closing the panel does not stop it, and stopping does not undo saved edits.

Form Agent refreshes clear the builder's Undo history. Do not assume editor Undo can reverse a whole Agent request. Inspect the saved result and make a specific corrective edit if needed.

For conflicts, failed saves, or uncertainty about which work finished, follow editor recovery.