> For the complete documentation index, see [llms.txt](https://gdplabs.gitbook.io/glchat/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://gdplabs.gitbook.io/glchat/application-ui/how-to-guide/chat-input-and-responses/interactive-agent-responses.md).

# Interactive Agent Responses

#### Overview

GLChat supports interactive Agent responses through **A2UI**. With this capability, an Agent response can be rendered as an interactive UI component inside the chat, instead of being shown only as plain text.

This allows users to interact with the Agent output more naturally, such as filling in forms, selecting options, reviewing structured information, confirming actions, or continuing a guided flow directly from the chat interface.

For example, instead of asking the user to reply manually with several details, the Agent can show a structured form or selection component. The user can then complete the interaction directly in GLChat.

<figure><img src="/files/ryPfpcCxPWVhQCMddObQ" alt=""><figcaption></figcaption></figure>

This helps users interact with Agent outputs in a more structured and visual way.

#### What Makes It Interactive

Interactive Agent responses allow the Agent to present information and collect user input using UI components.

Depending on the Agent configuration and supported components, the response may include:

* **Forms** for collecting structured input from users.
* **Buttons** for triggering actions or confirming the next step.
* **Selections** for choosing one or more options.
* **Cards or lists** for displaying structured information.
* **Tabs** for grouping related information.
* **Modals or confirmation dialogs** for review and approval steps.
* **Date, checkbox, slider, or text input fields** for guided data entry.

This helps reduce back-and-forth conversation when the Agent needs specific information from the user.

#### Example Use Cases

Interactive Agent responses are useful when the conversation requires more than a simple text answer.

Common use cases include:

* **Form submission**\
  The Agent can ask the user to complete a form, such as request details, issue information, or additional data needed to continue a workflow.
* **Confirmation step**\
  The Agent can show a summary and ask the user to confirm before continuing with an action.
* **Option selection**\
  The Agent can present several choices, such as categories, priorities, available actions, or recommended next steps.
* **Structured result display**\
  The Agent can show results in a card, table-like layout, list, or grouped section so the information is easier to scan.
* **Guided workflow**\
  The Agent can guide users step by step using interactive components, instead of relying only on long text instructions.
* **Action-oriented response**\
  The Agent can provide a button or input component when the user needs to continue an action directly from the chat.

#### How It Works

When a user interacts with an Agent, the Agent may return an A2UI-compatible response.

GLChat will detect the response and render it as an interactive component in the chat interface, as long as the component is supported.

The rendered result depends on:

* The A2UI components supported by the Agent.
* The rendering capability supported by GLChat.
* The Agent configuration.
* The response format generated by the Agent.
* Any additional behavior implemented on top of A2UI in GLChat.

If the Agent returns a supported interactive response, GLChat will render it directly. If the response is not supported, additional implementation or configuration may be required.

#### Supported Interaction Patterns

The exact component support may depend on the current GLChat implementation and Agent configuration. In general, interactive Agent responses may support patterns such as:

| Interaction Pattern | Description                                                        |
| ------------------- | ------------------------------------------------------------------ |
| Text input          | User enters information into a field.                              |
| Selection           | User chooses from available options.                               |
| Button action       | User clicks a button to continue or trigger an action.             |
| Confirmation        | User reviews information before proceeding.                        |
| Structured display  | Agent presents information using cards, lists, or grouped layouts. |
| Guided flow         | Agent guides the user through multiple steps using UI components.  |

#### Key Benefits

Interactive Agent responses help make Agent interactions more structured, visual, and easier to complete.

Key benefits include:

* Reduces long text-based instructions.
* Makes Agent responses easier to understand and act on.
* Helps users provide structured input with less ambiguity.
* Improves guided workflows inside GLChat.
* Supports richer Agent experiences beyond plain text.
* Enables clearer confirmation and review steps before an action is continued.

#### When to Use

Use interactive Agent responses when the Agent output is better presented as a UI component instead of regular text.

This is recommended when:

* The Agent needs the user to provide several pieces of information.
* The user needs to choose from predefined options.
* The Agent needs confirmation before continuing.
* The response contains structured information that is easier to scan visually.
* The interaction is part of a guided workflow.
* The Agent output is action-oriented and requires user input.

For simple explanations, summaries, or general Q\&A, a regular text response may still be sufficient.

#### Configuration Notes

To use interactive Agent responses, the Agent needs to be configured to return an A2UI-compatible response format.

The experience may vary depending on:

* Which A2UI components are enabled.
* Which components are supported by GLChat.
* How the Agent prompt or tool response is configured.
* Whether the required interaction behavior has been implemented in GLChat.

For example, an Agent may be able to return a form-like response, but the final behavior depends on whether the form components and submission handling are supported in GLChat.

#### Technical Reference

For the list of supported A2UI features and components, refer to the dedicated [**SDK A2UI** technical documentation page](/glchat/sdk-a2ui/overview.md)

#### Note

Interactive Agent responses depend on both the A2UI component support and the GLChat rendering implementation.

If a component or behavior is not supported yet, additional implementation or configuration may be required before it can be used in GLChat.