mirror of
https://github.com/multica-ai/multica.git
synced 2026-07-12 12:18:55 +02:00
bae8a84abd
* feat(agent): add Antigravity runtime backend Adds Google's Antigravity CLI (`agy`) as the 12th supported coding-tool runtime, alongside Claude / Codex / Cursor / Copilot / Gemini / Hermes / Kimi / Kiro / OpenCode / OpenClaw / Pi. The CLI emits plain assistant text on stdout (no structured event stream), so the backend streams stdout line-by-line as `MessageText` events and accumulates the same text as the final `Result.Output`. Session resumption uses `--conversation <id>`; because the conversation UUID is not echoed on stdout, the daemon routes `--log-file` to a temp file and recovers the id from the glog-formatted log lines. MUL-2767 Co-authored-by: multica-agent <github@multica.ai> * fix(agent): correct Antigravity capability contract from Elon review - ModelSelectionSupported now returns false for antigravity. `agy` has no --model flag and antigravityBackend deliberately drops opts.Model, so the UI must render a disabled "Managed by runtime" picker instead of an empty dropdown plus a silently-ignored manual-entry field. Also stop seeding AgentEntry.Model from MULTICA_ANTIGRAVITY_MODEL — the backend would silently ignore it. - Antigravity skills now write to {workDir}/.agents/skills/, the CLI's native workspace path (inherits Gemini CLI's layout per https://antigravity.google/docs/gcli-migration). Previously they went to the .agent_context/skills/ fallback that the CLI doesn't scan. Runtime brief moves antigravity into the native-discovery branch and local_skills.go points the user-level skill root at ~/.gemini/antigravity-cli/skills for Runtime → local skill import. - Doc + UI comment sync: providers matrix / install-agent-runtime / cloud-quickstart / agents-create / tasks (session-resume support) / skills / README all now list Antigravity in the right buckets, and the model-picker / model-dropdown comments cite antigravity (not the stale hermes reference) as the supported=false example. New tests: TestAntigravityModelSelectionUnsupported, TestInjectRuntimeConfigAntigravity (native discovery wording), TestWriteContextFilesAntigravityNativeSkills (.agents/skills/ landing, .agent_context/skills/ NOT written). Co-authored-by: multica-agent <github@multica.ai> * feat(provider-logo): swap inline placeholder for real Antigravity PNG Replaces the hand-drawn planet+arc placeholder with the official asset shipped from Downloads. Stored next to the component; bundlers (Next.js / electron-vite) resolve the PNG import to a URL string at build time. Added a small assets.d.ts so packages/views' tsc accepts PNG / SVG module imports — there was no prior asset usage in this package to register the declaration. --------- Co-authored-by: J <j@multica.ai> Co-authored-by: multica-agent <github@multica.ai>
51 lines
3.3 KiB
Plaintext
51 lines
3.3 KiB
Plaintext
---
|
||
title: 欢迎
|
||
description: 一个任务协作平台——人类和 AI 智能体在同一个工作区里共同工作。
|
||
---
|
||
|
||
import { Callout } from "fumadocs-ui/components/callout";
|
||
|
||
Multica 是一个任务协作平台，让人类和 AI [智能体](/agents) 在同一个 [工作区](/workspaces) 里共同工作。你可以像给同事派活一样，[把一个任务分配给智能体](/assigning-issues) ——由它去执行、汇报进展、在评论里回复你；也可以[打开聊天窗口直接和它对话](/chat)，让它帮你起草任务、回答问题、或完成一次性请求。
|
||
|
||
这一页讲清楚智能体在哪里运行，以及你有哪几种方式开始使用 Multica。
|
||
|
||
## 智能体在哪里运行
|
||
|
||
智能体执行任务**不**发生在 Multica 服务器上。目前 Multica 支持一种运行方式：
|
||
|
||
- **本地 [守护进程](/daemon-runtimes)** — 你在自己的机器上运行 `multica daemon`，由它调用本地安装的 [AI 编程工具](/providers)。目前内置 12 款：[Antigravity](/providers#antigravity)、[Claude Code](/providers#claude-code)、[Codex](/providers#codex)、[Cursor](/providers#cursor)、[Copilot](/providers#copilot)、[Gemini](/providers#gemini)、[Hermes](/providers#hermes)、[Kimi](/providers#kimi)、[Kiro CLI](/providers#kiro-cli)、[OpenCode](/providers#opencode)、[OpenClaw](/providers#openclaw)、[Pi](/providers#pi)。你的 API 密钥、工具链、代码目录都保留在本地。
|
||
|
||
<Callout type="info">
|
||
**云端运行时即将开放**，目前处于等待名单阶段。上线后，你无需在本地运行守护进程，即可在 Multica Cloud 上直接执行智能体任务。在 [下载页面](https://multica.ai/download) 登记邮箱以获取通知。
|
||
</Callout>
|
||
|
||
## 三种使用方式
|
||
|
||
前两张卡是**后端选择**——Multica 服务器运行在哪里；第三张是**客户端选择**——你从哪个界面使用。桌面应用可以搭配前两种后端中的任意一种。
|
||
|
||
<NumberedCards>
|
||
<NumberedCard number="01" title="Multica Cloud" href="/cloud-quickstart" tag="等待名单">
|
||
托管后端。安装命令行工具并在本地运行守护进程，连接到 Multica 托管的服务器。约 5 分钟完成。
|
||
</NumberedCard>
|
||
<NumberedCard number="02" title="自部署" href="/self-host-quickstart" tag="Docker · Helm">
|
||
用 Docker Compose 在自己的服务器上运行完整后端。数据库、服务器、存储都在你自己的基础设施上。
|
||
</NumberedCard>
|
||
<NumberedCard number="03" title="桌面应用" href="/desktop-app" tag="推荐">
|
||
原生多标签窗口。内置命令行工具并在启动时自动拉起守护进程——安装后无需运行任何命令即可使用。可连接 Multica Cloud 或你自部署的后端。
|
||
</NumberedCard>
|
||
</NumberedCards>
|
||
|
||
## 下一步
|
||
|
||
<NumberedSteps>
|
||
<Step number="01" title="先理解运行模型">
|
||
[Multica 是怎么工作的](/how-multica-works) — 30 秒读完，把"server 不跑 agent，agent 跑在你本地"这件事一次讲透。
|
||
</Step>
|
||
<Step number="02" title="挑一种使用方式开始">
|
||
上面三种里选一种——大多数人从 [桌面应用](/desktop-app) 起步，零命令行配置，5 分钟跑起来。
|
||
</Step>
|
||
<Step number="03" title="派出第一个任务">
|
||
创建一个 [Issue](/issues)，把执行人选成智能体而不是同事。等它来交活。
|
||
</Step>
|
||
</NumberedSteps>
|