Settings
AI Builder
Powers AI code generation and App Doctor diagnostics
ANTHROPIC_API_KEY
Your Anthropic API key — powers all AI features, used server-side only
GITHUB_TOKEN (env var)
Optional server env var for AI Builder Stage 2 export. You can also connect GitHub via Platform Connections.
Platform Connections
Connect GitHub, Vercel, Supabase, Cloudflare, and Railway. Save and test tokens with real provider verification.
Tokens are stored encrypted server-side and never returned to your browser. Each connection can be tested with a live provider check. Deployment automation is planned for Phase 2.
Manage ConnectionsSupabase
Database and authentication for ShiftStack
NEXT_PUBLIC_SUPABASE_URL
Supabase project endpoint
NEXT_PUBLIC_SUPABASE_ANON_KEY
Supabase public anonymous key
Environment variables are managed in your deployment settings and are never exposed beyond what Supabase requires.
Account
Authentication is handled by Supabase Auth
User accounts, sessions, and password management are handled entirely by Supabase. To manage users, update email/password policies, or configure OAuth providers, visit the Supabase Authentication dashboard.
Open Supabase DashboardNext Steps
Recommended actions to complete your setup
- 1
Connect GitHub for AI Builder export
Add your GitHub token via Settings → Connections so AI Builder can push generated code to a new repository.
- 2
Set production env vars
Add NEXT_PUBLIC_SUPABASE_URL, NEXT_PUBLIC_SUPABASE_ANON_KEY, SUPABASE_SERVICE_ROLE_KEY, and ANTHROPIC_API_KEY in your Coolify environment variables.
- 3
Configure Row Level Security
Ensure all Supabase tables have RLS enabled and policies scoped to auth.uid() so users only access their own data.
- 4
Enable Supabase backups
Turn on Point-in-Time Recovery in your Supabase project settings to protect against accidental data loss.
Need help?
Find answers to common questions about AI Builder, App Doctor, context attachments, GitHub export, and platform integrations.
View FAQEnvironment Status
Runtime configuration summary for this deployment
All required environment variables are configured. Environment values are managed in your deployment settings and are never exposed to the browser beyond what is explicitly prefixed NEXT_PUBLIC_.