Draft: these steps await verification against the current release of AgentKit.
What you need
- A Supabase account, or the willingness to create one at sign-in.
- For an existing project: knowing that once AgentKit turns on SSL enforcement, any client of that project that connects without encryption stops connecting.
Steps in the app
1
Open the Database settings
In the onboarding this is the Database step. Later, open Settings (⌘,) and go to Database. Choose the Supabase tab; it is the first and the default.
2
Sign in to Supabase
Start the sign-in. Supabase’s own sign-in opens in your browser; sign in and allow AgentKit. You copy no credentials.
3
Choose or create a project
AgentKit lists your projects. Choose one, or create a new one.For an existing project, AgentKit says first that clients without encryption will stop connecting. Confirm only if nothing of yours relies on unencrypted connections.
4
Let AgentKit set it up
AgentKit creates a database role and schema of its own in the project and turns on its SSL enforcement. The form then shows the connection and a connection indicator.
5
Set the pool size, if needed
While the database is a Supabase session pooler, the page holds its pool size, 15 by default. Set it to your pooler’s size, since the pooler does not report it; the sidebar’s Database row measures against it.
Steps by command line
The form reads and writes the machine’s database setting through the capabilities manager. To see what is set, or to check it:capabilities help gives the full reference for the database setting.
Check it worked
- The Database page shows the connection indicator as connected.
- The sidebar’s Database row is grey and shows used of available connections, such as
4/15. Hover it for the host and mode, the round trip, and when it was last read. - Agents lists your agents; a new Mac’s onboarding goes on to First Agent.