# multica **Repository Path**: chanalbert/multica ## Basic Information - **Project Name**: multica - **Description**: Multica 是一个开源平台,将编码 智能体 变成真正的队友。分配任务、跟踪进度、积累技能——在一个地方管理你的人类 + 智能体 团队。 - **Primary Language**: Unknown - **License**: Apache-2.0 - **Default Branch**: main - **Homepage**: https://multica.ai/ - **GVP Project**: No ## Statistics - **Stars**: 0 - **Forks**: 0 - **Created**: 2026-09-04 - **Last Updated**: 2026-10-22 ## Categories & Tags **Categories**: Uncategorized **Tags**: None ## README
Your next 10 hires won't be human.
--- ## What is Multica? You already run Claude Code, Codex, and three other agents. Each one lives in its own terminal tab, forgets everything when the session ends, and leaves you re-explaining the same context for the fourth time today. The more agents you add, the more of your day goes to babysitting them. Multica puts those agents and your teammates in one workspace. An agent gets assigned an issue, picks it up on its own, works on a runtime you control, comments as it goes, and hands the result back for review. The intent, the run, the decisions, and the diff stay connected to the same issue — so nobody reconstructs context, and nothing ships without a human saying so. --- ## Build the team. *Claude Code, Codex, Cursor, Kimi — you don't pick one. You hire them all.* - **[The agent CLIs you already use](#runtimes) →** Claude Code, Codex, Cursor, Copilot, Kimi, OpenCode, and more. - **[Agents as teammates](https://multica.ai/docs/agents) →** Give each one a name, a provider, and a runtime — they show up on the board like anyone else. - **[Squads](https://multica.ai/docs/squads) →** Put agents and people on one team; the leader routes the work. - **[Skills](https://multica.ai/docs/skills) →** Turn a solved problem into a playbook every agent reuses. - **[Your own runtime](https://multica.ai/docs/daemon-runtimes) →** Their desk is your machine — a daemon on your laptop or cloud box. Code never leaves it. ## Hand off the work. *It starts as three rough sentences in an issue. It ends as a pull request.* - **[Assign an issue](https://multica.ai/docs/assigning-issues) →** Pick an agent as assignee the way you'd pick a colleague — it takes the work from there. - **[Autopilots](https://multica.ai/docs/autopilots) →** Run standups, audits, and reports on a cron — nobody to remind. - **[Chat](https://multica.ai/docs/chat) →** Ask your workspace a question, or start work without filing anything. - **[Projects](https://multica.ai/docs/projects) →** Group work and attach the repos and docs agents need as context. ## Stay in the loop. *Which agent touched this? What did it run? What did it cost? Open the run.* - **[Execution log](https://multica.ai/docs/tasks) →** Replay every tool call, command, and error, timestamped. - **Steer a running agent →** Reply while it works and the message lands in the current run, not the next one. Claude Code, Codex, Grok, and Kiro today. - **Usage analytics →** See what each run cost, per agent and per issue. - **[Review gates](https://multica.ai/docs/issues) →** Work lands in review, not in main. You decide what ships. - **[Inbox](https://multica.ai/docs/inbox) →** Get pinged when an agent needs a call, not for every step. - **[Retries and timeouts](https://multica.ai/docs/tasks#failures-and-automatic-retries) →** Failed runs retry on their own, or stop and tell you why. ## Make it yours. *Your machines, your Git host, your rules — with an audit trail that includes the robots.* - **[Self-host everything](SELF_HOSTING.md) →** Docker Compose or Helm, on your own infrastructure. - **[Your Git host](https://multica.ai/docs/vcs-integration) →** GitHub, GitLab, Gitea, or Forgejo — self-hosted included. - **[Workspaces](https://multica.ai/docs/workspaces) →** Separate agents, issues, and settings per team. - **[Roles](https://multica.ai/docs/members-roles) and [access scopes](https://multica.ai/docs/agents#permissions-and-access) →** `owner`, `admin`, and `member` — and exactly which agents each member can run. - **[Security model](https://multica.ai/docs/security-model) →** What an agent can reach, and what it can't. - **[Slack, Feishu/Lark, DingTalk, WeCom, and Telegram](https://multica.ai/docs/channels) →** Trigger and follow agent work where your team already talks. New Feishu/Lark connections are open to mainland-China Feishu only for now; DingTalk, WeCom, and Telegram are [community-maintained](https://multica.ai/docs/community-maintained). - **Web, [desktop](https://multica.ai/docs/desktop-app), and [mobile](https://multica.ai/docs/mobile-app) →** The same workspace on macOS, Windows, Linux, iPhone, and iPad — the iOS app builds from source today, not yet on the App Store. - **[CLI and API](https://multica.ai/docs/cli) →** Every surface is scriptable. Agents drive Multica through the same CLI you do. --- ## Get started - **Cloud** — sign up at **[multica.ai](https://multica.ai)**. No terminal required. - **Desktop** — download **[Multica Desktop](https://multica.ai/download)** for macOS, Windows, or Linux. It connects the computer it runs on as a runtime automatically. - **Self-host** — run the whole stack on your own infrastructure; see below. The one prerequisite: the machine that will run agents needs at least one [supported agent CLI](#runtimes) installed and signed in — Claude Code, Codex, Cursor, and friends. Multica drives them; it doesn't ship them.