`config.toml` generated by `supabase link` has differences from remote project

[lautaropaske]

Describe the bug On a new project, supabase link doesn't create a ./supabase/config.toml, but CLI marks command as succesful while listing differences from remote config.toml. Current behavior makes it unclear if command is useful as it doesn't match remote linked config.toml.

WARNING: Local config differs from linked project. Try updating supabase/config.toml
diff supabase/config.toml <project-id>

workaround: do supabase init to create a config.toml file, add diffs sugested by CLI.

To Reproduce Steps to reproduce the behavior:

1. create a new project in supabase dashboard
2. create a new folder locally (i.e without existing supabase/config.toml), run supabase link
3. See error

Expected behavior On a fresh supabase link invokation, create if not exists a config.toml matching what's deployed currently in Supabase Dashboard.

Screenshots

System information

• command is not failing per se, but behaves unexpectedly
• Version of OS: MacOS Sequoia 15.3.2
• Version of CLI: 2.19.7

Additional context none.

[suspect-otw]

im getting same warning but mine got crushes after entering the pw of database

[ggbellotti]

+1

[victorpergher]

same here!

[suspect-otw]

same here!

i used data api for communication instead of linking the cli on windows command lines (powershell, cmd) still gives error

[boozedog]

i have the same issue

[ceferrari]

Same

[rzagmarz]

Does anyone managed to solve this?

I think the goal is that when linking a project both configs local and remote are the same no?

I’m facing same issue.

[krisnaw]

getting same error, how to solve this?

[spygi]

Same issue, command does not update the toml but also does not include everything in the diff e.g. SMTP-enabled (not secrets), rate limits etc..