base44 link
Links an existing local Base44 project to a Base44 app in the cloud. Use this when you have abase44/config.jsonc but haven’t connected it to a Base44 app yet.
Critical: When to Use Link vs Create
| Scenario | Command |
|---|---|
Starting fresh, no base44/ folder | npx base44 create |
Have base44/config.jsonc but no .app.jsonc | npx base44 link |
Project already linked (has .app.jsonc) | Already done, use deploy |
Syntax
Options
| Option | Description | Required |
|---|---|---|
-c, --create | Create a new project (skip selection prompt) | No |
-n, --name <name> | Project name (required when --create is used) | With --create |
-d, --description <description> | Project description | No |
--app-id <id> | App ID to link to an existing project (global flag, skips selection prompt) | No |
Non-Interactive Mode
For CI/CD or agent use: Create a new project:npx base44 link --create (missing —name)
WRONG: npx base44 link --create --app-id <id> (cannot use both)
RIGHT: npx base44 link --create --name my-app
RIGHT: npx base44 link --app-id <id>
Examples
What It Does
- Finds the
base44/config.jsoncin the current directory (or parent directories) - Verifies no
.app.jsoncexists (project not already linked) - Either:
- Creates a new Base44 app in the cloud (with
--create), OR - Links to an existing app (with
--app-idor interactive selection)
- Creates a new Base44 app in the cloud (with
- Writes the app ID to
base44/.app.jsonc
Requirements
- Must have
base44/config.jsoncin the project - Must NOT have
base44/.app.jsonc(usedeployif already linked) - Must be authenticated (run
npx base44 loginfirst)
Notes
- After linking, you can deploy resources with
npx base44 deploy - The
.app.jsoncfile should be git-ignored (contains your app ID)

