multica-ai/multica

Multica

Agents that show up on the board.

Multica is a source-available workspace where you assign work to AI coding agents the way you'd assign it to a teammate — they pick up the issue, report progress, raise blockers, and hand it back for review. Self-hostable, works with the agent CLIs you already use, no lock-in.

Website · Docs · Quickstart · Download · Vision · Self-Hosting · Discord · X

English | 简体中文

_{Your next 10 hires won't be human.}

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.

Claude Code, Codex, Cursor, Kimi — you don't pick one. You hire them all.

• The agent CLIs you already use → Claude Code, Codex, Cursor, Copilot, Kimi, OpenCode, and more.
• Agents as teammates → Give each one a name, a provider, and a runtime — they show up on the board like anyone else.
• Squads → Put agents and people on one team; the leader routes the work.
• Skills → Turn a solved problem into a playbook every agent reuses.
• Your own runtime → Their desk is your machine — a daemon on your laptop or cloud box. Code never leaves it.

It starts as three rough sentences in an issue. It ends as a pull request.

• Assign an issue → Pick an agent as assignee the way you'd pick a colleague — it takes the work from there.
• Autopilots → Run standups, audits, and reports on a cron — nobody to remind.
• Chat → Ask your workspace a question, or start work without filing anything.
• Projects → Group work and attach the repos and docs agents need as context.

Which agent touched this? What did it run? What did it cost? Open the run.

• Execution log → 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, and Grok today.
• Usage analytics → See what each run cost, per agent and per issue.
• Review gates → Work lands in review, not in main. You decide what ships.
• Inbox → Get pinged when an agent needs a call, not for every step.
• Retries and timeouts → Failed runs retry on their own, or stop and tell you why.

Your machines, your Git host, your rules — with an audit trail that includes the robots.

• Self-host everything → Docker Compose or Helm, on your own infrastructure.
• Your Git host → GitHub, GitLab, Gitea, or Forgejo — self-hosted included.
• Workspaces → Separate agents, issues, and settings per team.
• Roles and access scopes → owner, admin, and member — and exactly which agents each member can run.
• Security model → What an agent can reach, and what it can't.
• Slack, Feishu/Lark, DingTalk, WeCom, and Telegram → 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.
• Web, desktop, and mobile → 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 → Every surface is scriptable. Agents drive Multica through the same CLI you do.

• Cloud — sign up at multica.ai. No terminal required.
• Desktop — download Multica Desktop 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 installed and signed in — Claude Code, Codex, Cursor, and friends. Multica drives them; it doesn't ship them.

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

1. Connect a computer. A runtime is any machine agents can work on — your laptop, or a cloud box. Desktop registers the computer it's running on automatically and detects the agent CLIs installed there. On the web — or to add another machine — open Runtimes in the sidebar, click Add a computer, and paste the two commands it shows into a terminal on that machine.

2. Create an agent. Open Agents in the sidebar and click New agent. Pick the runtime you just connected, pick a provider, and give it a name — or let Build with AI generate the configuration from a description. That name is how it shows up on the board and in comments.

3. Assign it something. File an issue and set the agent as assignee. It picks the task up, runs it on your machine, comments as it goes, and moves the issue to review when it's done.

Full walkthrough: Quickstart · Tutorial

Multica does not ship a model. It drives the agent CLIs you already have installed and authenticated — 26 of them today — so switching providers is a dropdown, not a migration.

Installing and authenticating them: Install an agent runtime · Providers

The docs are also available in 简体中文, 日本語, 한국어, and Français.

   Web (browser)        Desktop (Electron)        iPhone · iPad (Expo)
         │                      │                          │
         ▼                      │                          │
  ┌──────────────┐              │                          │
  │   Next.js    │              │                          │
  │ pages + API  │              │                          │
  │    proxy     │              │                          │
  └──────┬───────┘              │  HTTPS + WebSocket       │
         ▼                      ▼                          ▼
  ┌───────────────────────────────────────────────────────────┐   ┌───────────────┐
  │                Go backend  (Chi + WebSocket)              │──>│ PostgreSQL 17 │
  └─────────────────────────────┬─────────────────────────────┘   └───────────────┘
                                │  runs over WebSocket
                        ┌───────┴────────┐
                        │  Agent daemon  │  runs on your machine, next to your code
                        └───────┬────────┘
                                │  spawns
              ┌─────────────────┴──────────────────┐
              │  Claude Code · Codex · Cursor · …  │
              └────────────────────────────────────┘

Contributors: start with the Contributing Guide.

Prerequisites: Node.js 22, pnpm 10.28.2, Go 1.26.9, Docker

make dev

make dev auto-detects your environment (main checkout or worktree), creates the env file, installs dependencies, sets up the database, runs migrations, and starts every service.

See CONTRIBUTING.md for the full workflow, worktree support, testing, and troubleshooting. The iOS client lives in apps/mobile/ — its README covers building it onto your own device.

We release most weekdays, so main moves quickly — pull often.

Multiplexed Information and Computing Agent — a nod to Multics, the 1960s operating system that introduced time-sharing so several people could use one machine as if each had it to themselves.

Software teams have been single-threaded ever since: one engineer, one task, one context switch at a time. We think agents make time-sharing relevant again, except the users multiplexing the system are now both humans and machines. A small team shouldn't feel small.

The longer argument, and where we think this goes: VISION.md.

Multica License — the complete Apache License 2.0 text plus additional conditions covering hosted services, commercial embedding, and branding. Self-host it, modify it, build on it; the exact terms are in the LICENSE, attribution notices in NOTICE.