Replying and Proving Fixes

Every piece of feedback in a project has its own thread where you can respond, ask questions, and show that an issue has actually been handled. Attaching proof — a screenshot, a short clip, or a note explaining the change — turns a claim of "fixed" into something the reviewer can confirm at a glance.

Replying to a Comment

Open any pin, note, or video comment to see its thread. Type your reply and post it — everyone with access to that comment sees it in order, so a conversation about a single issue stays in one place instead of scattered across emails or chats.

Who can reply depends on the project role:

•Teammates and admins can reply on any comment they can see.

•Clients can reply on their own comments to add detail or respond to a fix.

•Guests who left anonymous feedback and gave an email receive follow-up when a thread continues.

Attaching Proof-of-Fix

When you finish work on an issue, a plain "done" is easy to doubt. Instead, back your reply with evidence so the reviewer can verify without hunting through the site.

1.Open the comment you worked on and start a reply.

2.Attach your proof — an image showing the corrected result, or a short screen recording that walks through the fix in action.

3.Add a note describing what changed, then post the reply.

4.Move the comment to completed so it's clearly waiting on the reviewer's confirmation.

A short video is the most convincing proof for anything interactive — hover states, form validation, or a bug that only shows up mid-flow. It saves the reviewer from reproducing the steps themselves.

When a Fix Needs More Proof

If a reviewer isn't satisfied, they can reopen a comment rather than mark it resolved. When they do, they can leave a quick reason so you know what's still off. Two phrasings people reach for most often are ready to use in one tap:

•"Please add proof" — the change may be done, but the thread doesn't show it yet.

•"This isn't working, please check" — the issue still appears on their end.

Reply on the same thread with the additional evidence and set the comment back to completed. Keeping everything on one thread means the full history — original feedback, your fixes, and the reviewer's responses — stays together.

Confirming or Reopening

After proof is posted, the reviewer has the final say. They can confirm the feedback was addressed, which marks the comment resolved, or reopen it to send it back for another pass. This back-and-forth continues on the thread until both sides agree the issue is closed.

AI coding agents connected through the MCP server can also reply on threads and attach proof — for example, linking the commit that fixed an issue — then mark the comment completed, exactly as a teammate would.

Related topics: Track Feedback to Done, Record Screen Feedback, Fixing Feedback with an AI Agent.