---
title: How do I connect Supabase to codus?
question: connect supabase
area: integrations
order: 6
surface: desktop
audience: beginner
keywords: [supabase, connect supabase, management api, personal access token, sbp, run sql, database, edge functions, secrets, config, backend, hosting, super base, supbase]
related: [integrations-overview, connect-vercel, connect-wordpress]
updated: 2026-07-21
---

# How do I connect Supabase to codus?

Open **Integrations** in settings, find the **Supabase** card under **Hosting + deployment**, and click **Connect**. The card asks for a **personal access token** for the Supabase Management API, which you create in your Supabase dashboard, then paste in. Once connected, codus can list your projects, run SQL on your databases, and manage Edge Functions, secrets, and config. In the card's words, "Agents can stand up and operate your whole backend."

## Before you start

- You need a Supabase account. The token acts as you across all your organisations and projects, so connect a token from the account that owns the projects you want codus to work on.
- The token can run SQL on your real databases. codus treats destructive statements (things that delete or drop data) as strictly on-request, meaning an agent runs them only when you ask for that exact operation.

## Steps

1. Open the gear (**⚙**), click **See all settings →**, then click **Integrations**.
2. Find the **Supabase** card and click **Open Supabase access tokens**. Your browser opens supabase.com/dashboard/account/tokens.
3. On that page (**Account → Access tokens**), create a new personal access token. Give it a name like **codus**.
4. Copy the token. It starts with **sbp_**.
5. Come back to codus, paste the token into the box on the card, and click **Connect**.

## How do I know it worked?

The card shows a green **Connected** label with a project count, for example "Connected · 4 projects". That number is read from the Management API, so it confirms the token works.

## Common problems

- **The box would not accept my token.** Make sure you pasted the full token that starts with **sbp_**, with no trailing spaces.
- **codus sees the wrong projects.** The token acts as the account it belongs to. Create the token from the Supabase account that owns the projects you want, then reconnect.
- **I am nervous about SQL on production.** Ask the agent to describe what it will run first, and it will only make changes when you tell it to. Destructive statements are on-request by design.
- **I want to disconnect.** Click **Disconnect** and confirm. codus forgets the token; reconnect any time.