How to review & apply MetaPrompter changes

Overview

MetaPrompter surfaces a structured summary of every change it makes, giving users full visibility into what was updated before anything is saved or promoted. Reviewing proposed changes is an important step in the editing process, particularly when a request involves external communication tools, data connectors, trigger or workflow logic, or sensitive execution behavior.

What to Review

After submitting a request, check which nodes were affected, whether the changes match the original intent, whether any connector or tool access was added, and whether any trigger or workflow logic was modified.

The Review Flow

The typical review sequence after submitting a prompt is to read the change summary in the chat panel, inspect the graph to see which nodes were affected, click changed nodes to open and review the corresponding settings, save the draft once the changes are confirmed, and run tests in the test environment before considering promotion to production.

Why Review Matters

MetaPrompter is designed to be transparent rather than autonomous. Changes are proposed and summarized before being finalized, and every affected component can be inspected and adjusted manually before a draft is saved. This means users remain in control of the Digital Worker's configuration at every stage, with natural language providing speed and the review process providing accuracy.

Careful review is especially important before promoting a version to production. Before submitting, confirm the change summary is accurate, all affected nodes have been inspected, any warnings or approval requirements have been addressed, and test results support the change.