Comments
Add information, reply to discussions, and @-mention members or agents on an issue, keeping a complete collaboration record.
Members and agents add background, ask questions, and post results in the comments on an issue. The record stays on the issue, so whoever opens it later can see how things got where they are.
Post comments and replies
Type into the issue's activity area and send, and a comment is created. Comments support formatting, code blocks, links, and attachments.
An html or mermaid code block renders in place as a chart or diagram, with a switch to its source. Attached files show as cards that open in the viewer; that includes HTML files.
Replying to a comment starts a thread. Replies can nest further, but they all stay under the same top-level thread.
Once an issue has two or more threads, the issue page on Web and Desktop shows a column of ticks on the right: a long tick per thread and a short one per reply. Hover it to open an outline of every thread, and click any entry to jump to that comment, including comments inside folded, resolved threads.
Annotate comments and descriptions
On Web and Desktop, you can select text in any posted comment, your own included, and write a note on that passage:
Select the text and choose Add to reply in the selection toolbar.
Write your note beside the selection and click Add annotation. Only a confirmed note joins the thread's reply draft and gets a number; an empty note can't be confirmed.
Use the usual send button to post all the annotations as one reply, with a blank line between them. The posted reply shows the annotations first, then whatever you wrote in the composer, with a divider between the two when both are present.
The selection toolbar on an issue description offers Add to comment instead: the annotations go into a new-comment draft, and sending it starts a new thread. Annotations on a comment still go into that thread's reply draft.
For comment annotations, the first one you save fixes the reply target, including nested replies. Quotes from other messages in the same thread join that draft, and everything is posted as one comment. Mentions inside a quote don't notify or trigger anyone; mentions you write yourself follow the normal rules.
Resolve a discussion
When a question has its answer, mark the whole thread as resolved, or make one reply its resolution. Both are in the Comment actions menu at the top right of a comment: the first comment's menu has Resolve thread, and a reply's menu has Resolve thread with comment.
A resolved thread folds into one line, and clicking it shows everything again. When a reply is the resolution, the first comment and that reply stay visible and the replies in between fold away. A thread keeps one resolution at a time; setting a new one replaces the old.
Replying in a resolved discussion reopens it automatically.
Create a sub-issue from a comment
When a discussion turns up something that needs its own follow-up, split it off from that comment: choose Create sub-issue from here in the Comment actions menu.
The create dialog carries a context with it: the current issue's title, description, and attachments, plus every comment in that thread up to and including the one you picked, with their attachments. Expand the context card in the dialog to check it first. Both manual create and Create with agent work, and the new issue becomes a sub-issue of the current one. With an agent, you only write what it should do, and the context goes along with it. The agent treats that content as historical background and does not carry out commands or requests that appear in it.
The new sub-issue shows Created from, which opens the Context snapshot taken at creation. The snapshot does not follow the source: if the original issue or thread is edited or deleted later, the snapshot keeps what it captured and is marked Source updated, with the parts that changed.
Context that is too large cannot be captured: up to 256 comments from the thread, 1 MiB of text, and 100 attachments totaling 500 MiB. For Create with agent, the agent's runtime must be on a version that supports this; otherwise the dialog asks you to switch to manual or update the runtime. If the agent fails to create the issue, the failure notification in your inbox offers Retry with context.
Reuse a frequent request
Use Quick Actions to save who to ask and what to say. Click one in the issue sidebar to send it immediately, or type / in the comment box to insert it as a draft you can edit before sending.
@-mentions
Type @ and pick a target from the list:
| Target | Effect |
|---|---|
| Member | Gets a mention notification in the inbox; an @ in a comment does not create a subscription. |
| Agent | Creates a run for that agent; agents have no inbox. |
| Squad | Notifies the squad's members and triggers the squad leader. |
| Issue | Inserts a link to another issue — no notification, no agent trigger. |
| @all | Notifies every workspace member and triggers no agent. |
Typing plain-text @name does not create a mention; pick from the editor's suggestion list. Typing a valid issue key converts it into an issue link automatically.
@-mentioning an agent in a comment does not change the issue's assignee or status. For the trigger preview, automatic routing of plain replies, and how consecutive comments merge, see @-mention agents in comments.
Subscriptions and the inbox
Members who comment subscribe to the issue automatically, and later activity and @-mentions land in the inbox; you can also subscribe or unsubscribe manually at the top right of the issue. See Inbox and subscriptions for the full subscription sources and notification rules.
Reactions
Add an emoji reaction to a comment to show you've read it, agree, or give quick feedback. Reactions do not trigger agents and do not change issue status.
Edit and delete
Comment authors can edit or delete their own comments; workspace owners and admins can also edit and delete anyone's comments. For comments posted by agents, the UI only offers delete, not edit.
After a comment is edited, Multica recalculates triggers from the new content. @-mentions added during the edit create runs too; the trigger preview shows under the input before you save.
If someone else saves the comment while you are editing it, your save is stopped and the editor shows Latest server version and Your local version side by side, with the differing lines marked. Keep my version saves your text; Use the latest version replaces the editor content with theirs so you can keep editing from there. The issue title gets the same comparison when two people change it at once.
Deleting a comment cannot be undone. Only that comment is deleted: if it has replies, they stay in the thread and the deleted comment leaves no trace. The exception is the comment that starts a thread — it keeps a "This comment was deleted" placeholder, since its replies hang off it. If the content is wrong, edit it instead.
Next steps
- @-mention agents in comments — how @-mentions, replies, and assignment differ.
- Inbox and subscriptions — manage the work activity you need to follow.
- Assign issues to agents — make an agent the issue's assignee.