Supabase CLI v3: commands now run locally unless you add --remote, and hosted changes need --yes in CI (November 2026)

What you get

Supabase released CLI v3.0.0 on November 2, 2026, and since November 3 brew install supabase installs it. Supabase announced it as a breaking change on November 4. Anything that installs the CLI without a pinned version, such as a CI job or an AI coding agent, may already be on v3.

• Local by default: db push, db pull, db dump, migration list, gen types and the storage commands now target the local stack unless you pass --remote. --remote replaces --linked, --project-ref and --db-url, which still work but are deprecated.
• Hosted changes ask first: commands that change a hosted project ask for confirmation, defaulting to No. In CI they fail with HostedMutationConsentRequiredError unless you pass --yes. Piping y into a command no longer confirms it.
• Config: [inbucket] in supabase/config.toml is now [local_smtp], and supabase start fails on the old name. Flags and environment variables now win over config.toml, including [remotes.<name>] blocks.
• Other changes: pg-delta is the default diff engine, so db diff and db pull may write different SQL. secrets unset needs --all to remove every secret. Deprecated commands and flags are removed: running one exits with code 1 and prints its replacement. The CLI ships as one supabase executable; supabase-go is no longer installed.

Hosted projects, their data and self-hosted Supabase are not affected.

Prerequisites

• A project that uses the Supabase CLI (locally, in CI or through an AI coding agent)

Steps

1. Update to the latest v2 release first and run your workflows, including CI. v2.122.0 and later warn about removed items and changed defaults; fix each warning.
2. Rename the section in supabase/config.toml (and any block). The keys inside stay the same: