Agent tools and confirmations

Review plans and confirm supported Agent actions before they change anything. A clear request in the chat tells the Agent what you want changed; if the request is ambiguous, risky, or blocked by a conflict, the Agent should ask before continuing.

Know what can change

The main Agent workspace can answer questions, search CareMap Help, search authorized workspace content, inspect lightweight Guide details, read schedules, create, update, or remove scheduled Guide and Form items, calculate expressions, and create Notes.

Guide and Form editing tools are available only from the Agent inside the matching editor. The Guide Agent can apply changes to the open Guide, and the Form Agent can apply changes to the open Form. Opening a Guide or Form in the editor does not authorize a change by itself; the Agent still needs your clear request and the same permissions you would need to make the change manually.

Review a planned change

For important edits, ask the Agent to describe the plan before applying it. This is especially useful before deleting or moving Guide content, changing a Guide target Form, clearing Field mappings, changing schedules, or editing a Form structure.

When you are ready, confirm the exact change in the chat. For example, “Yes, move the Morning Check-in schedule to 10:00 AM on August 4,” is safer than “yes” when several items were discussed. If you want research only, say “do not change anything.”

Some actions require extra confirmation after the Agent finds a problem. For example, overlapping schedule changes should not be saved unless you explicitly confirm the overlap. Changing or clearing a Guide target Form may remove Field mappings, so confirm that fallout only when you understand the effect.

Watch tool activity

While the Agent works, you may see tool traces such as Searching CareMap knowledge, Searching CareMap Help, Reading schedule, Scheduling guide, Updating schedule, Removing scheduled guide, Creating Note, Calculating expression, or Applying Guide authoring plan. Tool traces show what the Agent is doing and can be expanded to review Input and Output.

A trace marked error means the tool could not complete. Common causes include read-only access, missing or archived content, stale editor context, ambiguous targets, schedule conflicts, unsupported fields, or a tool that is unavailable on the current Agent surface.

If the response is still running and is no longer useful, select Stop CareMap response. Completed tool results and the message are saved when CareMap reports that they were saved, so review the affected screen before asking the Agent to retry the same action.

Check the result

After a successful action, open the affected Guide, Form, schedule, or Note and confirm that the result matches what you approved. Source links and tool traces help you verify the answer, but they do not replace checking the actual record.

If the Agent cannot complete an action, try the same change manually. When the manual action is also unavailable, the issue is usually permissions, workspace scope, content state, or a product limit rather than the chat wording. Switch to the correct workspace, clear folder-only tool limits if needed, refresh the editor, or ask the owner or organization manager for access.

The Agent cannot use wording to bypass CareMap permissions. It also does not update Notes after creation, change sharing grants, expose another person's private content, or perform Guide or Form authoring from the main workspace Agent.