1What FoxPlug reads from Supabase
These are the exact things it reads, and nothing else.
| What | The details it takes |
|---|---|
| Your projects | id (ref) and name of each project the token can see; the first 8 are read; the name is shown in the success line ('Name and 3 more projects') |
| Edge functions per project: name and version | slug (or name) and version of each deployed function, one moment per function and version |
| Edge functions per project: when it changed | updated at (else created at), used only to skip functions older than the last read (7 days on a first read) |
| Database migrations per project: name | the migration name, with underscores turned into spaces so the line reads as words |
| Database migrations per project: version | the version, a UTC timestamp (YYYYMMDDHHMMSS), parsed into the time the migration shipped and used for the look-back window |
2Moments it finds, and what each becomes
A moment is one thing that happened in Supabase worth a second look. Each one is scored, then it becomes a post, a changelog entry, a thing to fix or an idea to email, or it is skipped.
an edge function is deployed (new function or new version)
The moment is titled like this: Deployed function send-invoice
You ship version 4 of a made-up function called send-invoice in the project Billing. On Check for what's new FoxPlug writes 'Deployed function send-invoice' with the line 'Shipped the send-invoice edge function in Billing (version 4).' It is scored like any other update, so a routine deploy may be skipped while a meaningful one can become a post.
a database migration is applied
The moment is titled like this: Shipped migration: add team invites table
A migration named add team invites table lands in the project Billing. FoxPlug writes 'Shipped migration: add team invites table' and 'Applied a database migration (add team invites table) in Billing.' The name is shown as plain words, never with underscores.
10 or more edge functions are deployed on the same day
The moment is titled like this: Redeployed 32 functions on 2026-11-09
You redeploy 32 functions in one morning. Instead of 32 separate updates FoxPlug writes one: 'Redeployed 32 functions on 2026-11-09', with the line 'Shipped 32 edge functions in one pass:' followed by the function names. Each folded deploy is recorded in a rejections table with the reason.
3How the brain uses it
The rules below are the ones that apply to Supabase. The same rules, with worked examples, are on the brain page.
- Supabase edge-function deploys and shipped database migrations become updates, the same way a deploy from a host does. How the brain decides
- Reads happen only when you press Build the brief or Check for what's new. How the brain decides
- Reads are read-only; nothing is changed in your tools. How the brain decides
4Set up Supabase in a few steps
Access: personal access token (starts sbp_). What to give it: account-scoped token — every org and every project you own.
- Open supabase.com/dashboard/account/tokens.
- Click Generate new token and name it FoxPlug.
- Choose a scoped token (not Classic), pick the one project you want FoxPlug to watch, and set each permission to Read.
- Click Generate. The token is shown only once: copy the token starting with sbp_ and paste it into FoxPlug before leaving the screen.
- Press Connect.
5Limits worth knowing
Where it stops, so nothing surprises you.
- Only the first 8 projects on the token are read.
- A first read looks back 7 days; later reads start from the last read.
- 10 or more function deploys on the same day are folded into one moment; migrations are never folded.
- If one project's functions or migrations cannot be read, the others still are; the failure is only logged.
- The in-app guide says the token is shown once at creation; lose it and you make a new one.
6What it never reads
Read only means read only, and the list below is what the code leaves alone.
- Rows in your database (no data address is called; only the list of projects, functions and migrations)
- The code of your edge functions (only name, version and update time are used)
- The SQL inside a migration (only its name and version are used)
- Anything it writes back: no deploy, migration or setting is changed
7Questions
Does FoxPlug read my database?
No. The code lists your projects, then the edge functions and the migrations of each, and uses names, versions and times. It never queries a table and never reads function code or migration SQL.
Which Supabase token should I make?
A scoped token limited to the one project you want watched, with each permission set to Read. The in-app guide warns that a Classic token (shown with a Legacy badge) covers every organisation and project with full access, and says to avoid it.
Why did thirty deploys become one update?
Ten or more function deploys on one day are treated as one piece of work. FoxPlug writes a single 'Redeployed N functions' update that lists them, and records each folded deploy with the reason.
I lost the token. Can I see it again?
No. Supabase shows it once when you generate it. Delete it and make another, as the in-app guide says.
FoxPlug reads this tool only when you press Check for what's new, and only to read. Plans and limits are on the pricing page. Questions: support.