Base44: Auth Commands for Managing App Authentication from the CLI
Base44Base44 introduced a suite of CLI commands for managing app authentication settings directly from the terminal, removing the need to visit the dashboard for common auth configuration tasks. Developers can now use auth pull to download their app's current login settings, auth password-login to enable or disable email/password login, and auth push to apply local changes to their live app. The workflow mirrors Base44's existing resource-sync pattern (pull → edit locally → push), making auth configuration part of the standard code-driven deployment cycle. Built-in safeguards prevent accidental lockouts by warning before pushing a config with no active login methods.
Sources & Mentions
3 external resources covering this update
New Auth CLI Commands for Configuration Management
Base44 expanded its command-line interface with a set of authentication management commands, giving developers full control over their app's login settings without leaving the terminal. Released on March 25, 2026, the feature brings authentication configuration into the same local-first, code-driven workflow that Base44 already uses for entities, functions, and connectors.
auth pull — Download Your Current Auth Config
The auth pull command fetches the app's current authentication configuration from Base44 and saves it to a local file in base44/auth/ by default (the path is configurable via config.jsonc). This gives developers a local snapshot of which login methods are active and allows them to version-control authentication settings alongside the rest of their project.
base44 auth pull
One important caveat: running auth pull overwrites any unsaved local changes to the auth config, so it should be used to sync down the canonical remote state.
auth password-login — Toggle Email/Password Login
With the auth password-login command, developers can enable or disable username/password authentication directly from the CLI:
base44 auth password-login enable
base44 auth password-login disable
This is the CLI equivalent of toggling the "Email and password" option in the dashboard settings. If disabling password login would leave the app with no active login method, Base44 warns the user and blocks the change until an alternative method (such as Google or SSO) is active — preventing accidental user lockouts.
Changes made with this command are local only until pushed with auth push or deploy.
auth push — Apply Auth Changes to Your Live App
Once the local auth config is updated, auth push uploads it to Base44 and applies it to the live application:
base44 auth push
An optional -y / --yes flag skips the confirmation prompt for use in automated workflows. As with auth pull, the CLI surfaces a final warning if the config being pushed would disable all login methods.
How It Fits the Base44 Workflow
These three commands complete a consistent local-first pattern for managing Base44 resources: pull the remote state, make changes locally, then push. Authentication settings can now be treated like any other resource in a Base44 project — editable in a text editor, diffable in version control, and deployable via the CLI. Teams working across environments or automating deployments will find this particularly useful for scripting auth configuration changes without manual dashboard visits.