The Repo

The Repo is every file of the site, as folders: a private GitHub repository made for the project. Flexi commits to it, every commit shows in the chat as a card, and the code is yours to take anywhere.

Opening a file

Any file opens. An HTML file opens with Page · Source, and Diff when the last commit changed it, at Full, Laptop, Tablet or Phone width. A picture or a PDF opens as it does in a chat's Files. The paperclip attaches the file to your next message in the chat, and @ in a message box attaches a repo file the same way: Flexi reads it for that message.

What is in it

• The site: everything outside .flexos/. A new project starts as one holding page.
• .flexos/: the Library, each chat's folder (its files), and the log: one file a month of every message you sent in every chat, with anything that looked like a key written as redacted. Flexi's replies are not in it. The folder is never served by the site.
• app/: a phone app, when the project has one. Off the website.
• flexapp/: the project's agents and their pages, one deployment for all of them. A commit there builds the agents, not the site.

One branch

FlexOS uses one branch, the one that deploys. Every commit goes to it: Flexi's changes, Library filings, what you attach, the docs, the log. A commit that changes the site starts a build; one that only touches .flexos/ or flexapp/ does not. Flexi cannot open a pull request or commit elsewhere, and he cannot push from his sandbox: every commit goes through the one door that shows it in the chat.

Keys are not in it

Keys live in the Vault, never in the repo, and a .env file is never committed: an import diverts it to the Vault. Keys and the Vault has the rest.

Where next

• Code: the repository's row in Settings, and Import a zip.
• Preview and going live: what a commit builds.