> ## Documentation Index
> Fetch the complete documentation index at: https://docs.bizzyco.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Chatting with an Agent

> The full-page Bizzy agent chat interface

Each agent has a chat interface at `/{org}/agents/{id}` — a full-page,
message-by-message view with inline tool calls and approval cards.

<Frame>
  <img src="https://mintcdn.com/thebizzycomapny/LTbGbhRRJUQlFsAe/images/user-guide/agents/chat-view.png?fit=max&auto=format&n=LTbGbhRRJUQlFsAe&q=85&s=8b9655588e21a3ff9d2a4a43d010cbf6" alt="Agent chat page with tool approval card" width="800" height="500" data-path="images/user-guide/agents/chat-view.png" />
</Frame>

## Starting a conversation

1. Open an agent from the **Agents** list.
2. Type a message in the composer at the bottom of the chat.
3. Send.

The agent thinks, optionally calls tools (subject to your
[permissions](/user-guide/agents/tool-permissions)), and replies.

## Tool calls inline

When the agent calls a tool, you see an inline card showing the tool name,
inputs (collapsed by default — expand to see), and outputs once the call
returns.

If the tool is set to **Ask**, the card pauses with:

* The tool's risk badge
* The inputs the agent wants to use
* **Approve** / **Deny** buttons

The approval waits as long as you need — there's no countdown. The agent can't
continue that conversation until you respond: **Approve** resumes it right where
it paused, and **Deny** lets it explain and move on. A pending approval is tied
to its own conversation, so starting a new chat leaves it parked — return to that
conversation to approve or deny it.

## Files and images in chat

When the agent or one of its tools produces a file, it appears in the
conversation as an attachment card instead of raw text. Images show a
thumbnail preview; other file types show a type icon with the filename and
format. Use the download button on the card to save the file.

Attachments in chat are display-only for now — you can't yet upload your own
files from the composer.

## Multiple conversations

Each conversation is independent, so you can keep several going at once — they
run simultaneously without interfering with one another. Starting a new chat
opens a fresh conversation; the one you were in keeps its full history and any
work in progress.

## Resuming past conversations

Past conversations appear in
[Agent Conversations](/user-guide/agent-conversations/index). Open any
conversation's detail page to see the full history; send a new message to
continue from where it left off.

## Under the hood

* The chat uses a WebSocket connection for low-latency streaming.
* The UI is lazy-loaded, so the first open of an agent chat may take a moment.
* Messages persist even if you close the tab — reload and you'll see what was
  already there.
* Messages are grouped by day with a date separator (**Today**, **Yesterday**,
  or the date) so longer conversations are easy to scan.

## Troubleshooting

| Problem                                      | Likely cause                                           | Fix                                                    |
| -------------------------------------------- | ------------------------------------------------------ | ------------------------------------------------------ |
| Agent just says "Max steps reached"          | The agent hit its `maxSteps` budget mid-turn           | Raise `maxSteps` on the agent, or simplify the request |
| Tool keeps asking for approval               | Permission set to **Ask**                              | Change to **Allow** in the Tools tab if you trust it   |
| Agent refuses a task it should be able to do | System prompt too restrictive, or tool set to **Deny** | Review the prompt and Tools tab                        |

## Next steps

<CardGroup cols={2}>
  <Card title="Agent conversations" icon="comments" href="/user-guide/agent-conversations/index">
    Review or resume past chats
  </Card>

  <Card title="Tool permissions" icon="shield-check" href="/user-guide/agents/tool-permissions">
    Fine-tune what the agent can do
  </Card>
</CardGroup>
