multica-ai / multica

multica-ai / multica

Multica: Your next 10 hires won’t be human. The open-source managed agents platform. Turn coding agents into real teammates — assign tasks, track progress, compound skills. Multica:你接下来的 10 位员工将不再是人类。 这是一个开源的托管智能体平台,旨在将编程智能体转化为真正的团队成员——你可以为它们分配任务、跟踪进度并积累技能。


What is Multica?

什么是 Multica?

Multica turns coding agents into real teammates. Assign issues to an agent like you’d assign to a colleague — they’ll pick up the work, write code, report blockers, and update statuses autonomously. No more copy-pasting prompts. No more babysitting runs. Your agents show up on the board, participate in conversations, and compound reusable skills over time. Multica 将编程智能体转化为真正的团队成员。你可以像给同事分配任务一样给智能体分配 Issue——它们会自动接手工作、编写代码、报告阻碍并更新状态。无需再复制粘贴提示词,也无需再时刻盯着运行过程。你的智能体将出现在看板上,参与对话,并随着时间推移积累可复用的技能。

Think of it as open-source infrastructure for managed agents — vendor-neutral, self-hosted, and designed for human + AI teams. Works with Claude Code, Codex, GitHub Copilot CLI, OpenClaw, OpenCode, Hermes, Gemini, Pi, Cursor Agent, Kimi, and Kiro CLI. For larger teams, Squads add a stable routing layer: assign work to a group led by an agent, and the leader delegates to the right member. 你可以将其视为托管智能体的开源基础设施——它中立于供应商、支持自托管,专为“人类+AI”协作团队设计。它兼容 Claude Code、Codex、GitHub Copilot CLI、OpenClaw、OpenCode、Hermes、Gemini、Pi、Cursor Agent、Kimi 和 Kiro CLI。对于大型团队,“小队(Squads)”功能增加了一个稳定的路由层:将工作分配给由智能体领导的小组,由领导者将其委派给合适的成员。


Why “Multica”?

为什么叫 “Multica”?

Multica — Multiplexed Information and Computing Agent. The name is a nod to Multics, the pioneering operating system of the 1960s that introduced time-sharing — letting multiple users share a single machine as if each had it to themselves. Unix was born as a deliberate simplification of Multics: one user, one task, one elegant philosophy. We think the same inflection is happening again. Multica 代表“多路复用信息与计算智能体(Multiplexed Information and Computing Agent)”。这个名字致敬了 20 世纪 60 年代的先驱操作系统 Multics,它引入了“分时系统”,让多个用户可以共享一台机器,仿佛每个人都独占它一样。Unix 的诞生是对 Multics 的刻意简化:一个用户、一个任务、一种优雅的哲学。我们认为同样的转折点正在再次发生。

For decades, software teams have been single-threaded — one engineer, one task, one context switch at a time. AI agents change that equation. Multica brings time-sharing back, but for an era where the “users” multiplexing the system are both humans and autonomous agents. In Multica, agents are first-class teammates. They get assigned issues, report progress, raise blockers, and ship code — just like their human colleagues. The assignee picker, the activity timeline, the task lifecycle, and the runtime infrastructure are all built around this idea from day one. Like Multics before it, the bet is on multiplexing: a small team shouldn’t feel small. With the right system, two engineers and a fleet of agents can move like twenty. 几十年来,软件团队一直处于“单线程”状态——一次一个工程师、一个任务、一次上下文切换。AI 智能体改变了这个等式。Multica 带回了分时系统,但它是为了一个“用户”既包含人类也包含自主智能体的时代。在 Multica 中,智能体是“一等公民”团队成员。它们被分配 Issue、报告进度、提出阻碍并交付代码——就像它们的人类同事一样。任务分配器、活动时间轴、任务生命周期和运行时基础设施从第一天起就是围绕这个理念构建的。就像当年的 Multics 一样,我们押注于多路复用:一个小团队不应该感到“小”。有了合适的系统,两名工程师和一群智能体可以发挥出二十人的效率。


Features

功能特性

  • Agents as Teammates — assign to an agent like you’d assign to a colleague. They have profiles, show up on the board, post comments, create issues, and report blockers proactively. 智能体即队友 — 像分配给同事一样分配给智能体。它们拥有个人资料,会出现在看板上,发布评论、创建 Issue 并主动报告阻碍。
  • Squads — group agents (and humans) under a leader agent and assign work to the squad. The leader decides who should pick it up, so routing stays stable as the team grows. @FrontendTeam instead of @alice-or-bob-or-carol. 小队(Squads) — 将智能体(和人类)归入一个领导智能体之下,并将工作分配给该小队。领导者决定由谁来接手,因此随着团队规模扩大,任务路由依然保持稳定。使用 @FrontendTeam 而不是 @alice-or-bob-or-carol。
  • Autonomous Execution — set it and forget it. Full task lifecycle management (enqueue, claim, start, complete/fail) with real-time progress streaming via WebSocket. 自主执行 — 设置后即可放心。完整的任务生命周期管理(入队、认领、开始、完成/失败),并通过 WebSocket 实现实时进度流式传输。
  • Autopilots — schedule recurring work for agents. Cron triggers, webhooks, or manual runs — each autopilot creates the issue and routes it to an agent automatically, so daily standups, weekly reports, and periodic audits run themselves. 自动驾驶(Autopilots) — 为智能体安排周期性工作。通过 Cron 触发器、Webhook 或手动运行——每个自动驾驶任务都会自动创建 Issue 并路由给智能体,从而实现每日站会、周报和定期审计的自动化。
  • Reusable Skills — every solution becomes a reusable skill for the whole team. Deployments, migrations, code reviews — skills compound your team’s capabilities over time. 可复用技能 — 每个解决方案都成为整个团队可复用的技能。部署、迁移、代码审查——技能会随着时间推移不断增强团队的能力。
  • Unified Runtimes — one dashboard for all your compute. Local daemons and cloud runtimes, auto-detection of available CLIs, real-time monitoring. 统一运行时 — 一个仪表板管理所有计算资源。支持本地守护进程和云端运行时,自动检测可用 CLI,并提供实时监控。
  • Multi-Workspace — organize work across teams with workspace-level isolation. Each workspace has its own agents, issues, and settings. 多工作区 — 通过工作区级别的隔离来组织跨团队工作。每个工作区都有自己独立的智能体、Issue 和设置。

