Supabase CLI errors after updating? v3 runs locally by default and asks before hosted changes
Ship ItChecked against the official source
Source checked 7 Nov 2026 · Published 8 Nov 2026 · Last reviewed 8 Nov 2026 · By Ctrl+Z Therapy (how we test)
The short answer
Supabase CLI v3.0.0 is the next major version, and npm, Homebrew, Scoop, the Linux packages, and supabase/setup-cli now install it by default (Supabase's changelog, November 4, 2026). Database commands target your local stack by default. Every command that changes a hosted project asks for confirmation first, and the default answer is No. When the CLI can't ask, as in CI, the command fails unless you pass --yes.
What to do
- Add --remote to every command that should reach your hosted project. One --remote flag replaces --linked, --project-ref, and --db-url.
- Add --yes to hosted changes that run unattended, in CI, deploy scripts or through an AI coding agent.
- If supabase start fails on [inbucket], rename [inbucket] to [local_smtp] in supabase/config.toml.
Good to know
- In CI, functions deploy, secrets set, config push and db push fail with HostedMutationConsentRequiredError until you add --yes.
- db push without --remote targets the local stack. It fails when no local stack is running.
- v3 changes the CLI only. Hosted projects, their data, and self-hosted Supabase are not affected.
Source
Checked on 7 Nov 2026. Prices, limits and settings change, so check the source before you rely on them.