> For the complete documentation index, see [llms.txt](https://kb.theloops.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://kb.theloops.io/agentstudio/resource-library/hidden-metaprompter/how-to-review-and-apply-metaprompter-changes.md). # 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. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://kb.theloops.io/agentstudio/resource-library/hidden-metaprompter/how-to-review-and-apply-metaprompter-changes.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.