Rubber Duck vs Supabase AI Assistant

“The insight here is sharp: models are worst at finding their own mistakes. Using a second model as an independent reviewer is the right call, and it mirrors how good human code review actually works. I want to know which model pairs GitHub is using — the quality of the adversarial check will depend heavily on choosing models with genuinely different failure modes.”

“The primitive here is clear: natural-language-to-Postgres-RLS-policy translation, embedded directly in Studio with zero additional config. The DX bet is that the right moment to generate an RLS policy is when you're already looking at the schema, not when you've switched to a docs tab or an external chat window — and that bet is correct. RLS is genuinely one of those areas where developers make subtle, security-breaking mistakes not because they're careless but because the mental model for row-level predicates doesn't map cleanly to SQL syntax. The moment of truth is whether the generated policies are actually correct for edge cases like authenticated vs. anon roles, and if Supabase has trained this on their own policy library, that's a real advantage over asking GPT-4 the same question cold. My only flag: schema suggestions being 'suggestions' rather than automated migrations means you still own the migration file, which is correct but worth noting — this doesn't automate away the dangerous part, just the hard-to-think-about part.”

“This doubles your inference cost for every agentic operation, and GitHub hasn't published latency numbers. If the cross-model review adds 10-15 seconds to every agent step, it'll be disabled by most developers within a week. Catch rates vs. latency overhead is the key tradeoff and it hasn't been benchmarked publicly yet.”

“The category is AI-assisted database tooling, and the direct competitors are Cursor with a Postgres connection, GitHub Copilot in a SQL file, and just pasting your schema into Claude. Supabase wins specifically on context — the assistant knows your actual schema, your existing policies, and the Supabase-specific conventions around auth.uid() and storage policies, which a generic LLM doesn't have without prompt engineering. The scenario where this breaks is anything involving complex multi-tenant RLS with dynamic role hierarchies — the kind of policy a senior backend engineer would spend two hours whiteboarding will not come out correct on the first generation, and a developer who trusts it without auditing will have a security hole. What kills this in 12 months: nothing, actually — this is the rare case where the right outcome is that this becomes table-stakes infrastructure in every database IDE and Supabase just keeps it. They own the distribution.”

“Model ensembling for quality control is the obvious next step in agentic AI workflows, and GitHub shipping it in Copilot normalizes the pattern. In two years, single-model agent pipelines will feel as naive as shipping code without CI. Rubber Duck is the CI layer for agentic code generation.”

“The thesis Supabase is betting on: in 2-3 years, the primary interface for database configuration is natural language embedded in the IDE surface, not SQL written from memory — and the team that owns the IDE owns the configuration layer. That's a falsifiable claim: it requires LLM accuracy on security-critical SQL to reach a threshold where developers trust generation over authoring, which is a higher bar than it is for, say, boilerplate component code. The second-order effect that's underappreciated: if RLS policy generation becomes reliable, it shifts the security responsibility in small teams from 'we need a backend engineer who knows Postgres internals' to 'we need someone who can describe access rules in English' — that's a genuine expansion of who can build secure multi-tenant applications. Supabase is on-time to this trend, not early: Prisma, PlanetScale, and Neon are all moving toward intent-based database management. The infrastructure state where this wins is Supabase Studio as the default database IDE for the next generation of full-stack developers who never learned raw SQL.”

“Honestly, I'd love this for writing. Having a second AI with a completely different perspective review a draft before it goes out catches things the primary model is blind to — that's just good editing practice. The name 'Rubber Duck' is perfectly chosen; it captures the spirit of the feature better than any technical description could.”

“The job-to-be-done is sharp and singular: help developers write correct, non-trivial Postgres security policies without becoming RLS experts first. That's a job with genuine friction — I've watched competent engineers spend 45 minutes on a policy that should have taken 5, specifically because the feedback loop between writing a policy and testing it under different roles is slow. Onboarding here is essentially zero: you're already in Studio, you describe what you want in plain English, you get SQL. The opinion baked into this product is that security configuration should live in the same surface as schema design, not in a separate security tab or external tooling — and that's the right opinion. The gap I'd flag is that 'schema normalization suggestions' is a much vaguer feature than RLS generation and needs more product definition: does it detect missing foreign keys, redundant columns, or full 3NF violations? That distinction matters for whether it's useful or just noise.”