Every service the project uses, its keys, and Set it up with Flexi.
Connections is every service the project uses: Stripe, Supabase, Resend, anything. One row each, A–Z, and each row says where it stands.
The word is worked out from the Vault's key names each time it is read, so a key added in Settings › Vault turns the row by itself. Keys filed under a service in the Vault, or an imported .env with a known key name (STRIPE_SECRET_KEY), make a row without anyone adding it. Enter in the list's field adds any service by name.
Two tabs. Keys: each by name, in the Vault or missing; a tap on a missing one opens Settings › Vault with that name in its field. Doc: the service's integration doc in the Library, or what will fill it.
The row's one button opens the service's space: one chat per service per project, with the same Doc, Tasks, Files and Context as any chat, listed under Connections rather than Chats. Its first message is sent for you the first time: Set up Stripe for this project.
In the space Flexi asks once what the service is for here, puts one card up for the missing keys, and, once every required key is in, writes the integration doc. Coming back later is the same space: rotate a key, add a webhook and its signing secret, move from test to live, rewrite the doc.
For a service you have no account with, Sign me up on the row opens the space asking for the sign-up walk. Flexi takes you through it one step a message, in your own browser: the project's own email (your-name@inbox.flexos.me, so the verification mail lands in the Inbox for you to open), a password of your own, never Google or GitHub sign-in. A phone number, a card or an identity check is yours by hand. Once you are in, he offers once to keep the login in the Vault.
For a service whose recipe FlexOS has verified, the sign-up robot can make the account: after your yes by name (Yes, sign up for Neon), FlexOS's own browser signs up as the project's address, follows the verification mail out of the project's inbox, makes a key named FlexOS and pastes each key into the Vault. A card in the chat shows the browser live. A captcha, a text code, a card or an identity check turns it to Your turn: the view becomes clickable, you do that part, and Done, carry on resumes. Stop ends it. The robot accepts the service's terms in the project's name, so Flexi says so, with the terms link, before asking for the yes.