EdgeOne Pages Deployment Skill
Deploy any project to EdgeOne Pages.
⛔ Critical Rules (MUST follow — never skip)
- CLI version MUST be or higher. If the installed version is lower, reinstall. Do NOT proceed with an outdated version.
- NEVER truncate the deploy URL. The includes query parameters that are required for access. Always output the complete URL including all query string parameters — without them the page won't load.
- MUST ask the user to choose China or Global site before login. Never assume.
- MUST auto-detect the login method — browser login in desktop environments, token login in headless/remote/CI environments. Follow the decision table below.
- 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:
bash
# 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
Decision Table
| CLI version | Login status | Action |
|---|
| Not installed or version < 1.2.30 | — | → Go to Install CLI |
| ✓ | Logged in | → Go to Deploy |
| ✓ | Not logged in, has saved token | → Go to Deploy with Token (use saved token) |
| ✓ | Not logged in, no saved token | → Go to Login |
Install CLI
bash
npm install -g edgeone@latest
Verify:
must output
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 (
):
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
bash
# 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.
Token Login
Token login does
NOT use
. The token is passed directly in the deploy command via
.
Guide the user to get a token:
- Go to the console:
- 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 (auto-used next time)
- No — Use for this deployment only
If Yes:
bash
mkdir -p .edgeone
echo "<token>" > .edgeone/.token
grep -q '.edgeone/.token' .gitignore 2>/dev/null || echo '.edgeone/.token' >> .gitignore
Tell the user: "✅ Token saved to
and added to
."
Deploy
Browser-authenticated deploy
bash
# Project already linked (edgeone.json exists)
edgeone pages deploy
# New project (no edgeone.json)
edgeone pages deploy -n <project-name>
: auto-generate from the project directory name. The first deploy creates
automatically.
Token-based deploy
First check for a saved token:
bash
cat .edgeone/.token 2>/dev/null
- Saved token found → use it, tell the user: "Using saved token from "
- No saved token → ask the user to provide one (see Token Login above)
bash
# 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
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
bash
edgeone pages deploy -e preview
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
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 | MUST include the full query string ( and everything after it) — without these params the page won't load |
| Project ID | Value after | — |
| Console URL | Line after "You can view your deployment..." | — |
Show the user:
✅ Deployment complete!
- Access URL:
https://my-project-abc123.edgeone.cool?<auth_query_params>
- Console URL:
https://console.cloud.tencent.com/edgeone/pages/project/...
Error Handling
| Error | Solution |
|---|
command not found: edgeone
| npm install -g edgeone@latest
|
| Browser doesn't open during login | Use token login instead |
| "not logged in" error | 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 |
| 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:
Pure static projects skip this.
Local Development
bash
edgeone pages dev # http://localhost:8088/
Environment Variables
bash
edgeone pages env ls # List all
edgeone pages env pull # Pull to local .env
edgeone pages env add KEY val # Add
edgeone pages env rm KEY # Remove
Project Linking
Token Management
| Task | How |
|---|
| Save token | Stored in (auto-added to ) |
| Update token | Delete , then deploy again — you'll be prompted to enter and save a new one |
| Use saved token | Automatic — the agent reads before each token deploy |
Command Reference
| Action | Command |
|---|
| Install CLI | npm install -g edgeone@latest
|
| Check version | |
| Login (China) | edgeone login --site china
|
| Login (Global) | edgeone login --site global
|
| View login info | |
| Logout | |
| Switch account | |
| Init functions | |
| Local dev | |
| Link project | |
| Deploy | |
| Deploy new project | edgeone pages deploy -n <name>
|
| Deploy preview | edgeone pages deploy -e preview
|
| Deploy with token | edgeone pages deploy -t <token>
|