mirror of
https://github.com/supabase/supabase.git
synced 2026-10-15 06:09:08 +03:00
Orgs with the HIPAA add-on had the Assistant's opt-in level forced to `disabled` on any project marked High Compliance, regardless of what the org picked in its AI settings. The restriction predated our AI provider BAAs. The consequence is those users see the Assistant failing to answer questions about their data w/ no clear path how to fix it, even though the LLM provider supports this use case. This PR removes these Assistant restrictions on the server and client so those projects honor the org's chosen level. Braintrust conversation tracing is unchanged and still blocked for these projects, see [this test case](https://github.com/supabase/supabase/blob/b9800ccf16/apps/studio/lib/ai/braintrust-logger.test.ts#L16-L20). See [comments](https://linear.app/supabase/issue/AI-1153/allow-hipaa-orgs-to-opt-in-to-assistant-data-access-for-high#comment-485a0d46) for legal approval and conditions. The client-side changes enable features like "Debug with AI" on SQL query failures, “Generate/Rename with AI” for snippet titles, and generated Assistant chat titles for these customers. The AI opt-in copy now adds a reminder to obtain consent from data subjects, linking the [shared responsibility model](https://supabase.com/docs/guides/deployment/shared-responsibility-model) based also on [this comment](https://linear.app/supabase/issue/AI-1153/allow-hipaa-orgs-to-opt-in-to-assistant-data-access-for-high#comment-f81ee610). <img width="400" alt="CleanShot 2026-09-17 at 5 01 02 PM@2x" src="https://github.com/user-attachments/assets/d02123f2-3e32-4d83-9f98-7d15e59222ef" /> To test with a HIPAA-enabled project in staging, you can use this [Plan Change [Staging]](https://app.hex.tech/supabase/app/Plan-Change-Staging-032BD32jo1EaisCS85qunf/latest) Hex to add the HIPAA add-on. Once the add-on is present, you can turn on High Compliance from a project's settings. Also in org settings, crank up the Assistant data opt-in level and verify the Assistant is able to answer questions about the project's data. My results testing with opt-in level "Schema, Logs & Database Data": | High compliance setting | Data opt-in working | |--------|--------| | <img width="1302" height="422" alt="CleanShot 2026-09-17 at 5 03 36 PM@2x" src="https://github.com/user-attachments/assets/c416371b-2eb8-49df-9c07-6d8eababb443" /> | <img width="1566" height="1516" alt="CleanShot 2026-09-17 at 5 05 14 PM@2x" src="https://github.com/user-attachments/assets/39624355-7f8f-46ce-9f08-a8acfb9da830" /> | Closes AI-1153 <!-- This is an auto-generated comment: release notes by coderabbit.ai --> ## Summary by CodeRabbit ## New Features - AI-assisted query renaming, snippet title generation, debugging, and tools now follow organization AI opt-in settings rather than project HIPAA status. - Debugging assistance and AI actions remain available for eligible users without additional HIPAA-based blocking. - AI metadata warnings consistently show standard opt-in messaging and permission settings. - AI settings remind users to obtain consent before entering personal data and link to shared responsibility guidance. <!-- end of auto-generated comment: release notes by coderabbit.ai --> --------- Co-authored-by: Joshen Lim <joshenlimek@gmail.com>
98 lines
3.0 KiB
TypeScript
98 lines
3.0 KiB
TypeScript
import { ToolSet } from 'ai'
|
|
import { IS_PLATFORM } from 'common'
|
|
|
|
import { filterToolsByOptInLevel } from '../tool-filter'
|
|
import { getFallbackTools } from './fallback-tools'
|
|
import { getIncidentTools } from './incident-tools'
|
|
import { getMcpTools } from './mcp-tools'
|
|
import { getNotebookTools } from './notebook-tools'
|
|
import { getReportTools } from './report-tools'
|
|
import { getSchemaTools } from './schema-tools'
|
|
import { getStudioTools } from './studio-tools'
|
|
import { getSupportLifecycleTools } from './support-tools'
|
|
import { AiOptInLevel } from '@/hooks/misc/useOrgOptedIntoAi'
|
|
|
|
export const getTools = async ({
|
|
projectRef,
|
|
connectionString,
|
|
authorization,
|
|
aiOptInLevel,
|
|
accessToken,
|
|
baseUrl,
|
|
supportMode,
|
|
isExplorerEnabled,
|
|
signal,
|
|
}: {
|
|
projectRef: string
|
|
connectionString: string
|
|
authorization?: string
|
|
aiOptInLevel: AiOptInLevel
|
|
accessToken?: string
|
|
baseUrl?: string
|
|
supportMode?: boolean
|
|
// Notebooks haven't shipped yet — they live behind the Explorer feature flag, so the
|
|
// assistant must not advertise list_notebooks/get_notebook until the caller confirms the
|
|
// flag is on for this user.
|
|
isExplorerEnabled?: boolean
|
|
// Required: tools fetched from the remote MCP server hold an HTTP connection
|
|
// that is closed when this signal aborts (i.e. when the request ends).
|
|
signal: AbortSignal
|
|
}) => {
|
|
// Always include studio tools
|
|
let tools: ToolSet = getStudioTools({ projectRef, connectionString, authorization, aiOptInLevel })
|
|
|
|
// If self-hosted, only add fallback tools
|
|
if (!IS_PLATFORM) {
|
|
tools = {
|
|
...tools,
|
|
...getFallbackTools({
|
|
projectRef,
|
|
connectionString,
|
|
authorization,
|
|
includeSchemaMetadata: aiOptInLevel !== 'disabled',
|
|
}),
|
|
}
|
|
} else if (accessToken) {
|
|
// If platform, fetch MCP and other platform specific tools. The MCP tools
|
|
// are fetched from the remote MCP server over the network, so a failure
|
|
// there (outage, timeout, auth) should degrade gracefully to the remaining
|
|
// tools rather than break the entire assistant.
|
|
let mcpTools: ToolSet = {}
|
|
try {
|
|
mcpTools = await getMcpTools({
|
|
accessToken,
|
|
projectRef,
|
|
aiOptInLevel,
|
|
signal,
|
|
})
|
|
} catch (error) {
|
|
console.error('Failed to fetch MCP tools:', error)
|
|
}
|
|
|
|
tools = {
|
|
...tools,
|
|
...mcpTools,
|
|
...getSchemaTools({
|
|
projectRef,
|
|
connectionString,
|
|
}),
|
|
...getReportTools({ projectRef, authorization }),
|
|
...(isExplorerEnabled
|
|
? getNotebookTools({
|
|
projectRef,
|
|
connectionString,
|
|
authorization,
|
|
aiOptInLevel,
|
|
})
|
|
: {}),
|
|
...(baseUrl ? getIncidentTools({ baseUrl }) : {}),
|
|
}
|
|
}
|
|
|
|
// Filter all tools based on the (potentially modified) AI opt-in level
|
|
const toolsWithSupport = supportMode ? { ...tools, ...getSupportLifecycleTools() } : tools
|
|
const filteredTools: ToolSet = filterToolsByOptInLevel(toolsWithSupport, aiOptInLevel)
|
|
|
|
return filteredTools
|
|
}
|