mirror of
https://gh-proxy.org/https://github.com/klinsmaya/multica.git
synced 2026-11-10 18:36:45 +08:00
Naiyuan QingandClaude Fable 5
e395fb8744
Complete rework of the docs site, in three passes squashed into one change: 1. P0 fact corrections across the core-loop pages (agent access model, comment triggers and coalescing, issue lifecycle, offline/queue semantics, task states and retries, dispatch via realtime push). 2. Chinese rewrite as the authoring language: final 12-group IA, new "Core concepts" and "Put agents to work" pages, curated welcome page, permanent-UI quickstart (no onboarding-wizard dependency), operator reference restored (CLI command reference, webhook response codes, task state/timeout tables, config set keys, upgrade notes). 3. Verification and sync: every load-bearing claim re-checked against current main with file:line evidence (migration 103 auto-backfill, CLI-only trigger toggling, duplication semantics, COOKIE_DOMAIN, GitHub App variables, Qwen Code as the 17th provider); register standards applied to all 39 pages; en/ja/ko synced from zh with same-language heading anchors (verified, zero dead links); 17 product screenshots plus 2 diagrams wired in. Supporting fixes: i18n middleware no longer swallows /images assets, sidebar folder indent survives custom link padding, unused editorial components removed. Co-authored-by: Claude Fable 5 <[email protected]>
63 lines
3.3 KiB
Plaintext
63 lines
3.3 KiB
Plaintext
---
|
|
title: Comments
|
|
description: Add information, reply to discussions, and @-mention members or agents on an issue, keeping a complete collaboration record.
|
|
---
|
|
|
|
import { Callout } from "fumadocs-ui/components/callout";
|
|
|
|
Comments are where ongoing collaboration on an [issue](/issues) happens. Members and agents add background, ask questions, and post results here, and the full context is still there the next time the issue is opened.
|
|
|
|
## Post comments and replies
|
|
|
|
Type into the issue's activity area and send to create a comment. Comments support formatting, code blocks, links, and attachments.
|
|
|
|
Replying to a comment forms a discussion thread. Replies can nest further, but they all stay under the same top-level discussion.
|
|
|
|
## Resolve a discussion
|
|
|
|
When a question reaches a conclusion, mark the whole discussion as resolved, or set one reply as the conclusion; a discussion keeps only one conclusion at a time. Resolved discussions collapse but can still be expanded.
|
|
|
|
Replying in a resolved discussion reopens it automatically.
|
|
|
|
## @-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 task 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.
|
|
|
|
<Callout type="info">
|
|
@-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](/mentioning-agents).
|
|
</Callout>
|
|
|
|
## Subscriptions and the inbox
|
|
|
|
Members who comment subscribe to the issue automatically, and later activity and @-mentions land in the [inbox](/inbox); you can also subscribe or unsubscribe manually at the top right of the issue. See [Inbox and subscriptions](/inbox) for the full subscription sources and notification rules.
|
|
|
|
## Reactions
|
|
|
|
Add an emoji reaction to a comment to acknowledge, 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 `owner`s and `admin`s 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 tasks too; the trigger preview shows under the input before you save.
|
|
|
|
<Callout type="warning">
|
|
Deleting a comment cannot be undone. Deleting a top-level comment deletes every reply under it. If the content is wrong, edit it instead.
|
|
</Callout>
|
|
|
|
## Next steps
|
|
|
|
- [@-mention agents in comments](/mentioning-agents) — how @-mentions, replies, and assignment differ.
|
|
- [Inbox and subscriptions](/inbox) — manage the work activity you need to follow.
|
|
- [Assign issues to agents](/assigning-issues) — make an agent the issue's assignee.
|