From Agent Folder to Shippable Agent: Five Checkpoints
An Agent SDK agent is a folder of instructions, tools, skills, and channels. This walkthrough follows five checkpoints from local validation to gateway-gated tool calls and replayable evals.
Supabasehieu, kemal_y, gildas_garcia, wenboAnnouncement
Supabase now scopes Personal Access Tokens to specific resources and permissions, limiting what each token can do. Announced at Supabase Select on October 2 after becoming generally available on September 28, the feature lets you choose resources such as a single project, permissions such as read-only database access, and an expiration date up to one year. The token’s scope is fixed at creation, and its effective permissions are bounded by the user’s own role; losing access revokes the token’s ability until restored. A review screen shows the blast radius with a risk banner, and scoped tokens start with the prefix sbp_fc. Existing full-access tokens remain unaffected and carry a Legacy badge, while the Dashboard now creates scoped tokens by default, with nearly nine out of ten new tokens scoped.
Personal Access Tokens previously granted full account access. Supabase introduced scoping to limit tokens to specific projects and permissions, announced at Supabase Select on October 2 after becoming generally available on September 28.
Create a token in the Dashboard by selecting resources (e.g., a single project), permissions (e.g., database read), and an expiry date. The token gets the prefix sbp_fc and can be used with the Management API, MCP server, or CLI via bearer authentication. Existing tokens remain unchanged.
Scoped tokens are created in the Dashboard by selecting resources, permissions, and an expiry; the token’s scope is fixed at creation.
A token’s effective permissions are bounded by the user’s own role; losing access to a resource revokes the token’s access until restored.
Existing full-access tokens remain unaffected and carry a Legacy badge; the Dashboard now creates scoped tokens by default, with nearly 90% of new tokens scoped since launch.
Yes, the Dashboard still offers a 'Create legacy token' option for workflows that need full access, but all new tokens are scoped by default.
The token loses that access until your access is restored. The token's detail view marks any resource you can no longer reach.
Create the token in the Dashboard and pass it with `supabase login --token <token>`. For CI, set the SUPABASE_ACCESS_TOKEN environment variable; it overrides locally saved tokens.
Summaries are generated from the original by a language model. Check the original before relying on it.
See the idea
An Agent SDK agent is a folder of instructions, tools, skills, and channels. This walkthrough follows five checkpoints from local validation to gateway-gated tool calls and replayable evals.
Keep reading
The Good Stuff
Paid picks we use ourselves. Links carry a referral code — a subscription through one earns us a commission at no extra cost to you.
One useful email. Unsubscribe anytime.