Follow these steps exactly once. After the initial setup, Push44 remembers your token in your browser's localStorage, so you won't need to repeat this for future exports (unless you clear browser data or the token expires).
📖 Introduction
Connecting GitHub is the first step to using Push44 with any AI platform. This tutorial walks through creating a Personal Access Token and pairing it with Push44 in under three minutes.
The Problem with Walled Gardens
First-time users often aren't sure which GitHub token type to create, which scopes to select, or where to paste it in Push44 — leading to confusing permission errors on the first export attempt.
The Push44 Solution
Follow these steps exactly once. After the initial setup, Push44 remembers your token in your browser's localStorage, so you won't need to repeat this for future exports (unless you clear browser data or the token expires).
Step-by-Step Walkthrough
5 stepsOpen GitHub token settings
Sign in to GitHub, then go to Settings → Developer settings → Personal access tokens → Tokens (classic) → Generate new token.
Name and scope your token
Give it a descriptive name like 'push44-export'. Set an expiration (90 days is a good default). Check the 'repo' scope box — this grants read/write access to your repositories.
Generate and copy the token
Click 'Generate token' at the bottom of the page. GitHub shows the token once — copy it immediately with the copy icon.
Paste it into Push44
Open push44.vercel.app, go through onboarding or settings, and paste the token into the 'GitHub Personal Access Token' field.
Verify the connection
Push44 makes a test call to the GitHub API to confirm the token works and shows your GitHub username once connected successfully.
Pro Recommendations
Set a calendar reminder before your token's expiration date so exports don't suddenly break.
You can create a Push44-specific token and revoke it anytime from GitHub without affecting any other apps.
Common Pitfalls to Avoid
Closing the token page before copying it — GitHub will not show the value again.
Pasting a token with extra whitespace — always paste directly without trailing spaces.
Frequently Asked Questions
Is a Personal Access Token safe to use with Push44?
Yes. Push44 stores it only in your browser's localStorage and uses it exclusively to call the GitHub API directly from your browser.
Can I revoke the token later?
Yes, at any time from GitHub's token settings page. Revoking it immediately stops Push44 (or any other app using it) from accessing your GitHub account.
Export and push your code in seconds.
Connect your platform, preview the visual diff, and create atomic commits on GitHub with zero server data retention.
Related Guides
View all →
export
beginner
How to Export Code from Base44
Step-by-step guide to exporting your full Base44 source code to GitHub using Push44. Free, no subscription, works with any Base44 project in under 2 minutes.
Fixing GitHub Token Permission Errors
Understand and fix GitHub Personal Access Token permission errors when pushing AI-generated code with Push44. Correct scopes explained.
GitHub Version Control for AI-Generated Apps
Add Git version control to any AI-built app. Track every change, collaborate with developers, and own your history. Works with Base44, Rocket.new, Floot, Zite.