Comments
Discuss a task in threaded comments — one level of replies, links, and @-mentions that notify teammates.
Every task has a comments thread for discussion, questions, and decisions. Open a task (View) and the thread sits below the task's notes.
Adding and threading
- Write a comment in the box and post it. Comments show the author's avatar, name, and a relative timestamp.
- Reply to a comment to start a thread. Threads are one level deep — a reply can't itself be replied to, which keeps long discussions readable. A reply is shown indented under its parent with a "Replying to …" label.
- You can edit and delete your own comments. An edited comment is marked
(edited). Deleting a top-level comment also removes its replies.
Links
Any http(s) URL you type is automatically turned into a clickable link that opens in a new tab. You don't need any special syntax — just paste the URL.
@-mentions
Type @ to bring up a picker of your workspace team members, filterable by name or email. Pick someone (arrow keys + Enter, or click) to insert the mention; it renders as a highlighted @Name in the posted comment.
- The mentioned person gets a dedicated "you were mentioned" notification, separate from the generic new-comment notification (so they're not notified twice).
- Mentions work in new comments, replies, and when editing.
Mentions are a team feature. In a personal workspace there are no other members, so the @ picker doesn't appear — comments, replies, and links still work normally.
Notifications
Comment activity creates notifications:
| You'll be notified when… | Who is notified |
|---|---|
| A new top-level comment is posted on a task | The task owner and its assignees |
| Someone replies to your comment | The comment's author |
| You're @-mentioned | Each mentioned member |
The person taking the action is never notified about their own comment, and an @-mentioned member receives only the mention notification for that comment.
Who can comment
Comment access follows task access: the task owner, anyone the task is assigned to, and — for a task in a team workspace — any member of that team can read and post comments. People without access to the task can't see or add comments.
Comments via MCP
Everything on this page is also available programmatically through the MCP server — list_comments, create_comment, update_comment, and delete_comment. The same rules apply: one-level replies, author-only edit/delete, task-access enforcement, and the same notifications (including @[Name](userId) mentions). MCP-created comments also record an activity-feed event attributed to the API key.
Related
- Tasks — where comments live.
- Teams — who can see and be mentioned in a team workspace.
- Activity feed — in-app comments are discussion, not activity events; comment actions taken via MCP are recorded there for API-key attribution.
- MCP server — read and write comments from external tools.