Reply to a comment as a thread

Internal comments can now be replied to directly, turning a single comment into a small thread instead of a flat list of separate notes. This article covers the Reply action, how threading and indentation work, the notification the original author gets, and the @mention pill in the composer.

This builds on the existing internal comments feature — if you haven’t used comments yet, start with Add internal comments. This article is specifically about replying to an existing comment as a thread.

Starting a reply

Every internal comment card now has a Reply action. Click it on any comment to open the composer targeted at that comment instead of starting a new top-level comment.

While you’re replying:

• The composer stays focused on that one thread — your reply is attached to the comment you clicked Reply on.
• If you switch to a different conversation, the reply target is cleared. Comment text you were drafting as a top-level comment is preserved separately from a reply-in-progress, so starting a reply doesn’t wipe out an unrelated draft you were writing.

Replies are one level deep

Threading in comments is intentionally simple: a reply always attaches to the thread root, not to the comment you clicked on.

• Reply to a top-level comment → it nests under that comment.
• Reply to a reply → it also nests under the original root comment, not under the reply itself.

In other words, there’s no infinite nesting. Every comment card shows at most one root and its flat list of replies underneath — there’s no reply-to-a-reply-to-a-reply chain to scroll through.

How replies render

A reply renders indented underneath its thread root, with a “replied” label in its header so it’s visually distinct from a fresh, top-level comment. This keeps related back-and-forth grouped together in the Comments panel and in the conversation timeline, instead of scattering across the message stream in chronological order.

Notifying the original author

When you reply to a comment, the author of the root comment gets a notification that someone replied to their comment. This works the same way as an @mention notification — it shows up in the same place, respects the same notification preferences, and behaves the same way when clicked through.

A few things worth knowing:

• The notification goes to the root author, even if you’re replying to someone else’s reply further down the thread.
• If your reply also @mentions someone, they get mentioned as usual — replying and mentioning are independent; you can do either, both, or neither.

@mention pills in the composer

While composing a comment or a reply, typing @ followed by a teammate’s name highlights the match with a pill as you type, so you can see at a glance which @mentions will actually resolve to a real teammate versus plain text that happens to start with @.

This works the same in both the top-level comment composer and the reply composer — it’s the same mention behavior you already know from regular comments, just available while replying too.

Summary

• Click Reply on a comment card to respond to it directly.
• Replies always attach one level deep, to the thread root — never to another reply.
• Replies render indented under the root, labeled “replied.”
• The root comment’s author is notified when someone replies to their comment.
• Typing @ in the composer shows a pill for recognized teammates, in both new comments and replies.

For the basics of adding a comment in the first place, see Add internal comments.