Comments are the conversation on a task. Next to them sits the activity trail, which records what changed without anyone having to write it down. This page covers both, plus mentions, agent recommendations and the board-wide activity log.
Open a task and scroll to Comments on the Details tab. The composer is the same rich Markdown editor used for notes, so headings, lists, code blocks and links all work, and the result is stored as Markdown.
Press Enter to send. A comment can be up to 10,000 characters.
Attach a file with the paperclip: From your computer uploads one, From board files picks a file already on the board. You can also drop a file straight onto the composer.
Commenting needs a board role of Editor or Admin. A Viewer, or a site GUEST, can read the conversation but not add to it.
Mentioning a person sends them a You were mentioned notification, whether or not they are on the task. Mentioning a team notifies every member of that team, the same way.
Everyone assigned to the task and everyone watching it gets a New comment notification when a comment arrives, so you only need a mention to reach someone who is neither. Nobody is notified about their own comment.
Mentions also work in a task's description, and in notes. A @name added to a description fires the same mention notification, and note mentions have their own notification type. See Notifications for how to choose which of these reach you, and where.
You can also link a note from the composer by typing its name, which creates a working link to it.
Hover a comment you wrote for its edit and delete controls. An edited comment is marked edited for everyone. Deleting asks for confirmation first.
Comments written by AI have no human author, so a site OWNER or ADMIN, or a board Admin, gets a separate control to delete them. That delete removes the comment and any recommendation attached to it.
An agent replying on a task can attach a single suggested change to its comment instead of just describing it. The comment then carries a button such as Move to In review, Set priority: High, Apply tag: blocked or Add subtask.
Recommendation
What accepting it does
Move
Moves the task to the suggested list.
Mark complete
Completes the task.
Set priority
Sets the suggested priority.
Apply tags
Replaces the task's tags with the suggested set.
Assign
Sets the task's members.
Set dates
Sets the start date, the due date or both.
Add subtask
Adds a checklist item with the suggested text.
Accepting runs the change as you, through the same path as doing it by hand, so your board permissions apply and the activity trail records you as the one who made the change. You can also dismiss the recommendation and leave the task alone.
Every task has an Activity section on Details and an Activity tab of its own. It records the things people and agents did rather than said: created, moved, completed, title and description changes, member, tag, watcher and priority changes, dates, estimates, cover colour, checklist items, comments added, edited and removed, and dependencies.
Agent work is recorded in the same stream, including the pages an agent read from the web, the blocking questions it asked and the moment it proposed a task as done. Entries made by an automation are attributed to Automation, and background jobs to System.
For the whole board, open the board page menu and choose Activity.
The dialog lists every logged change with the date, who made it, the entity, the action and what changed. Filter it by date range, by user, and by entity type: tasks, lists, boards, tags, comments, notes or dependencies.
The activity log is also what feeds board digests and the Overseer feed.
Self-hosted only
How long activity rows are kept is set in Settings > Server > Data Retention, under Audit Logs.
Comments and mentions
Comments are the conversation on a task. Next to them sits the activity trail, which records what changed without anyone having to write it down. This page covers both, plus mentions, agent recommendations and the board-wide activity log.
Writing a comment
Open a task and scroll to Comments on the Details tab. The composer is the same rich Markdown editor used for notes, so headings, lists, code blocks and links all work, and the result is stored as Markdown.
Press Enter to send. A comment can be up to 10,000 characters.
Attach a file with the paperclip: From your computer uploads one, From board files picks a file already on the board. You can also drop a file straight onto the composer.
Commenting needs a board role of Editor or Admin. A Viewer, or a site GUEST, can read the conversation but not add to it.
Mentions
Type
@and pick a person or a team.Mentioning a person sends them a You were mentioned notification, whether or not they are on the task. Mentioning a team notifies every member of that team, the same way.
Everyone assigned to the task and everyone watching it gets a New comment notification when a comment arrives, so you only need a mention to reach someone who is neither. Nobody is notified about their own comment.
Mentions also work in a task's description, and in notes. A
@nameadded to a description fires the same mention notification, and note mentions have their own notification type. See Notifications for how to choose which of these reach you, and where.You can also link a note from the composer by typing its name, which creates a working link to it.
Editing and deleting
Hover a comment you wrote for its edit and delete controls. An edited comment is marked edited for everyone. Deleting asks for confirmation first.
Comments written by AI have no human author, so a site OWNER or ADMIN, or a board Admin, gets a separate control to delete them. That delete removes the comment and any recommendation attached to it.
Agent recommendations
An agent replying on a task can attach a single suggested change to its comment instead of just describing it. The comment then carries a button such as Move to In review, Set priority: High, Apply tag: blocked or Add subtask.
Accepting runs the change as you, through the same path as doing it by hand, so your board permissions apply and the activity trail records you as the one who made the change. You can also dismiss the recommendation and leave the task alone.
Summarizing a long thread
When AI is configured for the workspace, the Comments header carries Summarize. It posts an AI Summary of the conversation so far.
The summary is yours alone
Only you see the summary, and other members are not notified about it.
The activity trail
Every task has an Activity section on Details and an Activity tab of its own. It records the things people and agents did rather than said: created, moved, completed, title and description changes, member, tag, watcher and priority changes, dates, estimates, cover colour, checklist items, comments added, edited and removed, and dependencies.
Agent work is recorded in the same stream, including the pages an agent read from the web, the blocking questions it asked and the moment it proposed a task as done. Entries made by an automation are attributed to Automation, and background jobs to System.
Board activity
For the whole board, open the board page menu and choose Activity.
The dialog lists every logged change with the date, who made it, the entity, the action and what changed. Filter it by date range, by user, and by entity type: tasks, lists, boards, tags, comments, notes or dependencies.
The activity log is also what feeds board digests and the Overseer feed.
Self-hosted only
How long activity rows are kept is set in Settings > Server > Data Retention, under Audit Logs.
Comments in notes
Notes have their own comment threads, separate from task comments, with the same mention behaviour. See The note editor.
Reacting to comments automatically
Three automation triggers fire on comments:
Use them to reopen a completed task when a new comment arrives, to ping the assignee, or to keep an audit trail somewhere else. See Triggers.
Related