Skip to content

Vifu CLI

The Vifu CLI is the developer tool for local game projects.

Use it to set up projects, build static web output, deploy playable cloud games, publish, and understand deploy errors.

Install

bash
curl -fsSL https://vifu.dev/cli | bash
vifu --help

npm remains available when the native installer is not available:

bash
npm install -g @vifu/cli@alpha
vifu --help

Project-local:

bash
npm install --save-dev @vifu/cli@alpha
npx vifu --help

Create projects with the npm initializer:

bash
npm create @vifu/vifu my-game -- --template vanilla --no-interactive

Create an account at vifu.ai, then log in:

bash
vifu login

Common Commands

CommandPurpose
vifu loginSign in for deploy and publish workflows.
vifu logoutSign out for the current API environment.
vifu logout --allClear all cached Vifu credentials.
vifu setupDetect and configure the current game project.
vifu buildBuild the project from the current directory.
vifu build ./gameBuild another project directory.
vifu runServe or run a local game project.
vifu testRun supported local game test workflows.
vifu deployBuild, validate, upload, and create a playable cloud URL.
vifu publishLower-level publish command for prepared builds and marketplace flows.

Deploy

bash
vifu deploy

What happens:

  1. Run project setup when it is missing and the project can be detected.
  2. Validate the project setup.
  3. Build the project unless --no-build is passed.
  4. Check the built game files.
  5. Upload only if validation passes and the artifact changed.
  6. Share a playable URL unless --no-share is passed.

Useful flags:

bash
vifu deploy --dry-run
vifu deploy --yes
vifu deploy --no-setup
vifu deploy --no-build
vifu deploy --no-share
vifu deploy --name my-stable-game-name

Manage Games

bash
vifu games list
vifu games share <game-id>
vifu games submit <game-id>
vifu games delete <game-id>

Management commands use the same Vifu Cloud account as deploy.

Optional Diagnostics

bash
vifu manifest check
vifu manifest explain

You usually do not need these before vifu deploy; deploy checks the manifest for you. Use them only when you want a quick local diagnosis or CI check without building or uploading.

Existing Projects

To adapt an existing browser game:

  1. Run vifu setup.
  2. Confirm the HTML entry, build command, and build output.
  3. Build to static browser files.
  4. Replace direct AI/backend calls with the Vifu SDK.
  5. Run vifu deploy.

Read Deploy Policy before adapting games that import JavaScript from a CDN or call external AI APIs.

For coding-agent workflows, install the separate Vifu Agent Skill.