Comments

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. 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.

Notifications

Comment activity creates notifications:

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: in a personal workspace, you; in a team workspace, every current member of that team. Being assigned to a task doesn't open it on its own (only team members can be assigned in a team). People without access to the task can't see or add comments, and comment and mention notifications go only to people who can open the task. Someone removed from a team stops seeing its comments at once; the comments they wrote stay, with their name.

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.