# Comments > Pin comments on anything in your shadcn/ui design system's canvas, discuss them in threads with your team and share-link viewers, and let your agent address them. Canonical: https://www.shadcndesign.com/docs/ds-manager-comments Comments sit right on the canvas. You click a button variant, a color swatch, a type slot or a ProBlocks block, and a pin drops there with a thread attached. You, the people you share the system with and your agents can reply in the thread, make the change and resolve it. Comments come with every plan. They need a signed-in account and a system synced to it. Signed out, the Comments panel shows "Sign in to comment". ## Leave a comment 1. Press `C`, or click **Comments** in the top bar, left of **Share**. Comment mode starts: the cursor turns into a pin, and the Comments panel takes the place of the right rail's tabs. 2. Move the pointer over the canvas. A dashed outline and a name chip show what your comment will sit on. 3. Click. A pin drops there instead of the click reaching the component, and the **New comment** box opens. It names what you clicked and the page it is on. 4. Type your comment and press Enter, or click **Post comment**. Shift+Enter starts a new line. Press `Esc`, `C` or the **Comments** button again to leave comment mode. A pin can sit on: - a part of a component, for one variant or size, such as "Button · ghost" - a specimen card on a token page, such as a color or a type slot - a ProBlocks block - a section of a page - the canvas itself, when you click on nothing in particular Each pin shows the author's initials in their color. Pins stay attached to their element when you edit, zoom, scroll or resize the canvas. They show while comment mode is on or one of their threads is open. ### Comment on a whole page To comment on a page rather than one element, use the **Comment on this page** field at the bottom of the Comments panel. Its thread has no pin. ## Threads Click a pin to open its thread. The header names what the thread is on and holds three buttons: - **Resolve** (the check mark) marks the thread done. - **Delete thread** (the trash can) removes the thread and every comment in it. Only the system's owner and the person who started the thread see it. There is no confirm step. - **Close** closes the thread. Type in **Reply** and press Enter, or click **Send reply**, to answer. Each comment shows who wrote it and when, such as "Jordan Lee 2h", and "· edited" once it has been edited. A comment from the design agent reads "Agent via" and the name of the person who ran it. A comment from a coding agent over MCP names that agent, such as "Claude Code via Jordan Lee". To change your own comment, hover it and open **Comment actions**: - **Edit** opens the comment in a field. Click **Save** when you are done. - **Delete** removes it. Deleting the first comment of a thread deletes the whole thread. You can edit and delete only the comments you wrote. A resolved thread shows "Resolved by" with the name and time at the top. Click **Reopen** to make it open again. ## The Comments panel The **Comments** panel lists the system's threads, grouped by page. The page you are on comes first, and each group heading shows how many threads it holds. Each row shows the first comment and a line such as "2 replies · primary" or "Resolved by Agent · primary". Click a row to open its thread. When the thread is on another page, DS Manager opens that page first and the thread at its pin. A page comment opens next to its row. **Filter comments** (the icon at the top of the panel) has these options: - **Open**, **Resolved** or **All**. **Open** is the default. - **Only this page** hides the threads on other pages. - **Mark all as read** clears every unread thread. When a filter hides everything, the panel says "No resolved comments" or "No comments here", with **Show all comments** to clear the filters. Each row has a **⋮** menu, **Thread actions**, that works without opening the thread: - **Resolve**, or **Reopen** on a resolved thread. - **Delete thread**, for the system's owner and the person who started the thread. The menu shows when you hover a row, focus it with the keyboard, or select it, so it works on touch screens too. ### Threads whose element is gone When the element a pin sat on is no longer on the page, its thread moves to a **Not on the canvas** group, and the row reads, for example, "Button · ghost was removed". When a whole page is gone, such as the page of a custom component you deleted, its group heading ends in ", page removed". These threads open next to their row. Resolve or delete them from the row's **⋮** menu. ## Read and unread A thread is unread while it has a comment you haven't seen, written by someone else or by an agent, your own agents included. - A blue dot on the **Comments** button in the top bar means at least one thread is unread. - In the panel, an unread row has a dot and a bold first line. - Opening a thread marks it read. **Mark all as read** in the filter menu marks the rest. In the left navigation, every page with open threads shows a small comment icon and the number of open threads. DS Manager doesn't send emails or notifications about comments. New comments show up in the app without a reload. ## Comments on share links People you send a [share link](/docs/ds-manager-share) to can comment too, as long as they are signed in to DS Manager and **Signed-in users can comment** is ticked in the **Share** popover. The box is ticked by default, also for links you shared before comments arrived on October 20, 2026. To keep a link view-only, untick it. Turning it off, turning sharing off or clicking **Regenerate link** cuts viewers off at once. The threads stay in your system either way. In the shared view, the **Comments** button sits left of the light and dark switch and opens a Comments column on the right. Viewers can read, post, reply, resolve and reopen threads, and edit or delete their own comments. A viewer who isn't signed in gets a sign-in prompt instead. ## Ask the agent Pro and Lifetime accounts can hand a thread to the [design agent](/docs/ds-manager-agent) in the editor: - Type `@` in a comment or reply and pick **@agent**: Ask the agent. The comment box shows the hint "@agent asks the agent". - Or click **Ask agent** at the bottom of a thread. The Agent tab opens with "Address this comment." in the composer and a chip that names the comment, such as "Comment · Button · ghost". Press send. The agent doesn't start on its own. It makes the change, replies in the thread as "Agent" and resolves it. The turn uses your AI usage like any other. You can also ask the agent in chat to go through the comments. It knows how many threads are open on the page you are on and in the whole system. **@agent** and **Ask agent** don't show in the shared view. ## Coding agents over MCP A coding agent connected over the [MCP server](/docs/ds-manager-mcp), such as Claude Code or Cursor, can read and answer the same threads with `read_comments` and `write_comment`. Ask it to go through the open comments on your system: it reads them, makes the changes and resolves each thread with what it changed. An agent over MCP can start a comment on a whole page, reply, resolve and reopen. It can't drop a pin on an element. It can also comment on someone else's system through a share link, while that link allows comments, but it can't edit that system. ## Limits - A comment holds up to 2,000 characters. Past that, the field says how many to remove. - A system holds up to 500 open threads. Resolve some to open more. - One person can post 30 comments a minute, across all systems and including their agents. When a comment can't be saved, a "Comment not saved" toast says why. A fork or a duplicate starts with no comments. Deleting a system deletes its comments.