Existing projects
Open a codebase you already have
Orepo can import a GitHub repository and edit those files in place. Public repos work without login to GitHub. Private ones work after you Connect GitHub in Settings. This is for an app that already exists, not only for a new page. A club product such as ENERGECiA, with members and subscriptions already in Supabase, is one example.
Import
In the project list, choose Open existing. Paste a GitHub link or owner/repo. Orepo downloads the source and keeps the file tree. Lockfiles, dependencies, and secret env files are left out. A private repository imports after you Connect GitHub in Settings → Models.
An Expo app is recognized from app.json or the Expo dependency. Prompts then change the screens that are already there. They do not replace the app with a new index.html. The same rule applies to an imported web project: its files stay. The default preview still shows index.html when the project already has one. Press Run to start the Expo web bundler or the project's own server in an E2B sandbox when an E2B key is available (yours in Settings → Agents, or the server key).
Open the sample loads a small Expo app so you can see the flow. Its screens call Supabase tables named for a club. Your own repo keeps whatever tables and screens it already has.
Supabase
If the project uses Supabase, paste that project's URL (https://….supabase.co) and its anon key. Orepo asks Supabase which tables that key can see, then lists those names. Choosing a table reads a few rows at that moment. The rows are shown and then dropped. They are not copied into the Orepo project, and Orepo does not create a second database.
The service role key is refused. Only the anon key is kept, in the project env file the app already expects (EXPO_PUBLIC_SUPABASE_URL and EXPO_PUBLIC_SUPABASE_ANON_KEY). Row access still follows that project's own row security.