mirror of
https://github.com/multica-ai/multica.git
synced 2026-07-30 16:20:35 +02:00
c7e725ef66
* docs(autopilot): rename Routines → Autopilots to match product UI
Unify naming between docs and product. Sidebar label, URL route,
CLI command, and onboarding copy all call this feature "Autopilot";
the docs were the only surface that diverged. Aligning the docs to
the product (rather than the reverse) because the 830+ code-side
references would be a much larger rename to propagate.
- Rename routines.mdx / routines.zh.mdx → autopilots.mdx / autopilots.zh.mdx
- Update meta.json / meta.zh.json index entries (routines → autopilots)
- Drop the reconciliation note ("docs say Routines, CLI says autopilot")
that shipped in the original routines.mdx and the cli.mdx section header
- Update cross-references in cli, how-multica-works, tasks,
assigning-issues, chat, mentioning-agents, daemon-runtimes (EN + ZH)
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
* feat(onboarding): link to docs from key steps and starter tasks
Users who want to dig deeper now have a next hop from inside the flow
instead of having to dig through the help menu. Placed as secondary
links (muted, underline-offset-4) so they don't pull focus from the
primary CTA on each step.
Placement — one link per surface, placed in secondary regions:
- Welcome: "Learn how Multica works" below the subhead
- Questionnaire: "Learn how agents work" in the Why-we-ask aside
- Runtime aside (shared by desktop + web): "Learn about runtimes"
- Agent step: "Creating your first agent" in the About-agents aside
- StarterContentPrompt dialog: "Learn how Multica works"
Starter tasks (content/starter-content-templates.ts): added a single
"Learn about X" tail link per task, only on first occurrence of each
concept within a branch. 8 links on the agent-guided branch + 8 on
the self-serve branch + 1 on the welcome issue header (17 total).
URL scheme: absolute https://multica.ai/docs/{slug} throughout —
absolute so desktop (Electron) opens them in the system browser, and
the /en prefix is omitted because the docs middleware redirects it
away (English is the default, Chinese is /zh/).
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
* feat(landing): add docs link to footer and how-it-works section
Docs were previously reachable only from the in-app help menu. Landing
now surfaces them in two places, both locale-aware (/docs for English,
/docs/zh for Chinese):
- Footer Resources group: Documentation link was pointing at the
GitHub repo; replaced with the real docs URL
- How-It-Works section CTA row: added "Read the docs" between the
primary CTA and the GitHub link, same ghost styling
Locale resolution: href is picked per-render based on the landing's
current locale (cookie-driven via useLocale). The docs app itself
does not auto-detect language, so we must pick the right path
explicitly when emitting the link.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
* fix(onboarding): clean up Autopilot rename leftovers and link formatting
- comments.mdx: "not routine updates" → "not day-to-day updates"
(adjectival holdover now that the feature is renamed Autopilot;
zeroes out remaining "routine" mentions in user-facing docs)
- starter-content-templates.ts: move the arrow inside the markdown
link — "[text →](url)" instead of "→ [text](url)" — so the arrow
is part of the clickable region. 17 occurrences.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
* fix(onboarding): drop docs link from welcome screen and starter-content dialog
"Learn how Multica works" was showing up too often in the first two
screens users see. Keep the link in the post-import welcome issue
header (where users actually have time to explore); remove it from
the two earlier surfaces where it competes with the primary CTA.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
---------
Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
59 lines
3.5 KiB
Plaintext
59 lines
3.5 KiB
Plaintext
---
|
||
title: 在评论里 @ 智能体
|
||
description: 用 @ 提及一个智能体，让它在评论里看一眼——不改 assignee、不改 status，比分配轻。
|
||
---
|
||
|
||
import { Callout } from "fumadocs-ui/components/callout";
|
||
|
||
在 [评论](/comments) 里 `@` 一个 [智能体](/agents) 是更轻的触发方式——**不改 assignee、不改 status**，只是让智能体在当前 [issue](/issues) 上看一眼。和 [**分配**](/assigning-issues)（把智能体变成负责人、接管 issue）相比，@ 提及适合"帮我看看这段"、"换个角度分析一下"、"拉进来讨论两句"。
|
||
|
||
## 在评论里 @ 一个智能体
|
||
|
||
和 @ 成员一样——打 `@` 触发 picker，选一个智能体。发出评论后 Multica 会立刻给被 @ 的每个智能体入队一个 `task`，附带**这条评论**作为触发上下文。智能体收到任务时能读到：
|
||
|
||
- Issue 的完整信息（描述 + 所有历史评论）
|
||
- 触发评论本身——作为它本次工作的起点
|
||
|
||
`@mention` 的 Markdown 语法、picker 的用法、`@all` 的语义见 [**评论**](/comments)。
|
||
|
||
## 和分配的差别
|
||
|
||
同样是让智能体工作，但机制完全不同：
|
||
|
||
| 维度 | 分配 | @ 提及 |
|
||
|---|---|---|
|
||
| 改 `assignee` | ✓ | ✗ |
|
||
| 改 `status` | ✗ | ✗ |
|
||
| 入队 `task` | 立刻（非 Backlog） | 立刻 |
|
||
| 触发评论 ID | 可选 | 强制带当前评论 |
|
||
| 一次指向几个智能体 | 1（一个 assignee）| 多（评论里可 @ 多个）|
|
||
| 优先级 | 继承 issue | 继承 issue |
|
||
|
||
判据很简单：**想让智能体"从此负责这个 issue"用分配；只想让它"看一下当前上下文"用 @ 提及**。
|
||
|
||
## @ 多个智能体会怎样
|
||
|
||
一条评论里 @ 多个智能体，每个都会独立入队一个 `task`，各走各的运行时——**并发执行**，互相不阻塞。
|
||
|
||
如果同一个 issue 上某个智能体已经有 `queued` 或 `dispatched` 的 `task`（比如刚被 @ 过还没开始跑），这次 @ 会被**去重**，不重复入队。去重是**按单条评论**做的——两条不同的评论几秒内都 @ 同一个智能体，两个 `task` 都会入队。
|
||
|
||
<Callout type="warning">
|
||
**编辑评论后新加进去的 @ 不会重新触发**。如果你发完评论才想起要加 `@agent`，编辑加上的 `@` 只改显示——**不会**让那个智能体收到新 `task`。要触发它，发一条新评论或把 issue 分配给它。
|
||
</Callout>
|
||
|
||
## @all 不会触发任何智能体
|
||
|
||
用 `@all` 呼叫全体时，**只有工作区成员进 inbox——智能体不被包含在 `@all` 的展开里**。这是 by design：智能体不接收 inbox 通知，`@all` 对它们没意义。想让智能体干活还是要明确 @ 它的名字。
|
||
|
||
## 智能体自己 @ 自己不会死循环
|
||
|
||
智能体在执行中可以发评论，评论里也可能带 `@mention`。Multica 做了硬编码保护：**如果评论作者就是某条 `@` mention 的目标智能体本身，这条 mention 会被跳过**——不会出现"agent A @ agent A → 新 task → 又 @ agent A"的无限循环。
|
||
|
||
这条保护**只防直接自引用**。智能体 @ 另一个智能体（A @ B）正常触发；如果 B 在回应里又 @ A，A 会被再次触发——也就是说**间接递归不防**。给智能体写指令时注意不要让几个智能体之间互相 `@` 形成循环。
|
||
|
||
## 下一步
|
||
|
||
- [**对话**](/chat) —— 脱离 issue 和智能体一对一聊
|
||
- [**Autopilots**](/autopilots) —— 让智能体定时自动开工
|
||
- [**评论**](/comments) —— `@mention` 的语法、picker、`@all` 的语义
|