Connect GitHub to your project
Push the agent-generated code out of the sandbox into a real GitHub repo. We use OAuth, so there's no token to copy or paste — you just sign in once and click Authorize.
Create a GitHub account (if you don't already have one)
Head to github.com/signup. Pick a username — it'll be the prefix for every repo URL — confirm your email, and pick the free plan. Free is enough; we don't need any paid features.
Verify your email
GitHub won't let you push code or accept OAuth invites until your primary email is verified. Check the inbox for the address you signed up with and click the confirmation link.
Open your project's top bar in Code.ae
In the workspace, look at the top-right toolbar. You'll see Push to GitHub if you're already connected, otherwise Connect GitHub.
Click 'Connect GitHub'
A new tab opens with GitHub's standard OAuth authorize page. It shows you exactly which permissions Code.ae is asking for — read + write to repos you choose, plus your email so we can author commits from your identity. Review and click Authorize.
Return to Code.ae and push
Switch back to the workspace tab. The button now reads Push to GitHub. Click it, choose a repo name, and the agent will create the repo, commit the workspace, and push. You'll see the live URL in a toast.
(Optional) Subsequent pushes
Every later push to the same project re-uses the same repo. You can override the commit message in the dialog. The repo URL is stored on the project so refreshes preserve it.
Connect GitHub again — the flow is idempotent. If you see commit email could not be matchedon a later Vercel deploy, that means GitHub doesn't have your email marked as verified yet; verify it on github.com/settings/emailsand retry.