This page is part of an AI coding agent skill and is written for agents, not humans. For the human-readable Base44 docs, see the developer documentation.

base44 scaffold

Scaffolds a local project for an existing Base44 app. Use this when you already have a Base44 app (you know its app ID) and want to set up the local project files to work with it. Runs fully non-interactively, so it is safe for agents and CI.

Critical: When to Use Scaffold vs Create vs Link

Scenario	Command
Starting fresh, want a NEW Base44 app + project from a template	`npx base44 create`
You already have a Base44 app (by ID) and want local files for it	`npx base44 scaffold`
Have a local `base44/config.jsonc` but no `.app.jsonc`	`npx base44 link`

Syntax

npx base44 scaffold [name] [options]

Scaffolds into the current directory.

Arguments & Options

Argument/Option	Description	Required
`name`	Project name (positional). Defaults to the current directory name.	No
`--app-id <id>`	Existing Base44 app ID. Falls back to the `BASE44_APP_ID` environment variable.	Yes*
`--no-skills`	Skip AI agent skills installation (skills are installed by default)	No

*The app ID is required: provide it via --app-id or the BASE44_APP_ID environment variable. If neither is set, the command fails.

Examples

# Scaffold the current directory for an existing app
npx base44 scaffold --app-id app_123

# Scaffold the current directory with an explicit project name
npx base44 scaffold my-app --app-id app_123

# Provide the app ID via environment variable instead of the flag
BASE44_APP_ID=app_123 npx base44 scaffold

# Scaffold without installing AI agent skills
npx base44 scaffold --app-id app_123 --no-skills

What It Does

Resolves the app ID from --app-id or the BASE44_APP_ID environment variable
Applies the backend-only template to the current directory
Registers the project files against the existing app and writes base44/.app.jsonc with the app ID
Installs AI agent skills (unless --no-skills is passed)

Provisioning Handoff (Stripe Projects / projects.dev)

scaffold is the command to run after a Base44 app is provisioned through a Stripe Projects / projects.dev flow. Use scaffold, not create — the app already exists, so create would create a duplicate. When Base44 is provisioned that way, the credentials are injected into the environment under a BASE44_PROJECTS_ prefix (e.g. BASE44_PROJECTS_BASE44_APP_ID, BASE44_PROJECTS_BASE44_ACCESS_TOKEN, BASE44_PROJECTS_BASE44_REFRESH_TOKEN). The CLI automatically normalizes these to the bare names it uses (BASE44_APP_ID, BASE44_ACCESS_TOKEN, …). As a result:

App ID is resolved from BASE44_APP_ID automatically — no --app-id flag needed.
Authentication is seeded from BASE44_ACCESS_TOKEN / BASE44_REFRESH_TOKEN — no interactive npx base44 login needed.

So the entire post-provisioning step is just:

npx base44 scaffold

Run it from the directory where you want the project files. After scaffolding, push resources with npx base44 deploy.

Notes

Template: Always uses the backend-only template (Base44 configuration only — no frontend is generated).
Non-interactive: Never prompts. It does not push entities or deploy the site. Use npx base44 deploy afterward to push resources.
Existing app only: Unlike create, this does not create a new Base44 app — it links local files to the app ID you supply.
Authentication: Requires you to be authenticated (run npx base44 login first).
The .app.jsonc file should be git-ignored (it contains your app ID).

​base44 scaffold

​Critical: When to Use Scaffold vs Create vs Link

​Syntax

​Arguments & Options

​Examples

​What It Does

​Provisioning Handoff (Stripe Projects / projects.dev)

​Notes

base44 scaffold

Critical: When to Use Scaffold vs Create vs Link

Syntax

Arguments & Options

Examples

What It Does

Provisioning Handoff (Stripe Projects / projects.dev)

Notes