Chat is the main interface for business users and operators who interact with agents. Use chat to send prompts, receive streamed responses, and review previous conversations.

​
Start a conversation

Open:
Existing conversations use:

​
What happens during a run

  1. You send a message.
  2. The frontend sends the request to the backend.
  3. The backend runs the configured ADK agent.
  4. The frontend renders the streamed response.

​
Embedded chat

Pinter also has embedded chat routes for surfaces that host chat inside another application:

​
Reading responses

Agent responses may include markdown, citations, tool output, execution details, or Flint chart artifacts depending on backend configuration. See Flint chart artifacts for the supported chart types, required encodings, examples, and compatibility aliases.
If a response looks incomplete, check backend connectivity and whether the conversation stream closed early.

​
Inspect execution traces

Each agent response can show an inline trace above the message. Expand it to see how the agent produced the answer:
  • Model reasoning steps.
  • Tool calls and their results.
  • Sub-agent transfers in multi-agent workflows.
Traces come from the backend trace store:
Use traces to diagnose wrong answers: check whether the agent called the expected tool and whether the tool returned useful data before blaming the model or the instruction.