# The MetaPrompter interface: fields & controls

{% embed url="<https://drive.google.com/file/d/1h8Cle3joNWDDQHGt9RPTqXvwwf-fl3v-/view?usp=sharing>" %}

*The input area, output area, & proposal controls that make up the MetaPrompter interface.*

### Overview

The MetaPrompter interface consists of three connected surfaces that work together to support natural language editing with full visibility into what changed. Each surface serves a distinct role in the editing and review process.

### Chat Panel

The chat panel is the primary interaction point. Users describe the changes they want to make, and MetaPrompter responds with an interpretation of the request, the proposed configuration changes, any warnings or approval requirements, and confirmation of saved updates.

The chat panel maintains a running record of the interaction, making it possible to follow the sequence of changes made across a session.

### Graph View

The graph view provides a visual representation of the Digital Worker's structure. As MetaPrompter applies changes, the relevant nodes update to reflect what was added, modified, or removed.

Node types represented in the graph include instructions, triggers, tools, connectors, memory, approvals, and outputs. Nodes can appear in different states depending on what happened to them: added, updated, removed, warning, approval required, draft, or live.

The graph gives users an immediate visual understanding of the scope and location of changes, making it easier to assess the impact of a request before saving.

### Settings Panel

Clicking a node in the graph opens the corresponding configuration area for that component. This allows users to inspect the specific change that was made and refine it manually if needed.

For example, if MetaPrompter updates a trigger node, clicking that node opens the trigger settings, where the new value can be reviewed, the schedule or conditions adjusted, and the change saved or discarded. This provides a direct path from natural language editing to precise manual refinement without leaving the interface.


---

# Agent Instructions: 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:

```
GET https://kb.theloops.io/agenticstudio/resource-library/hidden-metaprompter/the-metaprompter-interface-fields-and-controls.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.
