Why connect, not migrate
You don't move your data into Vibe — Vibe reads and writes against your existing Tadabase app via the Domain API. Tables, workflows, PDF templates, RLS policies — all stay where they are. Vibe just adds a new UI.
Picking the right app
When you create a Vibe project, the app picker lists every Tadabase app you can access. The picker shows table count and last activity so you can confirm you're binding to the right one.
How schema sync works
On project creation, Vibe pulls the full schema of your bound app into tada/schema.json. The agent reads this file to know your tables, fields, and connections — so when you say “the customers table,” it knows which slug to call.
Logging users in
Tadabase users authenticate against your Tadabase app, and the resulting session token is what Vibe uses to call the Domain API on their behalf. Calls are subject to your existing RLS rules — there is no second permissions system to keep in sync.