fusebase-cli

Initialize, develop, and deploy Fusebase Apps projects using the fusebase command-line tool.

5|2|Updated Feb 9, 2026
One-click install
npx skills add https://github.com/ryan-haver/fusebase-mcp --skill fusebase-cli-ryan-haver
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: fusebase-cli
Source: https://github.com/ryan-haver/fusebase-mcp/tree/main/apps/client-portal-dashboard/.claude/skills/fusebase-cli
Command: npx skills add https://github.com/ryan-haver/fusebase-mcp --skill fusebase-cli-ryan-haver

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Managing Fusebase Apps projects requires many platform-specific operations—creating apps, configuring permissions, running dev servers, deploying builds, and managing environments—that are error-prone when done manually through the UI or raw API calls. ## Core Features & Use Cases - Project Lifecycle Management: Initialize projects with fusebase init, scaffold SPA or backend templates, and register apps with declarative fusebase.json manifests. - Permissions & Access Control: Set dashboard view permissions (dashboardView.dashboardId:viewId.read,write) and access principals (visitor, orgRole:member, portal-scoped roles) at app creation time. - Dev & Deploy Workflows: Run local dev servers with hot reload and API proxying, then deploy apps with fusebase deploy, including isolated SQL store provisioning and RLS verification. - Use Case: An agent scaffolds a React SPA, registers it with fusebase app create including dashboard permissions, starts the dev server for testing, and deploys to production—all through CLI commands. ## Quick Start Ask the agent to initialize a new Fusebase app project and start the local dev server using the fusebase CLI.

Frequently Asked Questions about fusebase-cli

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create a new Fusebase app from the command line?▼

Run fusebase app create with the six required options: --name, --subdomain, --path, --dev-command, --build-command, and --output-dir. Add --permissions at creation time if the app needs dashboard view access, since that is the correct stage to set them.

How do I deploy Fusebase apps to production?▼

Run fusebase deploy from the project root. It installs dependencies, runs lint, builds each app, uploads the output directory, and activates the new version. Use --app to deploy a single app or --force to redeploy everything.

Should I ever write an app id manually in fusebase.json?▼

No. The apps[] array is declarative: each entry carries subdomain, name, and path but omits the platform app id. Hand-writing an id and then running app create causes a double-registration conflict; fusebase deploy resolves and writes back ids automatically.

Can I run the fusebase CLI in CI or non-interactive agent shells?▼

Yes. Without a TTY, fusebase init behaves as if --yes were passed: it never prompts and exits with code 1 if any required flag value is missing. Authenticate via the FUSEBASE_API_KEY environment variable and answer every prompt with a flag.

What is the format for dashboard view permissions in the fusebase CLI?▼

Permissions use the format dashboardView.dashboardId:viewId.privileges, where privileges are read, write, or read,write, and multiple entries are separated by semicolons. Gate privileges like app_api.<namespace>.<capability>.<action> are added to the app's Gate permissions instead.

Why did fusebase deploy fail with exit code 3?▼

Exit code 3 means the authenticated account may not manage apps in this organization. Re-run fusebase auth with an account that has app management rights, then retry the deploy.