What Scratch edits in Supabase
- Text and rich-text columns in any user-defined table
- JSON and JSONB columns
- Slug, title, and description fields
- Row-level edits without schema changes
How it works
Scratch pulls a table from your Supabase database. Each row becomes a local file. Your AI edits the prose columns. Primary keys, foreign keys, timestamps, computed columns, and check constraints stay where they are. The Supabase auth and storage schemas are excluded from discovery, so user accounts and uploaded files are out of scope. Validators enforce column constraints so the AI cannot write something the database would reject. You approve in Scratch. Scratch updates the rows through the standard Postgres driver.
The service role that Scratch uses bypasses Row-Level Security, so it can read and write any user-table regardless of policies. If you need a connector that honors RLS, ask Curtis. It is a roadmap question, not a code one yet.
Best for content tables (blog posts, product copy, knowledge base) that live in Supabase but do not have a CMS layer in front of them.