mirror of
https://github.com/supabase/supabase.git
synced 2026-09-06 18:11:51 +08:00
## I have read the [CONTRIBUTING.md](https://github.com/supabase/supabase/blob/master/CONTRIBUTING.md) file. YES ## What kind of change does this PR introduce? Chore / dependency upgrade. ## What is the current behavior? Studio is on AI SDK 6 (`ai` ^6.0.174, `@ai-sdk/react` ^3). Tool approvals still use the v6 `needsApproval` flag on individual tools. ## What is the new behavior? Upgrades Studio to AI SDK 7 (`ai` 7.0.59) and the matching `@ai-sdk/*` packages. Aligns call sites with v7 names (`instructions`, `isStepCount`, `onEnd`, `ToolExecutionOptions`). This is the bottom of stack #49171. Later layers add a shared Confirm card and AssistantQueryCell. ## Additional context - Stack: #49167 → #49168 → #49169 → #49170 - `needsApproval` on tools is left as-is in this PR so the upgrade can land independently. A follow-up can move those gates to `streamText({ toolApproval })` and `experimental_toolApprovalSecret`. - Independent of the notebook preview stack ([#49112](https://github.com/supabase/supabase/pull/49112), [#49159](https://github.com/supabase/supabase/pull/49159)), which should merge first before we wrap notebook proposals in Confirm. ## Test plan - [ ] `pnpm --filter studio test` for `lib/ai/tools/*` and assistant generate path - [ ] Assistant chat still streams and tool-approval SQL / Edge Function still pause for confirm - [ ] Evals still run with mock tools (`needsApproval: false` overrides) <!-- This is an auto-generated comment: release notes by coderabbit.ai --> ## Summary by CodeRabbit * **Improvements** * Updated AI-powered chat, onboarding, SQL, code completion, and recipe generation workflows for more reliable responses. * Streaming responses now better preserve reasoning and source information where available. * Improved tool privacy notices while preserving dynamically generated tool descriptions. * Refined AI response handling, including step limits and structured policy results. * **Bug Fixes** * Improved compatibility across AI-powered tool interactions and execution scenarios. <!-- end of auto-generated comment: release notes by coderabbit.ai -->
184 lines
6.7 KiB
TypeScript
184 lines
6.7 KiB
TypeScript
import type { JwtPayload } from '@supabase/supabase-js'
|
|
import { generateText, isStepCount, Output } from 'ai'
|
|
import { IS_PLATFORM } from 'common'
|
|
import { source } from 'common-tags'
|
|
import { NextApiRequest, NextApiResponse } from 'next'
|
|
import { z } from 'zod'
|
|
|
|
import type { AiOptInLevel } from '@/hooks/misc/useOrgOptedIntoAi'
|
|
import { getAIDetails } from '@/lib/ai/ai-details'
|
|
import { isExplorerEnabled } from '@/lib/ai/is-explorer-enabled'
|
|
import { getModel } from '@/lib/ai/model'
|
|
import { DEFAULT_COMPLETION_MODEL } from '@/lib/ai/model.utils'
|
|
import { RLS_PROMPT } from '@/lib/ai/prompts'
|
|
import { getTools } from '@/lib/ai/tools'
|
|
import { apiWrapper } from '@/lib/api/apiWrapper'
|
|
import { trustedUserEmail } from '@/lib/server/configcat'
|
|
|
|
const policySchema = z.object({
|
|
sql: z.string().describe('The generated Postgres CREATE POLICY statement.'),
|
|
name: z.string().describe('The name of the policy.'),
|
|
command: z
|
|
.enum(['SELECT', 'INSERT', 'UPDATE', 'DELETE', 'ALL'])
|
|
.describe('The SQL command this policy applies to.'),
|
|
definition: z
|
|
.string()
|
|
.optional()
|
|
.describe('The USING clause expression (for SELECT, UPDATE, DELETE).'),
|
|
check: z.string().optional().describe('The WITH CHECK clause expression (for INSERT, UPDATE).'),
|
|
action: z
|
|
.enum(['PERMISSIVE', 'RESTRICTIVE'])
|
|
.default('PERMISSIVE')
|
|
.describe('Whether the policy is PERMISSIVE or RESTRICTIVE.'),
|
|
roles: z.array(z.string()).default(['public']).describe('The roles this policy applies to.'),
|
|
})
|
|
|
|
const requestBodySchema = z.object({
|
|
tableName: z.string().min(1),
|
|
schema: z.string().default('public'),
|
|
columns: z.array(z.string()).optional(),
|
|
projectRef: z.string().min(1),
|
|
connectionString: z.string().min(1),
|
|
orgSlug: z.string().optional(),
|
|
message: z.string().optional(),
|
|
})
|
|
|
|
async function handler(req: NextApiRequest, res: NextApiResponse, claims?: JwtPayload) {
|
|
const { method } = req
|
|
|
|
switch (method) {
|
|
case 'POST':
|
|
return handlePost(req, res, claims)
|
|
default:
|
|
res.setHeader('Allow', ['POST'])
|
|
res.status(405).json({ data: null, error: { message: `Method ${method} Not Allowed` } })
|
|
}
|
|
}
|
|
|
|
export async function handlePost(req: NextApiRequest, res: NextApiResponse, claims?: JwtPayload) {
|
|
const authorization = req.headers.authorization
|
|
const accessToken = authorization?.replace('Bearer ', '')
|
|
|
|
if (IS_PLATFORM && !accessToken) {
|
|
return res.status(401).json({ error: 'Authorization token is required' })
|
|
}
|
|
|
|
const body = typeof req.body === 'string' ? JSON.parse(req.body) : req.body
|
|
const { data, error: parseError } = requestBodySchema.safeParse(body)
|
|
|
|
if (parseError) {
|
|
return res.status(400).json({ error: 'Invalid request body', issues: parseError.issues })
|
|
}
|
|
|
|
const { tableName, schema, columns = [], projectRef, connectionString, orgSlug, message } = data
|
|
|
|
let aiOptInLevel: AiOptInLevel = 'disabled'
|
|
|
|
if (!IS_PLATFORM) {
|
|
aiOptInLevel = 'schema'
|
|
}
|
|
|
|
if (IS_PLATFORM && orgSlug && authorization && projectRef) {
|
|
try {
|
|
const aiDetails = await getAIDetails({ orgSlug, projectRef, authorization })
|
|
|
|
aiOptInLevel = aiDetails.aiOptInLevel
|
|
} catch (error) {
|
|
return res.status(400).json({
|
|
error: 'There was an error fetching your organization details',
|
|
})
|
|
}
|
|
}
|
|
|
|
const explorerEnabled = await isExplorerEnabled(trustedUserEmail(claims?.email))
|
|
|
|
try {
|
|
const { modelParams, error: modelError } = await getModel({
|
|
provider: 'openai',
|
|
modelEntry: DEFAULT_COMPLETION_MODEL,
|
|
})
|
|
|
|
if (modelError) {
|
|
return res.status(500).json({ error: modelError.message })
|
|
}
|
|
|
|
// Closes the remote MCP connection opened in getTools when generation is done,
|
|
// if anything below throws, or if the client disconnects mid-generation so the
|
|
// connection isn't held until generateText resolves on its own (mirrors the
|
|
// request-scoped cleanup in generate-v4.ts).
|
|
const toolsAbortController = new AbortController()
|
|
req.on('close', () => toolsAbortController.abort())
|
|
req.on('aborted', () => toolsAbortController.abort())
|
|
// Fires when the response finishes or the connection drops.
|
|
res.on('close', () => toolsAbortController.abort())
|
|
try {
|
|
const tools = await getTools({
|
|
projectRef,
|
|
connectionString,
|
|
authorization,
|
|
aiOptInLevel,
|
|
accessToken,
|
|
isExplorerEnabled: explorerEnabled,
|
|
signal: toolsAbortController.signal,
|
|
})
|
|
|
|
const { output } = await generateText({
|
|
...modelParams,
|
|
stopWhen: isStepCount(5),
|
|
prompt: source`
|
|
You are a Postgres RLS (Row Level Security) expert.
|
|
Determine the most appropriate policies for the "${schema}"."${tableName}" table within a Supabase project.
|
|
|
|
${columns.length > 0 ? `Table columns: ${columns.join(', ')}` : 'No column metadata provided.'}
|
|
|
|
${message ? `User request: ${message}` : ''}
|
|
|
|
RLS Guide: ${RLS_PROMPT}
|
|
|
|
Requirements:
|
|
- Use the available planning and schema tools (like "list_policies" or "list_tables") to inspect the "${schema}" schema and existing policies before generating new ones.
|
|
- Ensure policies strictly adhere to the existing schema
|
|
- Return a curated list of recommended CREATE POLICY statements as JSON.
|
|
- Each policy must include: name, sql, command (SELECT/INSERT/UPDATE/DELETE/ALL), action (PERMISSIVE/RESTRICTIVE), roles (array of role names).
|
|
- Include "definition" (USING clause expression without the USING keyword) for SELECT, UPDATE, DELETE policies.
|
|
- Include "check" (WITH CHECK clause expression without the WITH CHECK keywords) for INSERT, UPDATE policies.
|
|
- Avoid duplicating existing policies and reference the public schema and typical Supabase best practices when deciding the coverage.
|
|
- Prefer PERMISSIVE policies unless a RESTRICTIVE policy is explicitly required
|
|
`,
|
|
tools,
|
|
output: Output.object({
|
|
schema: z.object({
|
|
policies: z.array(policySchema),
|
|
}),
|
|
}),
|
|
})
|
|
|
|
// Add table and schema to each policy from the request
|
|
const policies = (output?.policies ?? []).map((policy) => ({
|
|
...policy,
|
|
table: tableName,
|
|
schema,
|
|
}))
|
|
|
|
return res.json(policies)
|
|
} finally {
|
|
toolsAbortController.abort()
|
|
}
|
|
} catch (error) {
|
|
if (error instanceof Error) {
|
|
console.error(`AI policy generation failed: ${error.message}`)
|
|
return res.status(500).json({
|
|
error: 'Failed to generate policy. Please try again.',
|
|
})
|
|
}
|
|
return res.status(500).json({
|
|
error: 'An unknown error occurred.',
|
|
})
|
|
}
|
|
}
|
|
|
|
const wrapper = (req: NextApiRequest, res: NextApiResponse) =>
|
|
apiWrapper(req, res, handler, { withAuth: true })
|
|
|
|
export default wrapper
|