How to Configure Windsurf Supabase Approval

Published
Length
3 min read

Luis Felipe Dias

All posts

To set up windsurf supabase approval, pair editor command checks with strict database roles. You must review every terminal command or tool call before the agent runs it. Teams often let their AI coding tool use the default database admin password. When an agent holds broad database rights, one bad prompt can wipe live tables. It can also pull sensitive customer rows into the chat window. How native windsurf supabase approval and database roles work Cognition renamed Windsurf to Devin Desktop

Your coding agents run with your access.

Claude Code reaches prod with a developer's credentials, and approval prompts get clicked through. hoop.dev checks every query, masks sensitive data, and holds risky changes for a human.

To set up windsurf supabase approval, pair editor command checks with strict database roles. You must review every terminal command or tool call before the agent runs it. Teams often let their AI coding tool use the default database admin password. When an agent holds broad database rights, one bad prompt can wipe live tables. It can also pull sensitive customer rows into the chat window.

How native windsurf supabase approval and database roles work

Cognition renamed Windsurf to Devin Desktop in June 2026. The editor keeps the same features and uses the Cascade agent. This agent can run terminal commands on its own when you give permission. It opens a dedicated shell on your machine and loads your local profile. That means the agent can read any database keys saved in your shell variables. It also talks to external tools through Model Context Protocol servers.

On the database side, every Supabase project starts with a default postgres role. This role has admin rights, though Supabase blocks full superuser power to stop damage. The password you pick at project setup belongs to this admin role. Supabase warns teams not to share this password with outside tools. Instead, you should make a fresh database user for each tool you run. Supabase also includes built-in roles like anon for public requests and authenticated for logged-in users.

What native checks solve and what they leave open

Editor prompts and custom database roles solve the first layer of risk. The editor asks you before the agent runs a shell command. A custom Postgres role can limit which tables the agent can read or change. This stops an agent from dropping tables it does not own.

Still, local prompts and static roles leave a big gap during daily work. Clicking approve in the editor only checks that a command starts. When the agent runs a script or an MCP tool, the database only checks the login role. It does not pause risky queries in flight for a teammate to check. Also, if a table holds emails, phone numbers, or card numbers, a valid select query returns them in full. Native roles decide who logs in, not what each live statement does or returns.

Approval Chains & Escalation + End-to-End Encryption: architecture patterns and best practices

Continue reading? Get the full guide.

Free. No spam. Unsubscribe anytime.

Why local shell keys increase risk for AI agents

Because the editor loads your shell startup file, local secrets are easy to reach. Developers often put database URLs in their local shell files for convenience. Once the agent opens its terminal, those keys are live in the session. Even if you watch the chat prompt, a single script can run ten queries at once. You cannot approve one statement and reject the next inside that single script.

Teams need a way to inspect each query after the agent sends it. They also need a way to keep raw database passwords off developer laptops. Separating command approval from local editor clicks keeps live data safe during fast coding sessions.

Run guardrails and masking on the Postgres connection

Role grants and firewall rules are needed setup. Setup alone cannot check single SQL statements or mask sensitive rows in a response. By design, hoop.dev sits inline in the Postgres protocol beside Postgres, RDS, or Aurora as a sidecar for your Postgres. On every production query from an engineer or AI agent, hoop.dev decides whether to pass, mask, block, or hold it for approval.

First, hoop.dev guardrails refuse disallowed drops or deletes before they run, and risky statements can pause for human review. Next, hoop.dev data masking rewrites sensitive fields in returned rows in memory. Furthermore, hoop.dev holds SOC 2 Type II and logs every statement and verdict per resource. Check out the project on GitHub.

Frequently asked questions

Did Windsurf change its name to Devin Desktop?

Yes, Cognition renamed Windsurf to Devin Desktop on June 2, 2026. It keeps the same editor features and agent workflow, and old docs links now point to the new site.

Should I give the default Supabase postgres password to my AI agent?

No, the default postgres role has broad admin rights across your project. Supabase advises making a separate database user with narrow permissions for each outside tool or service.

Why are editor command prompts not enough for database safety?

Editor prompts only ask if a terminal command or script can start on your laptop. They do not inspect individual SQL statements in flight or rewrite sensitive fields like emails and card numbers in query results.

The query runs. The emails stay hidden.