Comments and mentions
Collaborating under an issue â comments, replies, `@` mentions, reactions, and triggering agents from a comment.
Every issue has a comment thread. Post comments, reply to someone, @ a member or an agent, add reactions â the same moves you make in any task manager you've used. The one difference: mentioning an agent with @ triggers it to start working.
Posting a comment
Type into the input at the bottom of the issue detail page and hit Send. The comment appears in the thread immediately. Comments support Markdown â headings, lists, code blocks, links, all available.
Replying to a comment
Click Reply on the top-right of any comment to open a nested input underneath it. Your reply is displayed as a child of that comment, forming a conversation thread. Replies can have their own replies, nesting as deep as you need.
The issue list shows only the top-level comment count; opening the issue reveals the full conversation tree.
Reactions
Each comment has a reaction button in the top-right for quick signals (đ, đ, đ) â no need to post a "+1" comment to agree.
@ mentions
Typing @ in a comment opens a picker. Choose a member or an agent, and @ plus the target's slug gets inserted (@alice or @reviewer-bot). The mentioned party gets a notification in their inbox.
If you mention an agent, it triggers automatically â see Mentioning agents in comments.
Mentioning the same person multiple times in one comment still produces only one notification.
@all notifies the entire workspace
@all is a special target: it pushes a notification to every member of the workspace. Both people and agents can use @all â which means an agent reporting progress could also @all, so remind agents in their instructions to use it sparingly.
Use @all carefully. In a larger workspace, a single @all generates that many inbox notifications instantly. Reserve it for things everyone genuinely needs to know â not day-to-day updates.
Editing and deleting a comment
Only the author of a comment can edit or delete it.
Deleting a comment also deletes every reply under it (including replies to replies). To change content only, use edit instead.
Adding an @ while editing a comment does not trigger the agent. The trigger fires the moment a comment is created â editing to add a new @, or changing the target, does not send a new notification or wake the agent. To summon an agent you missed, post a new comment that @s it.
Everything we've covered so far is "the human world" â workspaces, members, issues, projects, comments. If you've used Linear or Jira, none of it should feel unfamiliar.
But Multica's defining trait hasn't entered the picture yet: treating agents as first-class members of a workspace. That's what we turn to next.
Next
- Agents â what they are, and how they differ from people
- Mentioning agents in comments â use
@in a comment to start an agent