Skip to main content
An agent chat lets you submit a request and inspect the response, activity, and available result files.

​
Before you begin

Select the project and an available agent.

​
Start a conversation

  1. Open AgentOps → Agents and select an available agent.
  2. Open its chat, enter a specific request in the input field, and send it. Include relevant context and the outcome you need.
  3. Follow the response and any displayed activity. If an approval is requested, review it before choosing Approve or Reject.
  4. Inspect the answer and any result or file cards. Open or download a file when the corresponding action is available.

​
Verify and troubleshoot

Check the answer and files against your original request before relying on them. If a message fails, read the displayed error. Before retrying a request that may change something, check the conversation and destination for effects that may already have occurred. If an agent or resource is unavailable, check the selected project and your access. See Approvals and recovery. To set up an agent for a specific job, see Create and configure an agent. For named work assigned to an agent or team, see Create and manage a task.

​
Continue, steer, or stop work

When supported by the conversation, you can send a text instruction while the agent is working. It is queued for the active task rather than proving the agent has already acted on it. Check the displayed status and subsequent response. Attachments are not supported in this queued-text path; wait for the appropriate upload state to send a file. Use the conversation’s stop control, or /stop, to request that running work stop. Wait for the resulting status. Stopping a task does not undo a completed external write or notification. After a disconnect, reopen the existing conversation and inspect its recovered messages and results before resending work.

​
Open saved results beside the chat

A result card can identify a Canvas page, Table or Schedule. Select its title to open the resource in the side view. Inspect the resource’s actual content and use its own save controls when editing; an agent message is not proof that an edit was stored. You can also return through the resource’s normal project view. Saved native resources differ from downloadable file cards. To preserve a file outside the runtime, follow Upload and download files and Data management.