Vibe Coding
Back to Multica

Multica / Get started

Get started quickly with Cloud

5 minutes from registration to assigning the first task to the agent.

Get started quickly with Cloud key concepts infographic
Get started quickly with Cloud key concepts infographic

Overview

This page takes you through the end-to-end process of Multica Cloud - register → install command line tool → start daemon → create agent → assign the first task, which takes about 5 minutes to complete.

There is only one prefix: you have installed at least one AI programming tool(Antigravity, Claude Code,Codex,Cursor,Copilot,Gemini,Hermes,Kimi,Kiro CLI, OpenCode, OpenClaw, Pi). The daemon will automatically detect them when it starts. If any of them are not installed, the daemon will directly refuse to start.

1. Register an account

Register an account at multica.ai. You can log in with email (6-digit verification code) or Google.

After registration is completed, you will be automatically assigned to a default workspace (generated with your account name). You can change the name later or create a new workspace.

2. Install Multica command line tool

macOS/Linux (Homebrew is recommended):

brew install multica-ai/tap/multica

macOS/Linux (without Homebrew):

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

Windows (PowerShell):

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

After installation, verify:

multica version

3. Log in + start daemon process

Complete login + start daemon process with one command:

multica setup

multica setup will:

  1. Configure the command line tool to connect to Multica Cloud
  2. Open the browser to log in (same email verification code/Google OAuth as web login)
  3. Save the generated PAT to ~/.multica/config.json
  4. Automatically start daemon - start polling tasks every 3 seconds and send heartbeat every 15 seconds

**Are you using the desktop application? ** The daemon process is automatically started when the desktop application is started. There is no need to manually run multica setup. See desktop-app.

Verify that the daemon is running:

multica daemon status

Seeing online means it has successfully registered to the server.

4. Verify Runtime is online

Go to Settings → Runtimes in the web interface, and you should see the daemon you just started listed as one or more active runtimes—one for each of your locally installed AI programming tools.

Don’t panic when you see “offline”, first check [Troubleshooting → The daemon cannot connect to the server](/vibe-coding-tools/multica/troubleshooting#The daemon cannot connect to the server).

5. Create an agent

Go to Settings → Agents in the web interface and click New Agent:

  • Name——The name displayed by the agent on the bulletin board and in the comments. Choose one yourself.
  • Provider——Choose an AI programming tool that you have installed locally (only the ones detected during runtime will appear in the drop-down list)
  • Model (optional) - model selection within the tool (static list or dynamic discovery, depending on provider)
  • Instructions (optional) - system prompts for this agent

After creation, the agent will enter your workspace member list and can be assigned tasks like human members.

6. Assign the first task

Create an issue in the web interface, or use the command line:

multica issue create --title "Add an ASCII architecture diagram to README"

Assign this issue to the agent you just created - you can click on its avatar on the web, or use the command line:

multica issue assign MUL-1 --to my-agent-name

After --to, fill in the name of the agent or member, a substring will do - if the agent is called my-code-reviewer, filling in reviewer will also hit. If the names in the workspace overlap or conflict with each other, use --to-id <uuid> instead (mutually exclusive with --to); the UUID comes from multica agent list --output json or multica workspace member list --output json.

The daemon process will next:

  1. Take this task within 3 seconds (task status changes from queued to dispatched)
  2. Call the corresponding AI programming tool to start execution (the status changes to running)
  3. AI works locally—may read your code directory, execute commands, and edit files
  4. After completion, send the result back to Multica (the status changes to completed or failed, depending on whether to automatically retry)

The web interface displays progress in real time (via WebSocket) - no refresh required.

Next step