Getting started

From nothing to a running team. If you have never used Multica, start at step 1 — the whole thing is a few minutes, and after the last step you never type a command again unless you want to.

What you need

• An agent CLI you already talk to — Claude Code, Cursor, Codex, Windsurf, Gemini CLI. Mops runs inside it.
• The multica CLI — the small binary that connects your machine to a Multica workspace. You install this one (cloud, self-hosted or the desktop app are different choices, so Mops points you at multica.ai rather than guessing); everything after it is Mops's job.

That's it. Once the CLI answers, Mops takes over: no account-setup marathon, no dashboard to configure.

1 · Install the skill

Pick the line for your harness:

# any agent, via skills.sh
npx skills add jamillazarev/multica-ops

# Claude Code as a plugin (adds slash commands)
claude plugin marketplace add jamillazarev/multica-ops
claude plugin install multica-ops@multica-ops

# into a Multica workspace, as an agent skill
multica skill import --url github.com/jamillazarev/multica-ops

In Claude Code you also get a short /mops, installed on first run (one file in your own config, removed any time with rm ~/.claude/commands/mops.md). Everywhere else there are no slash commands and none are needed — plain language reaches every flow.

2 · Just say what you're making

You don't need to know a command. Say what you want — "set up a team for my Android app", "I have a Linear backlog, move it here" — or type /mops on its own, or even "hi".

Mops runs "day zero" for you — six checks, reported as one list with the fix for anything missing, not six separate prompts:

Check	If it's missing
Multica installed?	This one is yours. Mops points you at multica.ai — cloud, self-hosted, or the desktop app (it bundles the CLI) — and picks up as soon as multica version answers. It won't install it for you: the options differ enough that guessing is worse than waiting
Up to date?	tells you what's newer and the line to run — on a self-hosted server the update is yours, and the server goes first
Signed in?	multica setup cloud, or multica setup self-host --server-url … for your own server
A workspace?	creates one, or confirms which if you have several
Daemon running?	multica daemon start — this is what actually executes the work
A runtime?	your agent CLI, auto-detected on PATH — install one if none, then restart the daemon

Installing or updating anything on your machine is reported, never done behind your back — it's your call, and Mops names exactly what each step does and why.

3 · Answer three questions, then it takes over

Once the environment is ready, Mops reads what you have and routes you — you never pick a command:

What you have	Where it goes
nothing yet	/mops init — it shapes the work with you, then staffs a team
a Multica workspace already	/mops join — audits it, then fixes in batches you approve
a backlog in Linear / Jira / a CSV	/mops import — moves it over, unassigned, nothing runs by itself
a list of tasks, you'll set the order	crew mode — executors and gates, you're the manager
a one-hour job	a quick job — one or two agents, build → review, no machinery

These are the commands you type — in full, /mops init, /mops join, so you copy rather than translate. /multica-ops:init reaches the same flow, and plain language always works ("set up a team"). There's no bare /init; outside Claude Code there are no slash commands at all, only plain language.

The interview adapts to you. Tired of questions? Say "you decide" and Mops proposes the whole setup as one list for you to confirm or tweak. Want to be closely involved, or barely? That's the first thing it asks — and it decides how much else you're asked at all.

4 · Getting the new version

Say "is there a new version?" or run /mops upgrade. Mops fetches the update itself. New content applies the next time a file is read — you only restart when the release adds or renames a command or touches a hook, and Mops tells you which case it is. Then it migrates your workspace, re-screens any imported skills, tells you the line to update the CLI (yours to run, and only when the team is idle), and offers /mops whatsnew — a plain-language tour of what changed. See the upgrade diagram.

Upgrading from an older version?

Slash commands exist only on a Claude Code plugin install, and the /mops shortcut only on recent ones — so /mops upgrade (or /multica-ops:upgrade) may say unknown command. Two paths that work from any version:

1. Say "upgrade" in plain language — no slash needed; Mops runs the flow and gives you the one line to run.
2. Update the install yourself, then restart your agent: claude plugin update multica-ops (Claude Code plugin) or npx skills add jamillazarev/multica-ops (skills.sh install).

Where to go next

• Introduction — what Mops is, in one page
• Use cases — a situation → what to say
• Workflow diagrams — the whole thing, visually
• Commands — every command, if you ever want one