Create and manage Volcengine cloud resources through the ve CLI with safe authentication and confirmation flows.
Coding
Volcengine Vefaas
Try itDeploy and manage serverless applications on Volcengine veFaaS. Use when the user wants to deploy web apps, manage functions (pull code, upload and deploy),...
What it does
Deploy and manage serverless applications on Volcengine veFaaS. Use when the user wants to deploy web apps, manage functions (pull code, upload and deploy), configure environment variables, inspect veFaaS projects, troubleshoot vefaas CLI/auth/framework issues, or work with veFaaS services.
The skill document
volcengine-vefaas: Volcengine FaaS CLI
vefaas is the command-line tool for Volcengine Function Service (veFaaS). It enables serverless application deployment, function management, and configuration through a streamlined workflow.
Installation
npm i -g https://vefaas-cli.tos-cn-beijing.volces.com/volcengine-vefaas-latest.tgz
Verify installation:
vefaas --version
Core Workflow
The typical deployment pattern:
- Check Node.js:
node --version(requires >= 18, recommended 20+)- If version is too low, switch using nvm (
nvm use 20) or fnm (fnm use 20), or manually install a newer version
- If version is too low, switch using nvm (
- Check CLI:
vefaas --versionto verify installation - Check Auth:
vefaas login --checkto verify login status- If not logged in, run
vefaas login --sso(opens browser, auto-completes when user authorizes - no manual input needed)
- If not logged in, run
- Deploy:
vefaas deploy --newApp --gatewayName $(vefaas run listgateways --first) --yes - Access:
vefaas domainsto view URLs
Quick Commands
| Purpose | Command |
|---|---|
| Check auth | vefaas login --check |
| Login (SSO) | vefaas login --sso (non-interactive: opens browser, auto-completes when authorized, recommended) |
| Login (AK/SK) | vefaas login --accessKey --secretKey |
| Init from template | vefaas init --template |
| Deploy new app | vefaas deploy --newApp --gatewayName $(vefaas run listgateways --first) --yes |
| Deploy existing | vefaas deploy --app --yes |
| List gateways | vefaas run listgateways --first |
| View URLs | vefaas domains |
| Set env var | vefaas env set KEY VALUE |
| View config | vefaas config list |
| Pull code | vefaas pull --func |
| Inspect project | vefaas inspect |
Global Options
| Option | Description |
|---|---|
-d, --debug | Enable debug mode for troubleshooting |
--yes | Non-interactive mode (required for CI/AI coding) |
--region | Region override (e.g., cn-beijing) |
Cookbooks
Step-by-step guides for common scenarios:
- Template Quickstart - Create and deploy from official templates
- Deploy Existing Code - Deploy your existing project
- Manage Functions - Manage functions (pull code, upload and deploy)
References
Detailed documentation on specific topics:
- Authentication - Login methods and credentials
- Configuration - Config files and settings
- Environment Variables - Managing env vars
- Framework Detection - Supported frameworks and auto-detection
- MCP Deployment - MCP protocol,
run.sh, proxy, and path-selection checks - Troubleshooting - Debug mode, common issues, and solutions
Important Notes
- Always use
--yesfor non-interactive mode in CI/CD and AI coding scenarios - Use
$(vefaas run listgateways --first)to get an available gateway - Config is stored in
.vefaas/config.jsonafter linking - Use
--debugor-dto troubleshoot issues
Related skills
Use when the user wants to deploy a local directory or GitHub repository to Volcengine and needs the project analyzed, the app shape understood, and a ranked...
Deploy a local project directory or Git repository to Volcengine as a running, reachable cloud service. USE WHEN: deploy to Volcengine, deploy to 火山引擎/火山, deploy this repo/project, publish current code, launch the app, run it in the cloud, expose it as a service, deploy to ECS/VKE/veFaaS, run on ECS, push to VKE, deploy as serverless/FaaS, or the user wants the agent to choose a Volcengine hosting target. If the user only asks which Volcengine deployment target to choose, use `volcengine-prepare` skill first. Not for creating a single standalone resource — use `volcengine-cli` skill for that.
Use when the user asks to analyze, consult, setup, manage, configure, or design a Volcengine Landing Zone, including organization, accounts, finance, identity, cloudtrail, or network infrastructure.
Use Terraform/IaC for Volcengine resources only when the user explicitly chooses Terraform/IaC, already has a Terraform workflow/state, or confirms they need...
Use when the user asks to purchase, subscribe, provision, open, or place an order for any Volcengine commercial product, or uses Chinese verbs such as "开通 / 购买 / 下单 / 买 / 售卖 / 想买 / 订购" together with a Volcengine product name. Trigger even when the user does not mention "sale" but expresses a clear provisioning intent.