supabase pull orchestrates remote project setup

Introduced 2026-09-25 · score 0.91

HOW TO USE IT

When setting up local state from a linked remote Supabase project, run `supabase pull` to pull its config, database schema, and Edge Functions; it also fetches migration history automatically when `supabase/migrations` is missing or empty.

WHY THIS HELPS

Set up a local development environment from a remote Supabase project.

BEFORE THIS CHANGE

Previously, refresh config, migration history, database schema, and functions by running `config pull`, optionally `migration fetch`, `db pull`, and `functions download` individually.

REQUIREMENTS AND LIMITATIONS

• Version: 2.118.0
• --project-ref <project-ref-or-branch>: Selects a project ref or a branch name/UUID of the linked project; without it, targets the linked project.
• --dry-run: Shows the pull plan without writing or changing anything.
• --with-migration-history: Fetches remote migration history even when the local migrations directory already has files; matching local files can be overwritten.
• --force: Allows writing when config, migrations, or functions have uncommitted or untracked Git changes.
• --remote-label <name>: Selects the `[remotes.*]` config block for the config step.
• Prerequisite: Use CLI v2.118.0 or later for this command; it was introduced in v2.118.0.
• Prerequisite: The target defaults to the linked project. The database step requires Docker; without Docker, that step fails while config, migration-history, and functions steps can still run.

FIRST-PARTY EVIDENCE

• https://github.com/supabase/cli/releases/tag/v2.118.0
• https://github.com/supabase/cli/blob/v2.118.0/apps/cli/docs/supabase/pull.md

Check the installed version and the source before using it. Entry JSON

Report a problem with this card