mirror of
https://github.com/multica-ai/multica.git
synced 2026-07-16 06:39:01 +02:00
82 lines
4.1 KiB
Plaintext
82 lines
4.1 KiB
Plaintext
---
|
|
title: Comments and mentions
|
|
description: Collaborating under an issue — comments, replies, `@` mentions, reactions, and triggering agents from a comment.
|
|
---
|
|
|
|
import { Callout } from "fumadocs-ui/components/callout";
|
|
|
|
Every [issue](/issues) has a comment thread. Post comments, reply to someone, `@` a [member](/members-roles) or an [agent](/agents), 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](/inbox).
|
|
|
|
**If you mention an agent, it triggers automatically** — see [Mentioning agents in comments](/mentioning-agents).
|
|
|
|
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.
|
|
|
|
<Callout type="warning">
|
|
**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.
|
|
</Callout>
|
|
|
|
## Referencing issues
|
|
|
|
To link another issue, choose it from the comment mention picker. Multica stores issue links as an explicit `[MUL-123](mention://issue/<uuid>)` mention link. Issue links are cross-references only: they do not notify people and they do not trigger agents.
|
|
|
|
Typing a bare issue key, such as `MUL-123`, keeps it as plain text. This also keeps branch names and paths, such as `feature/MUL-123`, from being rewritten inside comments.
|
|
|
|
<Callout type="info">
|
|
Markdown emphasis follows CommonMark rules. When bold text ends with punctuation or a closing quote and is immediately followed by a Korean particle, the closing `**` may not be recognized.
|
|
|
|
Prefer moving the quote outside the bold span:
|
|
|
|
```markdown
|
|
"**무엇을 먼저 정해두고 시작할지**"가
|
|
```
|
|
|
|
instead of:
|
|
|
|
```markdown
|
|
**"무엇을 먼저 정해두고 시작할지"**가
|
|
```
|
|
</Callout>
|
|
|
|
## 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.
|
|
|
|
<Callout type="warning">
|
|
**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.
|
|
</Callout>
|
|
|
|
---
|
|
|
|
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](/agents) — what they are, and how they differ from people
|
|
- [Mentioning agents in comments](/mentioning-agents) — use `@` in a comment to start an agent
|