Vibe Coding
Back to Multica

Multica / Workspaces and Teams

Comments & Mentions

Collaborate on issues - comments, replies, @mentions, emoji reactions, and trigger agent work in comments.

Comments & Mentions key concepts infographic
Comments & Mentions key concepts infographic

Overview

Each issue has a comment area. You can post comments, reply to others, name members or agents with @, and add emoji reactions—the same things you do in familiar task management tools. The only difference is: @ an agent will automatically trigger it to start working.

Leave a comment

Write content in the input box at the bottom of the issue details page, click Send, and the comment will immediately appear in the comment stream. Comments support Markdown - titles, lists, code blocks, and links all work.

Reply to a comment

Click the reply in the upper right corner of any comment, and a nested input box will expand below the comment. Replies you write will appear as children of this comment, forming a conversation thread. You can continue to reply after replying, unfolding layer by layer.

What you see in the issue list is only the number of top-level comments. Only by clicking on the issue can you see the complete conversation tree.

Expressive reaction

You can add emoticons (such as 👍, 👀, 🎉) in the upper right corner of each comment to express your opinion quickly - there is no need to send a separate "+1" just for approval.

@mentions

Entering @ in the comment will pop up a prompt to select a member or agent. The other party's slug (such as @alice or @reviewer-bot) will be filled in after @. Mentioned people will receive a notification in their inbox.

If you mention an agent, it will be automatically triggered to start working - see Calling agents in comments for details.

If @ is used by the same person multiple times in the same comment, the other party will only receive one notification.

@all will notify the entire workspace

@all is a special target: it will push the notification to every member of the workspace. Both humans and agents can issue @all - this means that the triggered agent may also issue @all when reporting progress, and it needs to be reminded to use caution in the agent's instructions.

Use @all with caution. When there are many people in the workspace, a @all comment will instantly generate the same number of inbox notifications. Only use it on really important matters that everyone needs to know - not everyday trivial matters.

Quote issue

To link to another issue, select it in the comment's mention selector. Multica will save the issue link as an explicit MUL-123 mention link. Issue links are only cross-references: members are not notified and agents are not triggered.

Directly entering the bare issue key, such as MUL-123, will remain as normal text. In this way, branch names and paths in comments, such as feature/MUL-123, will not be rewritten.

Markdown bold follows CommonMark rules. When bold text ends with punctuation or closing quotation marks and is immediately followed by a Korean particle, the trailing ** may not be recognized. It is recommended to put the quotation marks outside the bold range:

"**무엇을 먼저 정해두고 시작할지**"가

instead of:

**"무엇을 먼저 정해두고 시작할지"**가

Edit and delete comments

Only the author of the comment can edit or delete his or her comment.

Deleting a comment will also delete all replies below it (including replies to replies). If you just want to change the content, use the edit function.

Editor's comment: Adding @ will not trigger the agent. The trigger occurs at the moment when the comment is created - if you later modify the comment content to add a new @, or change the @ object, the system will not re-send the notification, nor will it wake up the agent. To summon an untriggered agent, post a new comment @ it.


So far, we have been talking about the "human world" - workspace, members, issues, projects, and comments. If you’re familiar with products like Linear or Jira, the content so far shouldn’t seem unfamiliar.

But Multica’s core feature hasn’t arrived yet: making agents first-class citizen members of the workspace. At the beginning of the next chapter, we officially get to know this new species.

Next step