Deploy any project to EdgeOne Pages.
1.2.30 — reinstall if lower. Never proceed with an outdated version.EDGEONE_DEPLOY_URL includes query parameters required for access. Always output the complete URL.Before executing any edgeone CLI command (install, login, deploy, etc.), set the following environment variable in the current shell session:
export PAGES_SOURCE=skills
Or prefix each command inline:
PAGES_SOURCE=skills edgeone pages deploy
This tells the platform that the deployment is triggered from an AI skill context.
Run these checks first, then follow the decision table:
# Check 0: Set environment variable (required before any edgeone command)
export PAGES_SOURCE=skills
# Check 1: CLI installed and correct version?
edgeone -v
# Check 2: Already logged in?
edgeone whoami
# Check 3: Project already linked?
cat edgeone.json 2>/dev/null
# Check 4: Saved token exists?
cat .edgeone/.token 2>/dev/null
| CLI version | Login status | Action |
|---|---|---|
| ------------- | ------------- | -------- |
| Not installed or < 1.2.30 | — | → Go to Install CLI |
≥ 1.2.30 ✓ | Logged in | → Go to Deploy |
≥ 1.2.30 ✓ | Not logged in, has saved token | → Go to Deploy with Token (use saved token) |
≥ 1.2.30 ✓ | Not logged in, no saved token | → Go to Login |
npm install -g edgeone@latest
Verify: edgeone -v — confirm output is 1.2.30 or higher. Retry installation if not.
Before triggering any login flow, explain to the user why this step is needed and what to expect. Do not silently launch a browser window.
Tell the user:
> You need to log in or register an EdgeOne Pages account. Here's what to expect:
> - Why login is required: Deployment uploads your build output to your own account, generating a unique access URL and project record.
> - What you get for free: EdgeOne Pages offers a free tier with global CDN acceleration, automatic HTTPS, and custom domain binding — typically more than enough for personal projects.
> - What happens next: I'll run edgeone login, and your default browser will open the Tencent Cloud login page. Please complete the login/registration and authorize access, then come back here.
> - If you get stuck: If the browser doesn't open, or the CLI keeps waiting after you've logged in, let me know — I'll switch to Token login instead.
If the user does not respond for an extended period (e.g., more than 1–2 minutes), proactively ask about their status (whether the browser opened, any errors, or if they want to switch to Token login). Do not wait indefinitely.
Use the IDE's selection control (ask_followup_question) before running any login command:
> Choose your EdgeOne Pages site:
> - China — For users in mainland China (console.cloud.tencent.com)
> - Global — For users outside China (console.intl.cloud.tencent.com)
| Condition | Method |
|---|---|
| ----------- | -------- |
| Local desktop IDE (VS Code, Cursor, etc.) | Browser Login |
| Remote / SSH / container / CI / cloud IDE / headless | Token Login |
| User explicitly requests token | Token Login |
# China site
edgeone login --site china
# Global site
edgeone login --site global
Wait for the user to complete browser auth. The CLI prints a success message when done.
⚠️ Browser Session Reuse Trap: If the user previously logged into a different site (e.g., logged into Global site before, now trying China site, or vice versa), the browser may silently reuse the old Tencent Cloud session. The CLI will appear to succeed, but actually binds to the wrong account — subsequent deploy will fail with auth errors or whoami shows an unexpected account.
If this happens, guide the user to:
console.cloud.tencent.com and console.intl.cloud.tencent.com) first, then re-run edgeone login.Token login does NOT use edgeone login. Pass the token directly in the deploy command via -t.
Guide the user to obtain a token:
⚠️ Remind the user: the token has account-level permissions. Never commit it to a repository.
After the user provides a token, ask:
> Save this token locally for future deployments?
> - Yes — Save to .edgeone/.token (auto-used next time)
> - No — Use for this deployment only
If Yes:
mkdir -p .edgeone
echo "<token>" > .edgeone/.token
grep -q '.edgeone/.token' .gitignore 2>/dev/null || echo '.edgeone/.token' >> .gitignore
Confirm to the user: "✅ Token saved to .edgeone/.token and added to .gitignore."
# Project already linked (edgeone.json exists)
edgeone pages deploy
# New project (no edgeone.json)
edgeone pages deploy -n <project-name>
edgeone.json automatically.
First check for a saved token:
cat .edgeone/.token 2>/dev/null
.edgeone/.token"# Project already linked
edgeone pages deploy -t <token>
# New project
edgeone pages deploy -n <project-name> -t <token>
The token already contains site info — no --site flag needed.
After a successful deploy with a manually-entered token, ask if the user wants to save it (see "Offer to save the token locally" above).
edgeone pages deploy -e preview
The CLI auto-detects the framework, runs the build, and uploads the output directory. No manual config needed.
After edgeone pages deploy succeeds, the CLI outputs:
[cli][✔] Deploy Success
EDGEONE_DEPLOY_URL=https://my-project-abc123.edgeone.cool?<auth_query_params>
EDGEONE_DEPLOY_TYPE=preset
EDGEONE_PROJECT_ID=pages-xxxxxxxx
[cli][✔] You can view your deployment in the EdgeOne Pages Console at:
https://console.cloud.tencent.com/edgeone/pages/project/pages-xxxxxxxx/deployment/xxxxxxx
Extraction rules:
| Field | How to extract | ⛔ Warning |
|---|---|---|
| ------- | --------------- | ----------- |
| Access URL | Full value after EDGEONE_DEPLOY_URL= | Include the full query string (? and everything after) — without these params the page will not load |
| Project ID | Value after EDGEONE_PROJECT_ID= | — |
| Console URL | Line after "You can view your deployment..." | — |
Show the user:
> ✅ Deployment complete!
> - Access URL: https://my-project-abc123.edgeone.cool?
> - Console URL: https://console.cloud.tencent.com/edgeone/pages/project/...
>
> ℹ️ Note: This preview URL is for quick deployment verification. When accessed from mainland China, the link may become restricted (e.g., 401) after some time or when shared, due to domain ICP filing status or CDN acceleration policies. For long-term stable public access, bind a custom domain with proper ICP filing.
| Error | Solution |
|---|---|
| ------- | ---------- |
command not found: edgeone | Run npm install -g edgeone@latest |
| Browser does not open during login | Switch to token login |
| "not logged in" error | Run edgeone whoami to check, then re-login or use token |
| Auth error with token | Token may be expired — regenerate at the console |
Login appears successful but deploy reports auth error | Browser reused a session from the wrong site, binding the wrong account. Click "Sign in with a different account" on the login page, or log out from all Tencent Cloud consoles first |
edgeone whoami shows an unexpected account | Same issue: browser session reuse. Click "Sign in with a different account" or log out from all consoles and re-login |
| Project name conflict | Use a different name with -n |
| Build failure | Check logs — usually missing deps or bad build script |
For CLI command reference, environment variables, local dev setup, and token management details, see references/command-reference.md.
共 7 个版本