Base44: functions list, functions delete, and functions pull Commands

Base44

Base44 introduced three new CLI commands β€” functions list, functions delete, and functions pull β€” giving developers full terminal-based control over deployed backend functions. The functions deploy command was also enhanced with selective deployment by function name and a --force flag that removes remote functions no longer present locally.

Sources & Mentions

1 external resource covering this update


New Functions Management Commands in the Base44 CLI

Base44 expanded its command-line interface on March 15, 2026, with three new commands dedicated to managing deployed backend functions, along with significant improvements to the existing functions deploy command. These additions represent a meaningful step forward for developers who prefer to manage infrastructure entirely from the terminal.

functions list β€” Inspect Deployed Functions at a Glance

The functions list command retrieves all backend functions currently deployed to a Base44 project and displays them in the terminal. When functions include automations (scheduled triggers or database event listeners), the automation count appears alongside the function name, giving developers an immediate picture of what's live and what's active.

base44 functions list

This command is particularly useful when working across multiple machines or when the local project state may not reflect what's actually deployed β€” for example, after a collaborator has deployed a new function directly.

functions delete β€” Remove Deployed Functions by Name

The functions delete command removes one or more deployed backend functions from Base44's servers. Developers specify function names as positional arguments, separated by spaces or commas. Importantly, the command only affects the remote deployment β€” local project files are left untouched.

base44 functions delete <names...>

Base44's documentation includes a clear warning: deleting a function removes it from the platform entirely. Any endpoints, SDK calls, or automations that depend on the deleted function will immediately stop working.

functions pull β€” Sync Remote Functions to Local

The functions pull command downloads deployed backend functions from Base44 to the local project directory. Developers can pull all functions at once, or target a single function by name:

base44 functions pull [name]

Functions are downloaded to the base44/functions/ directory by default. The command retrieves both the function.jsonc configuration file and the source entry file for each function, and automatically skips functions whose local files already match the remote version. One important caveat: functions pull overwrites existing local files with the remote versions.

Updated: functions deploy with Selective Deployment and --force

The existing functions deploy command received two notable improvements. First, it now accepts one or more function names as optional arguments, enabling selective deployment:

base44 functions deploy [names...]

Second, a new --force flag was added. When deploying all functions (without specifying names), --force causes the command to delete any remote functions that no longer exist locally.

Summary of the New Commands

Command Purpose
functions list List all deployed backend functions
functions delete <names...> Remove deployed functions by name
functions pull [name] Download deployed functions locally
functions deploy [names...] Deploy specific functions by name
functions deploy --force Deploy all and remove remote-only functions

Each project supports a maximum of 50 backend functions. Functions are deployed from the base44/functions/ directory by default.


Mentioned onGitHub
Base44 CLI: functions list, delete & pull Commands | Yet Another Changelog