/makers-cli

name: edgeone-makers-cli
description: >-
  EdgeOne Makers CLI command reference.
  Use when running edgeone CLI commands for dev, build, deploy, env management.
metadata:
  author: edgeone
  version: "1.2.1"

EdgeOne Makers CLI Reference

Install

npm install -g edgeone@latest

**This Skill requires CLI `>= 1.7.0` for every CLI execution flow**, including local dev, build, login, switching, linking, env, authenticated deployment and anonymous deployment / claim. Check `edgeone -v` before the first CLI operation and upgrade if lower. Writing code or reading guidance does not require installing/upgrading CLI; local previews do not require authentication unless they use credentialed services.

**Release availability**: `1.7.0` is the planned public CLI baseline. If it is not yet available from the user's configured registry, or `@latest` still resolves below it, stop and explain that the required release is unavailable; do not repeatedly install, silently continue with an older CLI, switch registries without consent, or assume a local development build is publicly released. This Skill should be published after the public `1.7.0` package is available and verified.

Version alone is not proof of the invoked package's capabilities: verify the actual CLI on PATH. `login --help` must expose `--interaction`, `--workspace`, `--session`; explicit linking requires `makers link --help` with `--mode`, `link_existing`, `create_upload`, `--skip-env-sync`, `--expected-workspace`, and `--json`; `whoami --help` must expose `--json`. Missing capabilities after a reported version match require checking the installed package/path, not a legacy fallback, guessed flags or private credential files. An arbitrary exit 1 is never proof of missing login.

Login, workspace switching and project targets

Execution modes

• **Standalone Skill**: execute native CLI in the actual project root after setting `PAGES_SOURCE=skills`. MCP is optional; do not require an expert team, connector or MCP server. Keep `agent` interaction for user choices, not automatic paid-workspace selection.
• **When equivalent MCP tools are available**: use `account_info`, `edgeone_workspace` and `deploy_folder`; keep exact IDs internal. Native CLI remains available for actions without an equivalent tool. Missing MCP alone is not an error for standalone use.
• **Connector already authenticated**: do not repeat installation or browser login merely because a Skill starts. Connector auto is an explicit bootstrap policy, not this Skill's default and not permission to use its selected workspace. Handle `workspace_confirmation_required` by asking for a business target. Do not infer it from plan, order or current selection.

Choose the correct action

| User intent | Native command | Effect | |---|---|---| | Login when unauthed, target unknown | `edgeone login --interaction agent` | Browser authentication, then conversation selection if required | | Complete the pending login | `edgeone login --interaction agent --session <sessionId> --workspace <workspaceId>` | Uses the original one-use result in the original directory; normally no second browser login | | List workspaces | `edgeone workspace ls --json` | Discover IDs, names and availability; do not use for silent first-login orchestration | | Choose among current-account workspaces | `edgeone workspace use --interaction agent` | Returns neutral choices; without a sessionId this is not a pending browser login | | Switch/confirm a known workspace | `edgeone workspace use <workspaceId> --interaction agent` | Verifies/reuses cached credentials; missing credentials trigger authentication for that target | | Complete a pending workspace switch | `edgeone workspace use <workspaceId> --interaction agent --session <sessionId>` | Continue using the original returned result, in the same directory | | Switch account | `edgeone switch --interaction agent` | New account authentication; not a workspace switch |

Use the exact chosen ID, not a guessed ID from a name. On `selection_required`, stop business operations and ask the user by available workspace names. If sessionId is present, retain it internally and continue with the matching command above. If absent, issue `workspace use` with the chosen ID without inventing a session. Browser waiting links or exit 0 are not login success. Verify the final result and effective identity before continuing the original task. `already_logged_in` does not confirm a workspace switch: do not repeatedly run `login --workspace` against an already-authenticated account; use `workspace use`. Do not logout as a normal switching strategy.

For a known target while unauthed, the login command may include `--workspace <workspaceId>`. For an account already authenticated, this is not a substitute for `workspace use`. Choose the site on the unified browser page when no site was specified; only add `--site china|global` for an explicit user choice. Do not guess site from the desired project area. Allow the normal browser opener; use `--no-browser` only when a confirmed host owns opening the link. Keep the browser callback listener alive until the CLI returns its final result.

Verify identity and credentials

`edgeone whoami --json` is read-only: authenticated: true means authenticated; authenticated: false means explicitly unauthed; authenticated: null means verification failed. A network, service or local-file error must not trigger automatic relogin. Authentication success alone does not confirm a new business target. For an existing directory association, preserve its owning project/workspace; use cached owning-workspace credentials or targeted authentication as directed by the CLI, rather than re-linking to the global selection.

A global selection does not overwrite a local credential or shell token. After switching, verify the effective workspace in the same project directory. If it is still the old workspace, check only whether explicit envi