mirror of
https://github.com/multica-ai/multica.git
synced 2026-07-05 13:29:44 +02:00
c7e725ef66
* docs(autopilot): rename Routines → Autopilots to match product UI
Unify naming between docs and product. Sidebar label, URL route,
CLI command, and onboarding copy all call this feature "Autopilot";
the docs were the only surface that diverged. Aligning the docs to
the product (rather than the reverse) because the 830+ code-side
references would be a much larger rename to propagate.
- Rename routines.mdx / routines.zh.mdx → autopilots.mdx / autopilots.zh.mdx
- Update meta.json / meta.zh.json index entries (routines → autopilots)
- Drop the reconciliation note ("docs say Routines, CLI says autopilot")
that shipped in the original routines.mdx and the cli.mdx section header
- Update cross-references in cli, how-multica-works, tasks,
assigning-issues, chat, mentioning-agents, daemon-runtimes (EN + ZH)
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
* feat(onboarding): link to docs from key steps and starter tasks
Users who want to dig deeper now have a next hop from inside the flow
instead of having to dig through the help menu. Placed as secondary
links (muted, underline-offset-4) so they don't pull focus from the
primary CTA on each step.
Placement — one link per surface, placed in secondary regions:
- Welcome: "Learn how Multica works" below the subhead
- Questionnaire: "Learn how agents work" in the Why-we-ask aside
- Runtime aside (shared by desktop + web): "Learn about runtimes"
- Agent step: "Creating your first agent" in the About-agents aside
- StarterContentPrompt dialog: "Learn how Multica works"
Starter tasks (content/starter-content-templates.ts): added a single
"Learn about X" tail link per task, only on first occurrence of each
concept within a branch. 8 links on the agent-guided branch + 8 on
the self-serve branch + 1 on the welcome issue header (17 total).
URL scheme: absolute https://multica.ai/docs/{slug} throughout —
absolute so desktop (Electron) opens them in the system browser, and
the /en prefix is omitted because the docs middleware redirects it
away (English is the default, Chinese is /zh/).
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
* feat(landing): add docs link to footer and how-it-works section
Docs were previously reachable only from the in-app help menu. Landing
now surfaces them in two places, both locale-aware (/docs for English,
/docs/zh for Chinese):
- Footer Resources group: Documentation link was pointing at the
GitHub repo; replaced with the real docs URL
- How-It-Works section CTA row: added "Read the docs" between the
primary CTA and the GitHub link, same ghost styling
Locale resolution: href is picked per-render based on the landing's
current locale (cookie-driven via useLocale). The docs app itself
does not auto-detect language, so we must pick the right path
explicitly when emitting the link.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
* fix(onboarding): clean up Autopilot rename leftovers and link formatting
- comments.mdx: "not routine updates" → "not day-to-day updates"
(adjectival holdover now that the feature is renamed Autopilot;
zeroes out remaining "routine" mentions in user-facing docs)
- starter-content-templates.ts: move the arrow inside the markdown
link — "[text →](url)" instead of "→ [text](url)" — so the arrow
is part of the clickable region. 17 occurrences.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
* fix(onboarding): drop docs link from welcome screen and starter-content dialog
"Learn how Multica works" was showing up too often in the first two
screens users see. Keep the link in the post-import welcome issue
header (where users actually have time to explore); remove it from
the two earlier surfaces where it competes with the primary CTA.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
---------
Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
130 lines
5.3 KiB
Plaintext
130 lines
5.3 KiB
Plaintext
---
|
|
title: CLI command reference
|
|
description: One-page overview of every top-level Multica CLI command. For full usage, run `multica <command> --help`.
|
|
---
|
|
|
|
import { Callout } from "fumadocs-ui/components/callout";
|
|
|
|
The Multica CLI mirrors almost everything the Web UI can do (create [issues](/issues), assign [agents](/agents), start the [daemon](/daemon-runtimes), and more). This page lists every top-level command with a one-line description. For the full set of flags and examples, run `multica <command> --help`.
|
|
|
|
## Getting authenticated
|
|
|
|
Run this the first time you use the CLI to obtain a **personal access token (PAT)**:
|
|
|
|
```bash
|
|
multica login
|
|
```
|
|
|
|
Your browser opens automatically. After you approve in the web app, the CLI saves the PAT (prefixed with `mul_`) to `~/.multica/config.json`. Every subsequent command authenticates with that PAT.
|
|
|
|
<Callout type="tip">
|
|
For CI or headless environments, skip the browser flow: create a PAT in the web app under **Settings → Personal Access Tokens**, then run `multica login --token <mul_...>` to supply it directly.
|
|
</Callout>
|
|
|
|
For the difference between token types, see [Authentication and tokens](/auth-tokens).
|
|
|
|
## Auth and setup
|
|
|
|
| Command | Purpose |
|
|
|---|---|
|
|
| `multica login` | Log in and save a PAT |
|
|
| `multica auth status` | Show current login status, user, and workspace |
|
|
| `multica auth logout` | Clear the local PAT |
|
|
| `multica setup cloud` | One-shot setup for Multica Cloud (login + install daemon) |
|
|
| `multica setup self-host` | One-shot setup for a self-hosted backend |
|
|
|
|
## Workspaces and members
|
|
|
|
| Command | Purpose |
|
|
|---|---|
|
|
| `multica workspace list` | List every workspace you can access |
|
|
| `multica workspace get <slug>` | Show details for one workspace |
|
|
| `multica workspace members` | List members of the current workspace |
|
|
|
|
## Issues and projects
|
|
|
|
| Command | Purpose |
|
|
|---|---|
|
|
| `multica issue list` | List issues |
|
|
| `multica issue get <id>` | Show a single issue |
|
|
| `multica issue create --title "..."` | Create a new issue |
|
|
| `multica issue update <id> ...` | Update an issue (status, priority, assignee, etc.) |
|
|
| `multica issue assign <id> --agent <slug>` | Assign to an agent (triggers a task immediately) |
|
|
| `multica issue status <id> --set <status>` | Shortcut to change status |
|
|
| `multica issue search <query>` | Keyword search |
|
|
| `multica issue runs <id>` | Show agent runs on an issue |
|
|
| `multica issue rerun <id>` | Rerun the most recent agent task |
|
|
| `multica issue comment <id> ...` | Nested: view / post comments |
|
|
| `multica issue subscriber <id> ...` | Nested: subscribe / unsubscribe |
|
|
| `multica project list/get/create/update/delete/status` | Project CRUD |
|
|
|
|
## Agents and skills
|
|
|
|
| Command | Purpose |
|
|
|---|---|
|
|
| `multica agent list` | List the workspace's agents |
|
|
| `multica agent get <slug>` | Show an agent's configuration |
|
|
| `multica agent create ...` | Create an agent |
|
|
| `multica agent update <slug> ...` | Update an agent |
|
|
| `multica agent archive <slug>` | Archive |
|
|
| `multica agent restore <slug>` | Restore an archived agent |
|
|
| `multica agent tasks <slug>` | Show an agent's task history |
|
|
| `multica agent skills ...` | Nested: attach / detach skills |
|
|
| `multica skill list/get/create/update/delete` | Skill CRUD |
|
|
| `multica skill import ...` | Import a skill from GitHub, ClawHub, or the local machine |
|
|
| `multica skill files ...` | Nested: manage a skill's files |
|
|
|
|
## Autopilots
|
|
|
|
| Command | Purpose |
|
|
|---|---|
|
|
| `multica autopilot list` | List every autopilot in the workspace |
|
|
| `multica autopilot get <id>` | Show a single autopilot |
|
|
| `multica autopilot create ...` | Create an autopilot |
|
|
| `multica autopilot update <id> ...` | Update |
|
|
| `multica autopilot delete <id>` | Delete |
|
|
| `multica autopilot runs <id>` | Show run history |
|
|
| `multica autopilot trigger <id>` | Trigger a run manually |
|
|
|
|
## Daemon and runtimes
|
|
|
|
| Command | Purpose |
|
|
|---|---|
|
|
| `multica daemon start` | Start the daemon (background by default; add `--foreground` to run in the foreground) |
|
|
| `multica daemon stop` | Stop the daemon |
|
|
| `multica daemon restart` | Restart the daemon |
|
|
| `multica daemon status` | Check whether the daemon is online and its concurrency |
|
|
| `multica daemon logs` | View daemon logs |
|
|
| `multica runtime list` | List runtimes in the current workspace |
|
|
| `multica runtime usage` | Show resource usage |
|
|
| `multica runtime activity` | Recent activity log |
|
|
| `multica runtime ping <id>` | Ping a runtime to check it's online |
|
|
| `multica runtime update <id> ...` | Update a runtime's configuration |
|
|
|
|
## Miscellaneous
|
|
|
|
| Command | Purpose |
|
|
|---|---|
|
|
| `multica repo checkout <url>` | Clone a repo locally for agents to use |
|
|
| `multica config` | View or edit local CLI configuration |
|
|
| `multica version` | Print the CLI version |
|
|
| `multica update` | Upgrade the CLI to the latest release |
|
|
| `multica attachment download <id>` | Download an attachment from an issue or comment |
|
|
|
|
## Getting full flags
|
|
|
|
Every command supports `--help`:
|
|
|
|
```bash
|
|
multica issue create --help
|
|
multica agent update --help
|
|
```
|
|
|
|
v2 will ship a dedicated detailed reference page for each command.
|
|
|
|
## Next steps
|
|
|
|
- [Authentication and tokens](/auth-tokens) — PAT vs. JWT vs. daemon token
|
|
- [Daemon and runtimes](/daemon-runtimes) — how the `daemon` commands work under the hood
|
|
- [Creating and configuring agents](/agents-create) — all options for `multica agent create`
|