Skip to main content
Version: v1.7.0

Agent response view

Overview​

The agent response view appears when you start an agent chat and provides a structured interface for tracking agent tasks. It features customizable view modes (Simplified, Standard, and Detailed) and background streaming, which lets you navigate to other chats or pages while the agent is working, without losing any progress or metadata.

View modes​

The interface offers three unique view modes, each designed to effectively support different complex workflows. Click View at the top-right of the agent response to switch between view modes.

  • Simplified view: The main UI displays only the final response, omitting the chain of thoughts, which is the reasoning process the model uses to arrive at its answer.
Simplified view
  • Standard view: Shows the chain of thoughts in the main UI. The right panel does not open automatically, keeping the interface cleaner unless you choose to inspect details.
Standard view
  • Detailed view: Shows the chain of thoughts in the main UI and the right panel opens automatically during streaming to show progress.
Detailed view

Right panel features​

The right panel provides detailed information about the agent's execution. Click Details to open the right panel. It contains the following sections:

  • Steps: An organized timeline of code generation, execution steps, results, and file generation.

  • Files: A file explorer view listing all files in the current workspace.

  • Sources: A list of external web sources referenced by the agent, showing titles, domains, and content snippets. Appears only when sources exist.

  • Thoughts: A panel displaying the agent's analysis.

  • Chat: Internal agent-to-agent chat logs. Visible when internal agent chat data is available, typically after task completion.

Right panel
note

Not all tabs appear for every conversation. Sources appear only when sources exist.

File actions​

You can directly Download files and Import to collection in the current workspace. To add files as tools, see Add files as tools.

Click Files in the right panel, then click the menu icon

to see the available options.

File actions

You can also scroll to the bottom of the agent response and click See all files to directly open Files in the right panel.

Download files​

Download selected files in the form of a ZIP archive.

The Download Files dialog includes:

  • A search bar to filter files
  • A toggle to switch between All, New, and Old files
  • An option to select files or Select all
  • A Download button
Download files

Import files to collection​

Add selected files to a collection directly.

The Import Files to Collection dialog includes:

  • A search bar to filter files
  • A toggle to switch between All, New, and Old files
  • An option to select files or Select all
  • A dropdown to select the target Collection
  • An Import button

Select the files to add, then choose the Collection from the Target Collection dropdown.

Import files to Collection

Add files as tools​

You can configure tool settings for selected files and package multiple files as a single tool.

In the Add Files as Tool dialog, select the files. Under Tool Configuration, configure the settings to apply to the selected files. You can select from three types of tools:

1. Local MCP Tools​

  1. Select Local MCP Tools to create a custom MCP server tool.
  2. Upload a ZIP file containing a server.py entry point (required), along with optional envs.json and description.md files.
  3. Enter a descriptive name for your local MCP tool under MCP Server Name.
  4. Under MCP Usage Mode, select Runner, Creator, or both.
  5. Optionally, select Enable by Default to make the tool available in new conversations.
  6. Click Add Tool.
Local MCP Tools
info

See Local MCP Tools to learn more about local MCP tools and MCP usage modes.

2. Browser Action Tools​

  1. Select Browser Action Tools to add a tool for browser automation and web interactions.
  2. When uploading multiple files, provide a common description that applies to all tools.
  3. Click Add Tool.
Browser Action Tools

3. General Code Tools​

  1. Select General Code Tools to upload custom code tools with system prompt integration.

  2. Tool name: Enter the primary function name that the agent will call. This must exactly match your main function name.

  3. Description: Describe what the code does.

  4. System Prompt: Describe your tool and provide usage instructions.

  5. Unzip file on server: Select this checkbox if you are uploading a .zip file that needs to be extracted on the server.

  6. Enable by Default: Select this checkbox to enable the tools by default for new conversations.

  7. Click Add Tool.

General Code Tools
info

See How to review agent behavior to understand how an agent completes a request.

Technical limitation

Files within the workspace cannot directly access other files. For example, an HTML file cannot link to or reference another file in the workspace. HTML and React previews render in a sandboxed iframe with a limited set of packages available.

Images

Agent-generated HTML files are rendered in a sandboxed iframe. If you want an agent-generated HTML file to show images directly in the UI preview, instruct the agent to use Base64 encoding. Otherwise, images generated with relative file paths will only be visible when downloaded and viewed locally.

Further reading​

See Agents overview to learn more about Enterprise h2oGPTe agents, getting started with agents, how agents work, and creating custom agent tools.

Feedback