# Chat with an Agent

> Part of the NocoDB documentation (Agents). Index of all pages: https://nocodb.com/llms.txt. Any docs page is available as Markdown by adding `.md` to its URL.

URL: https://nocodb.com/docs/agents/chat-with-agent
Last updated: 2026-10-29

Chat with a NocoDB agent from its home page, start new chats, and find the chats and the runs that its triggers started in the session list of the agent.

Every NocoDB agent has a chat. When you open the agent and type a message, the agent answers with what it finds in your project. The agent uses its tools, within its [access](/docs/agents/tools-and-access) and its role. Each chat, and each run that a trigger starts, is a **session** of the agent.

## Before you begin

* You need the **Viewer** role or higher in the project.
* The agent must be turned on. When an agent is paused, its message box is not available.

## Start a chat

1. Open the project.
2. In the mini sidebar, click **Agents**.
3. In the sidebar, click the agent. The agent home page opens.
4. Type a message in the box, or click one of the **Suggested prompts**.
5. Press **Enter**. The agent answers in a new chat.

The agent home page shows the message box, up to 4 **Suggested prompts**, and the 5 most **Recent** sessions. A lightning icon marks the sessions that a trigger started.

To start another chat, click **New** in the chat header. You can also click **New chat** under the agent in the sidebar.

Coding agents have a different session screen, with the code, a live preview and a terminal. See [Coding sessions](/docs/agents/coding-sessions).

## Find a session

The sidebar shows the 5 newest sessions under the agent that is open. When the agent has more sessions, the sidebar also shows **View all** and the number of sessions. To see all the sessions:

1. Under the agent in the sidebar, click **View all**. The session list opens.
2. Search by name, or filter the list:

| Filter        | Shows                                                                                         |
| ------------- | --------------------------------------------------------------------------------------------- |
| **All**       | Every session.                                                                                |
| **Chats**     | Sessions that a person started in the chat.                                                   |
| **Automatic** | Runs that started without a chat: a schedule, a trigger, a channel message or a webhook call. |

The list groups sessions by date: **Today**, **Yesterday**, **Previous 7 days** and **Older**. To go back, click the back arrow.

<img alt="The session list of an agent with the search box and the All, Chats and Automatic filters" src={__img0} placeholder="blur" />

## Who can see which sessions

The kind of session sets who can see it:

| Session              | Who can see it                                                            |
| -------------------- | ------------------------------------------------------------------------- |
| **A chat**           | Only the person who started it. Only that person can rename or delete it. |
| **An automatic run** | Every project member who can see the agent.                               |

An automatic run is read-only. Its conversation shows **This conversation was started by a trigger and can't be continued.** To ask a follow-up question, start a new chat.

## What an agent can do in a chat

In a chat, the agent acts with the lower of two roles: its own project role, or your role. For example, an agent with the **Editor** role cannot change records when a **Viewer** chats with it. See [Roles and permissions](/docs/agents/permissions).

The agent can only use the tools that are on in [Tools and access](/docs/agents/tools-and-access). When something is outside its tools, the agent says so.

## Good to know

* A message can have up to 10,000 characters.
* The agent uses [credits](/docs/product/workspaces/credits) for each reply. When the credits of the workspace are low or used up, the message box shows a warning.
* To test a new agent, ask it a few questions in the chat. The answers show how it reads its instructions.

## Related

* [Instructions and files](/docs/agents/instructions)
* [Triggers and results](/docs/agents/triggers)
* [Channels](/docs/agents/channels)
* [Coding sessions](/docs/agents/coding-sessions)

---

## Related pages

- [Agents](https://nocodb.com/docs/agents.md): NocoDB agents are AI agents that work in a project: they read and change your tables, documents and code, answer in chat, and run on their own on a trigger.
- [AI Agents](https://nocodb.com/docs/agents/ai-agents.md): NocoDB is a no-code AI agent builder for business: AI agents that work on your tables and documents, answer in chat, and run agentic workflows on triggers.
- [Create an AI Agent](https://nocodb.com/docs/agents/create-agent.md): How to create an AI agent in NocoDB: describe the job in a setup chat or pick a template, then review and turn it on. NocoAI can also build it.
- [AI Agent Use Cases and Templates](https://nocodb.com/docs/agents/use-cases.md): AI agent use cases and examples for sales, customer service, marketing, operations and project management: 13 NocoDB templates to start from.
- [Instructions and Files](https://nocodb.com/docs/agents/instructions.md): Write the instructions of a NocoDB agent as a brief for a teammate, mention tables and documents with @, and attach files that the agent reads on every run.
- [Tools and Access](https://nocodb.com/docs/agents/tools-and-access.md): Set the AI agent tools of a NocoDB agent: what it can read and change in tables, records, documents and the web, its project role and its managed machine.
- [AI Agent Skills](https://nocodb.com/docs/agents/skills.md): Turn on AI agent skills in NocoDB: reusable instructions from the project, workspace or organization catalog that an agent loads when a task needs them.
- [Triggers and Results](https://nocodb.com/docs/agents/triggers.md): Build an AI agent workflow in NocoDB with triggers: a schedule, record changes, comments, forms or webhooks. Send the results to chat, email or Slack.
