Multica / Reference
CLI command quick review
One-page overview of all top-level commands of Multica CLI. For complete usage, check `multica <command> --help`.

Overview
Multica CLI moves almost everything that the Web UI can do to the command line (create issues, assign agents, start daemons, etc.). This page lists all top-level commands, each with a purpose. For complete flags and examples, use multica --help.
Authentication entrance
When using the CLI for the first time, log in and get a Personal Access Token (PAT):
multica login
The browser will automatically open, and after you agree on the web side, the CLI will save the PAT (mul_ prefix) to ~/.multica/config.json. All subsequent commands will automatically use this PAT authentication.
CI / browser-less environment skips the browser process: first create a PAT on the web side Settings → Personal Access Tokens, and then fill it in directly with
multica login --token <mul_...>.
For detailed distinctions between Token types, see Authentication and Tokens.
Authentication and initialization
| Command | Purpose |
|---|---|
multica login |
Log in and save PAT |
multica auth status |
View current login status, user, workspace |
multica auth logout |
Clear local PAT |
multica setup cloud |
Multica Cloud one-click initialization (login + install daemon) |
multica setup self-host |
One-click initialization of self-deployment backend |
Workspaces and members
| Command | Purpose |
|---|---|
multica workspace list |
List all workspaces you have access to |
multica workspace get <slug> |
View details of a workspace |
multica workspace member list |
List members of the current workspace |
multica workspace update <id> --name "..." [--description "..."] [--context "..."] [--issue-prefix "..."] |
Modify workspace metadata (admin/owner permissions). Long text is available with --description-stdin / --context-stdin. |
Issue and Project
The
listclass commands (multica issue list,autopilot list,project list, etc.) display the short ID that can be copied directly in the table by default: issue is the key (such asMUL-123), and the remaining resources are UUID short prefixes.<id>in the table below accepts both short IDs and full UUIDs, so typical usage ismultica issue list→ copy key →multica issue get MUL-123. Add--full-idtolistwhen a complete UUID is required.
| Command | Purpose |
|---|---|
multica issue list |
List issues (the issue key that can be copied is displayed by default) |
multica issue get <id> |
View a single issue (accept issue key or UUID) |
multica issue create --title "..." |
Create a new issue |
multica issue update <id> ... |
Modify issue (status, priority, assignee, etc.) |
multica issue assign <id> --to <name> |
Assign to a member, agent or squad (assigning to an agent triggers a run) |
multica issue status <id> <status> |
Quickly change status |
multica issue search <query> |
Keyword search |
multica issue children <id> |
View child issues grouped by stage |
multica issue pull-requests <id> |
View associated PRs and their status |
multica issue runs <id> |
View the tasks run by the agent on the issue |
multica issue run-messages <task-id> |
View the messages of a certain execution |
multica issue usage <id> |
View the aggregate token usage of a single issue |
multica issue rerun <id> |
Re-create a task for the current agent assignee of the issue |
multica issue cancel-task <task-id> |
Cancel a queued or running task |
multica issue comment <id> ... |
Nesting: View / Post comment |
multica issue comment resolve/unresolve <comment-id> |
Mark comment thread resolved/unresolved |
multica issue subscriber <id> ... |
Nesting: subscribe/unsubscribe |
multica issue metadata <id> ... |
Nesting: read and write issue metadata |
multica issue label <id> ... |
Nesting: Manage labels on issues |
multica project list/get/create/update/delete/status |
Project CRUD |
multica label list/create/update/delete |
Workspace label CRUD |
Agents and Skills
Skill import conflict
| Command | Purpose |
|---|---|
multica agent list |
List agents in a workspace |
multica agent get <slug> |
View agent configuration |
multica agent create ... |
Create an agent |
multica agent update <slug> ... |
Modify agent |
multica agent archive <slug> |
archive |
multica agent restore <slug> |
Restore archived agents |
multica agent tasks <slug> |
View the agent's task history |
multica agent avatar <slug> |
Upload agent avatar |
multica agent env <slug> ... |
Read or replace the agent's custom environment variables |
multica agent skills ... |
Nesting: Mount/Unmount Skill |
multica skill list/get/create/update/delete |
Skill CRUD |
multica skill import ... |
Import Skill from GitHub / ClawHub / native |
multica skill files ... |
Nesting: Manage Skill files |
multica skill import --url <url> defaults to --on-conflict fail. If there is already a Skill with the same name in the workspace, the command will return a structured conflict result and exit without modifying the workspace.
If you are the creator of an existing Skill and want to overwrite it with the newly imported content while retaining the original Skill's ID and agent binding, use --on-conflict overwrite. If you want to keep the existing Skill and save another copy, use --on-conflict rename, and the system will automatically add a suffix such as -2. If you just want to skip items with the same name when importing in batches, use --on-conflict skip.
multica skill import --url https://skills.sh/acme/repo/review-helper
multica skill import --url https://skills.sh/acme/repo/review-helper --on-conflict overwrite
multica skill import --url https://skills.sh/acme/repo/review-helper --on-conflict rename
multica skill import --url https://skills.sh/acme/repo/review-helper --on-conflict skip
squad
See Squad for the full model.
| Command | Purpose |
|---|---|
multica squad list |
List the squads in the workspace |
multica squad get <id> |
View a squad |
multica squad create --name "..." --leader <agent> |
Create a squad (owner/admin) |
multica squad update <id> ... |
Modify name, description, instructions, captain, avatar |
multica squad delete <id> |
Archive (soft delete) - At the same time, transfer the issue assigned to the squad to the captain |
multica squad member list/add/remove/set-role <squad-id> |
Manage squad members and update role in place |
multica squad activity <issue-id> <action|no_action|failed> --reason "..." |
Called at the end of each round by the captain agent to record evaluation |
Autopilots
multica autopilot create/update also supports --subscriber to set default subscribers for issues created in createissue mode; update supports --clear-subscribers to clear default subscribers.
| Command | Purpose |
|---|---|
multica autopilot list |
List all autopilots in the workspace |
multica autopilot get <id> |
View a single autopilot |
multica autopilot create ... |
Create autopilot |
multica autopilot update <id> ... |
Modify |
multica autopilot delete <id> |
Delete |
multica autopilot runs <id> |
View run history |
multica autopilot trigger <id> |
Manually trigger once |
multica autopilot trigger-add/update/delete <id> |
Manage schedule or webhook trigger |
multica autopilot trigger-rotate-url <id> <trigger-id> |
Rotate webhook trigger URL |
Daemons and runtimes
| Command | Purpose |
|---|---|
multica daemon start |
Start daemon (default background; add --foreground to run in the foreground) |
multica daemon stop |
Stop daemon |
multica daemon restart |
Restart daemon |
multica daemon status |
Check whether the daemon is online + concurrency conditions |
multica daemon logs |
View daemon logs |
multica runtime list |
List the runtimes of the current workspace |
multica runtime usage |
View resource usage |
multica runtime activity |
Recent activity records |
multica runtime update <id> ... |
Trigger CLI update on a certain runtime |
multica runtime delete <id> [--cascade] |
Delete the runtime and optionally archive the bound agents at the same time |
multica runtime profile ... |
Manage custom runtime profiles and native path overrides |
Miscellaneous
| Command | Purpose |
|---|---|
multica repo checkout <url> |
Pull the repo locally for use by the agent |
multica config |
View/modify CLI local configuration |
multica version |
Show CLI version |
multica update |
Upgrade CLI to the latest version |
multica attachment download <id> |
Download issue/comment attachments |
Check the complete flag
Every command supports --help:
multica issue create --help
multica agent update --help
v2 will give each command a separate detailed reference page.
Next step
- Authentication and Tokens ——The difference between PAT / JWT / Daemon Token
- Daemon and Runtimes - The working mechanism behind the
daemoncommand - Create and configure agents - full options for
multica agent create