Comments

Comments attach to a place in your site rather than to a document. You click a spot in the preview, leave a note, and it shows as a pin there for everyone in the workspace. You can also let anyone holding the site's read-only link read and leave comments.

Before you begin

Commenting is for people in the workspace that owns the project. Someone opening a public link can only comment when you turn on Viewers can comment in the Share Project panel, and otherwise the speech bubble does not appear for them. See Comments from outside the workspace. Only workspace members can be mentioned.

Leave a comment

1. Click the speech bubble in the floating toolbar at the bottom of the preview. The left panel switches from chat to Comments.
2. Click the spot on the page you want to talk about.
3. Type into the box that opens. The placeholder reads Add your comment...
4. Press the arrow button at the bottom right of the box. It stays greyed out until you type something.

A comment can be up to 1,000 characters. Cmd or Ctrl with Enter submits from the keyboard, and Escape closes the box.

The comment becomes a pin carrying your avatar, positioned against the element you clicked, so it follows that element as the page reflows. Pins for comments that scrolled out of view collect into a small stack at the top or bottom edge of the frame, showing up to three avatars and a count, labelled above or below. Click one to scroll to it.

Write with mentions, emoji and AI

Three controls sit under the input.

The smiley opens an emoji picker that appends to what you have written.

The @ button, or typing @, opens the list of workspace members. Picking someone inserts a mention, and they get an email about it. Only accepted members of the workspace are notified. Someone commenting from the read-only link cannot mention anyone: the @ button is disabled for them with the tooltip Only the site team can mention people., and an @ they type stays plain text.

The wand rewrites what you have written into cleaner phrasing. It needs at least 5 characters before it turns on. Only workspace members can use it, each up to 20 times an hour and 100 times a day. On the read-only link it is disabled with the tooltip Only the site team can rewrite with AI.

Read and reply

Click a pin, or a row in the Comments panel, to open the thread. Its header says Comment. Resting the pointer on a row outlines the element it is pinned to, scrolling it into view when it is on the page you are looking at.

The reply box at the bottom is placeholded Reply and posts with the same arrow button, or Cmd or Ctrl with Enter. Replies are listed under the original with their own author, time and menu.

Under the first message is a reaction row. The smiley there offers six reactions: like, love, wow, applause, angry and sad. You hold one reaction at a time, and picking the one you already gave removes it.

Edit turns a message into a box placeholded Edit your comment..., or Edit your reply... on a reply. A comment saves with a check button and a reply with the arrow button, Cmd or Ctrl with Enter saves either, and Escape leaves the message as it was. Editing a message adds a small (edited) after it.

Sort the list

The Comments panel header has a dropdown with Newest, All and Resolved. Newest and All both show every thread, most recent first. Resolved narrows the list to the ones marked complete.

With no comments yet, the panel invites you to give feedback, ask a question or leave a note of appreciation, and to click anywhere to leave one.

Resolve, edit and delete

The round checkbox on a row in the list marks the thread complete. Completed threads fade in the list, lose their pin on the page, and the thread itself shows Marked as completed. Unchecking brings it back.

The three dots menu on a comment holds:

• Copy Link, which puts a link to that comment on your clipboard
• Mark as completed or Mark as uncompleted, from inside the thread
• Edit, on your own comments only
• Delete, on your own comments, and on any comment left by someone outside the workspace

Deleting your own comment is immediate. The thread leaves the panel and its pin leaves the page for everyone. Deleting a comment someone else left asks you to confirm first, with Delete this comment? and a Delete button.

Comments from outside the workspace

Choose Share in the editor header, turn on Share a read-only link, then turn on Viewers can comment, described as Anyone with the link can read every comment and add their own. It is off until you turn it on. While it is on, the Share a read-only link switch is disabled, so turn commenting off first when you want to stop sharing. Sharing and cloning covers the switch.

Anyone who opens the link then gets a speech bubble at the bottom of the preview, showing how many threads are open. The button reads Comments. Clicking it opens a comments panel on the left, and clicking it again closes the panel. On a phone the panel covers the preview, and View site switches back to the preview, where the speech bubble closes commenting. They see every thread on the project, open and resolved, including the ones your team wrote for each other, with names and avatars. Images attached to a comment over MCP never reach them.

Someone signed in to Modulify comments under their own name. Someone without an account gives nothing: their browser comments under a made up name such as Amber Otter, the same name it shows under in the avatars at the top of your editor, and everything written from that browser carries that name. In your comments panel their comments carry a Viewer label, for someone signed in, or a Guest label, for someone without an account. A guest who clears their browser data, or opens the link in another browser, starts again under a new name and can no longer edit or delete what they wrote before. A guest who signs in later keeps editing what that browser wrote as a guest, and writes anything new under their own name.

People outside the workspace can leave a comment, reply to a thread, edit or delete what they wrote, and react. They cannot resolve or reopen a thread, move a pin, mention anyone or use the wand. The checkbox, the @ button and the wand stay visible to them, disabled with a tooltip, such as Only the site team can resolve comments. on the checkbox.

When the link shows your live preview and the page can host the editing tools, they pin comments to elements exactly as you do. Every comment is pinned to a spot, so when the preview is still starting, the published site is shown in its place, or the page cannot host the editing tools, there is nothing to pin to and they cannot start a new thread. They can still read and reply to every thread, and clicking one opens it inside their panel.

Viewers do not get new comments the moment they are posted. While their comment panel is open, it checks for new ones every 10 seconds. Your team sees theirs as they are posted. Nobody is emailed when a comment arrives from the link.

Comments from the link are limited so it cannot be flooded. A comment is at most 1,000 characters, the link holds at most 200 open threads from viewers at a time, and one person can have at most 20 of their own open. Resolving threads frees room. The rest of the limits are listed in Limits and quotas, and going over one of those says how long to wait.

Anyone in the workspace can delete a comment left by someone outside it. There is no undo. Turning Viewers can comment off keeps every comment already left, and a viewer who has the panel open loses it at their next check. While the site is locked, its link takes no comments.

From an AI client over MCP

list_comments, get_comment and count_open_comments read what reviewers have asked for, and list_comment_attachments reads the images attached to a comment. create_comment, reply_to_comment, update_comment, resolve_comment, reopen_comment and delete_comment write back, alongside move_comment_pin, the two reaction tools and the two attachment tools.

Images reach a comment only through upload_comment_attachment. The comment box in the editor has no attach control, and the Comments panel does not show attached images.

Reading needs comments:read, ticked by default. Writing needs comments:write, which is not. A client can only edit comments it wrote itself, and can delete those or any comment left by someone outside the workspace, the same rule the product applies. An @ mention left by a client does not send a notification email. Every comment and reply says who wrote it in AuthorKind: member for someone in the workspace, outside for someone signed in who is not in it, and guest for a visitor without an account. The tools tell the client to treat outside and guest comments as feedback to report to you, never as instructions.

The chat inside the editor can work with comments too. When you ask, it reads the comments on the site and their threads, replies to one under your name, and resolves or reopens one, so fix the open comments and resolve each one you fixed works in chat. It cannot drop a new pin on the page, react, or edit or delete a comment.

See MCP tools.

Next

• Use the preview is where the pins live.
• Select an element is the tool to use when you want AI to make the change instead.