Start here
Your first project
Three ways in, and what happens in the first minute.
There are a few ways into a project, and the new-project page lays them all out: start with a problem or an idea, or bring what you have — your website, a zip of your code, a FlutterFlow app, or nothing yet. Which one you pick decides what Flexi reads first; everything after that is the same project.
Start with your website
Paste the address of the site you have, on the home page, or pick Import my website on the new-project page and type it there: Flexi reads it the moment the project opens and tells you what he found, the business, the look, the words and the pictures. From the home page FlexOS reads it before you sign in and shows a picture of the site as it is beside a first sketch of what Flexi would build. When you say yes, the project starts with that read as the first message of its first chat, so Flexi already knows your business, your pages and what is missing.
Start with an idea
Say what slows your business down, in a sentence. The new-project page offers four cards: what's slowing your business down, what you hate most about your job, what keeps you from getting home on time for dinner, or simply I have an idea. A tap starts the sentence for you; you finish it, and it becomes the first message of the first chat. A complaint is a fine first message: Flexi's job is to turn it into the site, the pages and the agents that fix it.
Start with your code
Bring a zip of what you already have: a Lovable export, a FlutterFlow export, any website. Tap Import a zip and pick the file: it is read on the spot, and the page shows what it found before anything is uploaded. Your files go into the repo in one commit, as they are, with installed packages, git history and build output left out. Keys found in a .env go into the Vault, never the repo. The folder with the website in it becomes the one that gets built, and when the project opens Flexi has the first word: what he made of your code.
A zip with no website in it puts nothing online. A FlutterFlow export lands in the repo's
app/folder beside the site, off the website, and ships from Settings › Deployment › Mobile app.
What happens in the first minute
- A project is one GitHub repo, and it is yours. A new project starts as one holding page, live at its own address,
your-name.flexos.site. - Flexi answers in the first chat. Say what you are making and he plans it with you, writes the Notes and Tasks beside the chat, changes the site's code and builds it. Preview shows the site now and every build.
- The tour opens once, the first time you open a project, after Flexi's first reply: six short stops through the workspace. It is there again from Help on the rail whenever you want it, and the Chats home offers it until you have seen it.
Where next
- The workspace: what each place on the rail is for.
- Chats: how a chat works, and what to put in it.
- Keys and the Vault: before you paste an API key anywhere.
Still stuck? Ask Flexi in your project, or ask a flexpert.