Keep the conversation going.
Remember how each user likes to read. Store the conversations that follow.
Test preference and conversation APIs against your database.
Set SUPABASE_URL and SUPABASE_SECRET_KEY (or SUPABASE_SERVICE_ROLE_KEY) in the Python server’s .env. Run supabase/migrations/001_preferences_conversations.sql in your Supabase SQL editor, restart the backend, then refresh.
Select a playground user
These are app test records, separate from Supabase Auth accounts.
Active user: select or create a user
Make reading feel personal
Save one preference record per user.
Save replaces the preference document with the complete form. It does not change the other playgrounds’ settings.
Storage response
The saved record is shown after each API action.
A place to pick up where you left off
Select a user and test a storage API. Your database response appears here.
⌘ Request & response inspectorView details +
LAST REQUEST
Run an API action.
LAST RESPONSE
No response yet.
Local admin playground. The backend uses a privileged Supabase key and selected user IDs are test-record scopes, not authenticated identities. Keep this endpoint local until application authentication is added. The other playgrounds do not automatically save here. Writes go to your configured Supabase project; no automatic retries or delete actions are exposed.