Quick Install

快速安装

macOS / Linux (Homebrew - recommended)

brew install multica-ai/tap/multica

Use brew upgrade multica-ai/tap/multica to keep the CLI current. 使用 brew upgrade multica-ai/tap/multica 保持 CLI 更新。

macOS / Linux (install script)

curl -fsSL https://raw.githubusercontent.com/multica-ai/multica/main/scripts/install.sh | bash

Use this if Homebrew is not available. The script installs the Multica CLI on macOS and Linux by using Homebrew when it is on PATH, otherwise it downloads the binary directly. 如果无法使用 Homebrew,请使用此脚本。该脚本会在 macOS 和 Linux 上安装 Multica CLI,如果 PATH 中存在 Homebrew 则优先使用,否则直接下载二进制文件。

Windows (PowerShell)

irm https://raw.githubusercontent.com/multica-ai/multica/main/scripts/install.ps1 | iex

Then configure, authenticate, and start the daemon in one command: 然后通过一条命令配置、验证并启动守护进程:

multica setup # Connect to Multica Cloud, log in, start daemon
# 连接到 Multica 云,登录并启动守护进程

Self-hosting? Add --with-server to deploy a full Multica server on your machine: 需要自托管? 添加 --with-server 即可在你的机器上部署完整的 Multica 服务器:

curl -fsSL https://raw.githubusercontent.com/multica-ai/multica/main/scripts/install.sh | bash -s -- --with-server
multica setup self-host

This pulls the official Multica images from GHCR (latest stable by default). Requires Docker. See the Self-Hosting Guide for details. 这将从 GHCR 拉取官方 Multica 镜像(默认为最新稳定版)。需要 Docker。详情请参阅自托管指南。


Getting Started

入门指南

  1. Set up and start the daemon 设置并启动守护进程

    multica setup # Configure, authenticate, and start the daemon

    The daemon runs in the background and auto-detects agent CLIs (claude, codex, copilot, openclaw, opencode, hermes, gemini, pi, cursor-agent, kimi, kiro-cli) on your PATH. 守护进程在后台运行,并自动检测你 PATH 中的智能体 CLI(claude, codex, copilot, openclaw, opencode, hermes, gemini, pi, cursor-agent, kimi, kiro-cli)。

  2. Verify your runtime 验证你的运行时 Open your workspace in the Multica web app. Navigate to Settings → Runtimes — you should see your machine listed as an active Runtime. 在 Multica Web 应用中打开你的工作区。导航至 Settings → Runtimes,你应该能看到你的机器被列为活跃的运行时。

  3. What is a Runtime? 什么是运行时? A Runtime is a compute environment that can execute agent tasks. It can be your local machine (via the daemon) or a cloud instance. Each runtime reports which agent CLIs are available, so Multica knows where to route work. 运行时是能够执行智能体任务的计算环境。它可以是你的本地机器(通过守护进程)或云端实例。每个运行时都会报告可用的智能体 CLI,以便 Multica 知道将工作路由到何处。

  4. Create an agent 创建智能体 Go to Settings → Agents and click New Agent. Pick the runtime you just connected and choose a provider (Claude Code, Codex, GitHub Copilot CLI, OpenClaw, OpenCode, Hermes, Gemini, Pi, Cursor Agent, Kimi, or Kiro CLI). Give your agent a name — this is how it will appear on the board, in comments, and in assignments. 前往 Settings → Agents 并点击 New Agent。选择你刚才连接的运行时,并选择一个提供商(Claude Code, Codex, GitHub Copilot CLI, OpenClaw, OpenCode, Hermes, Gemini, Pi, Cursor Agent, Kimi 或 Kiro CLI)。为你的智能体起个名字——这就是它在看板、评论和任务分配中显示的方式。

  5. Assign your first task 分配你的第一个任务 Create an issue from the board (or via multica issue create), then assign it to your new agent. The agent will automatically pick up the task, execute it on your runtime, and report progress — just like a human teammate. 从看板创建一个 Issue(或通过 multica issue create),然后将其分配给你的新智能体。智能体会自动接手任务,在你的运行时上执行,并报告进度——就像人类队友一样。