$ the-wire · showcase
Self-hosted Assistant tools move to the contract registry
By RepoJournal · Filed · About Supabase · Composed from the cited sources · methodology
The Studio refactor deletes four self-hosted fallback tools in favor of registry contracts, while the eval snapshot refreshes with no user-facing change.
refactor(studio): move self-hosted Assistant tools to contracts supabase/supabase
The self-hosted Assistant now draws every callable tool from the registry, with the allowlist derived from it, and the fallback tools getSchemaTables, getRlsKnowledge, getFunctions and getEdgeFunctionKnowledge are deleted. Self-hosted deployments instead get the shared tools plus a local list_tables contract that takes the same input as the MCP tool and builds its output from pg-meta.
refactor(studio): move self-hosted Assistant tools to contracts (#52468) supabase/supabase
The same refactor, landed as a commit stacked on supabase/supabase#52422, so tool prompts and schemas now live in one place rather than diverging between hosted and self-hosted paths. Anyone running self-hosted Studio who relied on the removed fallback tools should expect the contract-backed list_tables path instead.
chore: refresh eval results supabase/evals
The automated releaser refreshed apps/web/src/data/eval-results.json from the latest eval run, the routine snapshot update that keeps the published numbers current.
chore: refresh eval results (#473) supabase/evals
by supabase-evals-releaser[bot]
The commit behind that snapshot, coordinated with mattrossman, carries the same data-only change into the tree.