EdgeOne Pages Deployment Skill

Deploy any project to EdgeOne Pages.

⛔ Critical Rules (MUST follow — never skip)

1. 1. CLI version MUST be 1.2.30 or higher. If the installed version is lower, reinstall. Do NOT proceed with an outdated version.
2. NEVER truncate the deploy URL. The EDGEONE_DEPLOY_URL includes eo_token= and eo_time= query parameters — they are required for access. Always output the complete URL.
3. MUST ask the user to choose China or Global site before login. Never assume.
4. MUST auto-detect the login method — browser login in desktop environments, token login in headless/remote/CI environments. Follow the decision table below.
5. After token login, MUST ask if the user wants to save the token locally for future use.

---

Deployment Flow

Run these checks first, then follow the decision table:

CODEBLOCK0

Decision Table

CLI version	Login status	Action
Not installed or version < 1.2.30	—	→ Go to Install CLI
INLINECODE4 ✓

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 |

---

Install CLI

CODEBLOCK1

Verify: edgeone -v must output 1.2.30 or higher. If not, retry installation.

---

Login

1. Ask the user to choose a site

You MUST ask before running any login command. Use the IDE's selection control (ask_followup_question):

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)

2. Detect environment and choose login method

Condition	Method
Local desktop IDE (e.g. VS Code, Cursor, etc.)	Browser Login
Remote / SSH / container / CI / cloud IDE / headless

Token Login | | User explicitly requests token | Token Login |

Browser Login

CODEBLOCK2

Wait for the user to complete browser auth. The CLI prints a success message when done.

Token Login

Token login does NOT use edgeone login. The token is passed directly in the deploy command via -t.

Guide the user to get a token:

1. 1. Go to the console:

- China: https://console.cloud.tencent.com/edgeone/pages?tab=settings
- Global: https://console.intl.cloud.tencent.com/edgeone/pages?tab=settings

1. 2. Find API Token → Create Token → Copy it

⚠️ Remind the user: the token has account-level permissions. Never commit it to a repository.

3. Offer to save the token locally

After the user provides a token, MUST ask:

Would you like to save this token locally for future deployments?

• - Yes — Save to .edgeone/.token (auto-used next time)
• No — Use for this deployment only

If Yes:

CODEBLOCK3

Tell the user: "✅ Token saved to .edgeone/.token and added to .gitignore."

---

Deploy

Browser-authenticated deploy

CODEBLOCK4

INLINECODE15: auto-generate from the project directory name. The first deploy creates edgeone.json automatically.

Token-based deploy

First check for a saved token:

CODEBLOCK5

• - Saved token found → use it, tell the user: "Using saved token from .edgeone/.token"
• No saved token → ask the user to provide one (see Token Login above)

CODEBLOCK6

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).

Deploy to preview environment

CODEBLOCK7

Build behavior

The CLI auto-detects the framework, runs the build, and uploads the output directory. No manual config needed.

---

⚠️ Parse Deploy Output (Critical — read carefully)

After edgeone pages deploy succeeds, the CLI outputs:

CODEBLOCK8

Extraction rules:

Field	How to extract	⛔ Warning
Access URL	Full value after INLINECODE20	MUST include ?eo_token=...&eo_time=... — without these params the page won't load
Project ID

Value after EDGEONE_PROJECT_ID= | — |
| Console URL | Line after "You can view your deployment..." | — |

Show the user:

✅ Deployment complete!

• - Access URL: INLINECODE23
• Console URL: INLINECODE24

---

Error Handling

Error	Solution
INLINECODE25	INLINECODE26
Browser doesn't open during login

Use token login instead | | "not logged in" error | edgeone whoami to check, then re-login or use token | | Auth error with token | Token may be expired — regenerate at the console | | Project name conflict | Use a different name with -n | | Build failure | Check logs — usually missing deps or bad build script |

---

Appendix

Edge/Node Functions

For projects needing server-side functions, run before first deploy:

CODEBLOCK9

Pure static projects skip this.

Local Development

CODEBLOCK10

Environment Variables

CODEBLOCK11

Project Linking

CODEBLOCK12

Token Management

Task	How
Save token	Stored in .edgeone/.token (auto-added to .gitignore)
Update token

Delete .edgeone/.token, then deploy again — you'll be prompted to enter and save a new one | | Use saved token | Automatic — the agent reads .edgeone/.token before each token deploy |

Command Reference

Action	Command
Install CLI	INLINECODE33
Check version

edgeone -v | | Login (China) | edgeone login --site china | | Login (Global) | edgeone login --site global | | View login info | edgeone whoami | | Logout | edgeone logout | | Switch account | edgeone switch | | Init functions | edgeone pages init | | Local dev | edgeone pages dev | | Link project | edgeone pages link | | Deploy | edgeone pages deploy | | Deploy new project | edgeone pages deploy -n <name> | | Deploy preview | edgeone pages deploy -e preview | | Deploy with token | edgeone pages deploy -t <token> |