EdgeOne Pages Deploy

intent

deploy any frontend or full-stack project to EdgeOne Pages (Tencent's edge hosting platform). use this skill when a user wants to deploy, publish, ship, host, launch, go live, or create a preview on EdgeOne Pages. examples: "deploy my app", "publish this site", "push this live", "deploy and give me the link", "create a preview deployment", "deploy to EdgeOne", or "ship to production".

inputs

CLI tool:

• EdgeOne CLI, installed globally via npm. minimum version 1.2.30 required. install with npm install -g edgeone@latest.

Project context:

• local project directory with buildable source code (framework auto-detected by CLI).
• optional: existing edgeone.json file (created on first deploy).

Authentication:

• choice between browser login (desktop IDEs) or token login (remote/headless/CI environments).
• browser login: requires interactive browser access.
• token login: requires API token from EdgeOne console (https://console.cloud.tencent.com/edgeone/pages or https://console.intl.cloud.tencent.com/edgeone/pages for global site).

Site selection:

• user must specify: China (console.cloud.tencent.com) or Global (console.intl.cloud.tencent.com).

Optional saved token:

• .edgeone/.token file (if user previously saved a token).

procedure

1. check CLI version: run edgeone -v. if not installed or version is below 1.2.30, run npm install -g edgeone@latest and verify version again. do not proceed with outdated CLI.

2. check login status: run edgeone whoami. output shows logged-in user or "not logged in" message.

3. check saved token: run cat .edgeone/.token 2>/dev/null. if file exists, token is available for use. if not, proceed to login.

4. ask user for site choice (China or Global): if not already logged in, use a selection prompt. present two options: China (console.cloud.tencent.com) or Global (console.intl.cloud.tencent.com). record the choice.

5. detect environment and choose login method (see decision points section). if local desktop IDE, use browser login. if remote/SSH/container/CI/cloud IDE or user requests token, use token login.

6. execute browser login (if applicable): run edgeone login --site china (or --site global). wait for user to complete authentication in opened browser. CLI prints success message when done.

7. execute token login (if applicable): guide user to EdgeOne console settings tab to create or copy API token. token is passed directly to deploy command via -t flag, not via login command. after deployment, ask user if they want to save token locally.

8. save token locally (if user chooses yes): create .edgeone/ directory with mkdir -p .edgeone. write token to .edgeone/.token. append .edgeone/.token to .gitignore if not already present. confirm with user.

9. check for existing project link: run cat edgeone.json 2>/dev/null. if file exists, project is already linked. if not, user will provide a project name or allow auto-generation from directory name.

10. execute deploy command:

    • if browser authenticated and project linked: edgeone pages deploy
    • if browser authenticated and new project: edgeone pages deploy -n <project-name>
    • if token authenticated (saved) and project linked: edgeone pages deploy -t <token>
    • if token authenticated (saved) and new project: edgeone pages deploy -n <project-name> -t <token>
    • the CLI auto-detects framework, runs build, uploads output directory.

11. parse deploy output: after successful deploy, CLI outputs multi-line response including EDGEONE_DEPLOY_URL=, EDGEONE_PROJECT_ID=, and console URL. extract complete URL from EDGEONE_DEPLOY_URL= field (must include eo_token= and eo_time= query parameters). extract project ID and console URL.

12. present results to user: show access URL (with full query params), console URL, and deployment confirmation. access URL is immediately usable and accessible.

decision points

if CLI not installed or version < 1.2.30:

• run npm install -g edgeone@latest immediately. do not skip this check. re-verify version with edgeone -v before proceeding.

if user is already logged in (checked via edgeone whoami):

• skip login steps. proceed directly to deploy (step 10).

if user is not logged in:

• ask user to choose China or Global site. this choice determines login endpoint.

if environment is local desktop IDE (VS Code, Cursor, etc.):

• use browser login. run edgeone login --site <china|global>. wait for user to complete browser authentication.

else if environment is remote, SSH, container, CI, cloud IDE, or headless:

• use token login. token is passed via -t <token> flag on deploy command, not via separate login command.

else if user explicitly requests token login:

• use token login regardless of environment.

if saved token exists at .edgeone/.token:

• read and use saved token automatically for deploy command. inform user "using saved token from .edgeone/.token".

else if no saved token exists:

• guide user to create token at EdgeOne console (site-specific URL). ask user to provide token string. after deployment, ask if user wants to save token locally.

if user answers yes to "save token locally":

• create .edgeone/ directory, write token to .edgeone/.token, add to .gitignore. skip if already done.

else if user answers no:

• do not save token. proceed with this deployment only. token will not be reused next time.

if edgeone.json exists:

• project is already linked. use -n flag is optional (existing project ID is used). run edgeone pages deploy (or with -t <token> if token auth).

else if edgeone.json does not exist:

• project is new. user must provide project name or allow auto-generation from directory name. use -n <project-name> flag.

if deploy output contains error (auth failure, token expired, project name conflict, build failure):

• see error handling table below. token expired requires regenerating token at console. project name conflict requires choosing different name. build failure requires checking logs and project dependencies.

if preview environment deployment requested:

• add -e preview flag to deploy command: edgeone pages deploy -e preview.

output contract

on successful deployment, output must include:

• access URL: complete string from EDGEONE_DEPLOY_URL= field, including ?eo_token= and eo_time= query parameters. format: https://<project-id>.edgeone.cool?eo_token=<token>&eo_time=<timestamp>. this URL must be fully functional and immediately accessible.

• project ID: extracted from EDGEONE_PROJECT_ID= field. format: pages-<alphanumeric>.

• console URL: extracted from deployment output or constructed. format: https://console.cloud.tencent.com/edgeone/pages/project/<project-id>/deployment/<deployment-id> (or .intl. subdomain for global).

• token saved confirmation (if applicable): message "token saved to .edgeone/.token and added to .gitignore".

data format:

• all URLs are plain strings, complete and untruncated.
• all query parameters are preserved.
• all extraction is read directly from CLI output.

outcome signal

user knows the skill worked when:

• deployment confirmation is displayed: "deployment complete" message with access URL, project ID, and console URL.
• access URL is immediately clickable and loads the deployed site (no authentication gate, because eo_token= and eo_time= params are included).
• console URL links to the deployment details page in EdgeOne dashboard.
• edgeone.json file now exists in project root (created automatically on first deploy).
• .edgeone/.token file exists in project root (if user saved token).
• .gitignore includes .edgeone/.token entry (if token was saved).
• user can visit the site URL and see live content immediately (no waiting for CDN propagation in normal cases).

---

critical rules (mandatory)

1. CLI version must be 1.2.30 or higher. if version is lower or CLI is not installed, reinstall immediately. do not proceed with outdated version.

2. never truncate the deploy URL. EDGEONE_DEPLOY_URL includes eo_token= and eo_time= query parameters. both are required for access. always output the complete URL.

3. always ask user to choose China or Global site before login. never assume. use a selection control.

4. auto-detect login method: browser login for local desktop IDEs, token login for remote/headless/CI environments. follow the decision table.

5. after token login, always ask if user wants to save token locally. this improves UX for repeated deployments.

---

detailed workflows

install CLI

npm install -g edgeone@latest

verify with edgeone -v. output must show version 1.2.30 or higher. if lower, retry installation. if still fails, check npm permissions or proxy settings.

site selection

present user with clear choice:

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)

record selection. use it for login endpoint.

browser login

# china site
edgeone login --site china

# global site
edgeone login --site global

CLI opens default browser automatically. user completes auth flow (Tencent account, MFA if enabled). CLI prints success when done. wait for user to confirm they finished.

edge case: if browser doesn't open, ask user to manually visit Tencent console and use token login instead.

token login

token login does not use edgeone login command. token is passed directly via -t flag on deploy command.

get token from console:

1. navigate to console URL (based on site choice):

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

2. find API Token section.

3. click Create Token or copy existing token.

4. copy token string (full alphanumeric value, no truncation).

remind user: token has account-level permissions. never commit to repository. tokens can expire or be revoked.

edge case: if token is invalid or expired, user must regenerate at console and provide new token.

save token locally

after successful token-based deploy, ask user:

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:

mkdir -p .edgeone
echo "<token>" > .edgeone/.token
grep -q '.edgeone/.token' .gitignore 2>/dev/null || echo '.edgeone/.token' >> .gitignore

confirm: "token saved to .edgeone/.token and added to .gitignore".

edge case: if .gitignore doesn't exist, create it or add line manually.

project linking

first deploy automatically creates edgeone.json with project ID. user does not need to run edgeone pages link separately unless relinking to a different project.

to relink:

edgeone pages link

CLI prompts for project selection from user's EdgeOne account.

deploy with browser auth (project already linked)

edgeone pages deploy

CLI auto-detects framework (React, Vue, Next.js, static, etc.), runs build command, uploads output to EdgeOne. no manual build step needed.

deploy with browser auth (new project)

edgeone pages deploy -n <project-name>

replace <project-name> with desired name or auto-generate from directory name. edgeone.json is created automatically.

edge case: if project name already exists under user's account, CLI returns conflict error. user must choose different name with -n <new-name>.

deploy with saved token (project already linked)

edgeone pages deploy -t $(cat .edgeone/.token)

or manually:

edgeone pages deploy -t <token>

CLI reads token from command line. no separate login command. token already contains site info, so no --site flag needed.

deploy with saved token (new project)

edgeone pages deploy -n <project-name> -t $(cat .edgeone/.token)

deploy to preview environment

edgeone pages deploy -e preview

creates preview URL (temporary, for testing before prod). same output parsing rules apply.

parse CLI output

after successful deploy, CLI outputs block like:

[cli][✔] Deploy Success
EDGEONE_DEPLOY_URL=https://my-project-abc123.edgeone.cool?eo_token=xxxx&eo_time=yyyy
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:

field	extraction rule	warning
access URL	full value after EDGEONE_DEPLOY_URL= including ?eo_token=...&eo_time=...	must not truncate query params or page won't load
project ID	value after EDGEONE_PROJECT_ID=	,
console URL	line after "you can view your deployment..."	,

present to user:

✅ deployment complete!

• access URL: https://my-project-abc123.edgeone.cool?eo_token=xxxx&eo_time=yyyy
• console URL: https://console.cloud.tencent.com/edgeone/pages/project/...

error handling

error	cause	solution
command not found: edgeone	CLI not installed	npm install -g edgeone@latest
version < 1.2.30	outdated CLI	npm install -g edgeone@latest, verify with edgeone -v
browser doesn't open during login	environment headless or display unavailable	use token login instead with -t <token>
"not logged in" after login command	session expired or not persisted	run edgeone whoami to check, then re-login or use token
auth error with token (401, 403)	token invalid, expired, or has wrong permissions	regenerate token at EdgeOne console, copy fresh token, re-deploy
project name conflict	name already exists under user's account	use different name with -n <new-name>
build failure during deploy	framework not detected, missing deps, or bad build script	check project package.json, install deps with npm install, verify build command, check CLI logs
"rate limited"	too many requests to EdgeOne API	wait 60 seconds, retry deploy
network timeout	connection lost to EdgeOne servers	check internet connection, retry deploy
empty result set (no output)	deploy process hung or crashed	kill process (ctrl-c), check logs, retry
.edgeone/.token file not readable	permissions issue	check file permissions with ls -la .edgeone/.token, ensure readable by current user

advanced usage

initialize edge functions (optional):

for projects using server-side functions or middleware, run before first deploy:

edgeone pages init

pure static projects skip this. CLI guides through function setup if functions detected in project.

local development:

edgeone pages dev

starts local dev server at http://localhost:8088/. mirrors EdgeOne Pages routing. useful for testing before deploy.

manage environment variables:

edgeone pages env ls          # list all vars in project
edgeone pages env pull        # download vars to local .env file
edgeone pages env add KEY val # add or update var
edgeone pages env rm KEY      # remove var

environment variables are project-scoped. useful for API keys, endpoints, secrets.

token management:

task	command / how
save token	mkdir -p .edgeone && echo "<token>" > .edgeone/.token and add to .gitignore
update token	delete .edgeone/.token, then deploy again. user prompted to enter and save new token
use saved token	automatic. CLI reads .edgeone/.token before each token-based deploy
revoke token	delete at EdgeOne console settings. CLI will fail with auth error until new token provided

switch accounts:

edgeone switch

logs out current user and prompts to login as different account.

logout:

edgeone logout

removes browser-based session. saved token at .edgeone/.token is not deleted.

---

credits: original procedure by vincentism (clawhub). enriched and restructured to Implexa standards.