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

# Comments and change requests

> How people discuss a canvas, ask the agent for a change, and how the agent hears about it.

People can comment on a canvas while it is active. A comment can be about the whole canvas or about one component. People can also ask the agent that built the canvas to change it. To ask the canvas's own agent instead, see [The canvas's agent](https://docs.canvasview.dev/people/canvas-agent.md).

## Comment on a canvas

1. Open the canvas and select **Comments** in the bar.
2. Write your comment. Comments are plain text, up to 2,000 characters.
3. Under **On**, choose **The whole canvas** or a component.
4. Select **Post comment**.

You can also select the comment icon on a component to see and add comments on it. Select **Reply** to answer a comment. Replies are one level deep: a reply to a reply joins the same thread.

Everyone who can open the canvas sees its comments, live. Viewers can read comments but not add them. See [Canvas roles](https://docs.canvasview.dev/account/sharing-and-access.md#canvas-roles). A canvas holds up to 500 comments.

## Ask the agent for a change

Select **Ask the agent to change the canvas** before you post. This asks the agent that built the canvas, through your organization's events. The comment becomes a change request and shows **Request for the agent**. While the agent has not responded, it shows **Waiting for the agent**, and the **Comments** button shows how many requests are waiting.

A request stops waiting when the agent replies in its thread, when the agent changes the canvas after it, or when the thread is resolved.

## Resolve a thread

Select **Resolve** on a thread to close it, or **Reopen** to open it again. The person who started the thread can resolve it, and so can any editor or admin of the canvas: its owner, Admins of its organization, members when it is shared with the organization, and anyone invited as an editor or admin. Resolved threads are hidden under **Show resolved**.

## Who wrote a comment

* On a canvas that needs sign-in, a comment carries the person's CanvasView name.
* On a link-access canvas, a comment carries the name the person typed.
* Comments from the agent are marked **Agent**.

## How the agent hears about comments

Comments create events in your organization's event log, which your agent can read or receive by [webhook](https://docs.canvasview.dev/developers/events-and-webhooks.md):

| Event | When |
| - | - |
| `change.requested` | A person asked the agent for a change. One event for each request. |
| `comment.added` | People commented. At most one event per canvas every 5 seconds. |

Events say which canvas changed, not what was said. The agent reads the comments with `list_comments` and replies with `add_comment`, on the whole canvas, on a component, or in a thread. The agent's own comments create no events.

## When a canvas is read-only

An answered, closed or expired canvas takes no new comments. Its comments stay visible while the canvas can be opened, and are deleted with the canvas. See [Canvas lifetime](https://docs.canvasview.dev/account/canvas-lifetime.md).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.