Why GitHub Integration Matters in a Cloud IDE
The promise of a cloud IDE is that you rarely have to leave your browser to do development work. For that promise to hold, the IDE needs to handle not just code editing and deployment, but also the version control workflows that underpin professional software development: branching, committing, diffing, and merging.
CloudCode's GitHub integration covers the everyday parts of that lifecycle — push, pull, branches, pull requests, CI and issues — without opening a separate browser tab.
Connecting Your Repository
To connect GitHub, open the GitHub tab in the right panel (next to Preview and Files) and click Connect GitHub. CloudCode asks you to approve an OAuth request on GitHub. It requests the 'repo' and 'read:user' scopes; GitHub's 'repo' scope grants read/write access to the repositories your account can access, and GitHub doesn't let OAuth apps narrow it to selected repos. Your token is stored server-side, and you can disconnect at any time from the same tab.
Once connected, search your repositories in the Repos tab and click one to link it to your project. You can also import a repo's files into the current project, start a new project from a repo, or create a new repository (private by default) and link it in one step.
Syncing is manual and in your control. The Push tab commits your project files to the branch you choose as a single commit — with an AI-written commit message if you like — and adds a '.gitignore' and '.env.example' if your project doesn't have them. The Pull tab fetches a branch and flags every file that differs from your copy, letting you keep the local or the remote version of each one. Nothing is pushed automatically, so edits made by you or the Claude Code agent stay in CloudCode until you decide to push.
You can also stay in the terminal: 'git status', 'git add', 'git commit -m', 'git push' and 'git pull' work against the linked repository through the GitHub API.
Creating Branches
In CloudCode, branches go hand in hand with workspaces. Click New workspace in the left sidebar, give it a name following your team's conventions — 'feature/user-authentication', 'fix/login-race-condition', 'chore/upgrade-dependencies' — and tick Create GitHub branch to create the matching branch from main. Each workspace keeps its own copy of your files inside CloudCode, and you can compare two workspaces or merge one into another.
Understanding Diffs
CloudCode shows you diffs in several places: the Pull tab flags files that differ between your copy and a branch, 'git diff' in the terminal compares your local files with the remote, Compare with… shows a diff between two workspaces, and every pull request shows its changed files and diffs. Lines added are highlighted in green; lines removed are highlighted in red.
Reading diffs is the most important quality gate in your development workflow. The agent is very capable, but it is not infallible. Reading the diff catches cases where it changed something you did not intend — a comment it removed, a subtle logic change in a function that was adjacent to the one you asked it to modify. And if a change does slip through, every file keeps a version history you can restore from.
Opening Pull Requests
When your branch is ready for review, open the PRs tab and click New PR. Choose the head and base branches; CloudCode shows the commits between them, and AI Title can write a title from them. Add a description, optionally mark the PR as a draft, and create it.
CloudCode creates the pull request on GitHub via the API. From this point, the PR is a standard GitHub pull request — it can receive comments from teammates, trigger your CI, and be reviewed using GitHub's native code review interface. Inside CloudCode you can list open, closed or all pull requests and open any of them to see its branch, author, changed files and diffs.
Reviewing and Merging
For each pull request, CloudCode shows you the diff file by file, with a link out to GitHub. Line comments, review requests and approvals happen on GitHub itself.
When a PR is ready to merge, you can merge it directly from CloudCode using any of the three GitHub merge strategies: merge commit, squash merge, or rebase merge. Merging doesn't change the files in your CloudCode project, so use the Pull tab afterwards to bring the merged result in.
Handling Merge Conflicts
Conflicts show up in two places in CloudCode. When you pull a branch, the Pull tab lists every file that differs from your copy and lets you choose the local or the remote version of each. When you merge one workspace into another, the merge dialog lists new, modified and unchanged files, and you resolve each conflict by keeping the source, keeping the target, or editing the file manually.
For tricky files, you can also ask the agent to help: give it both versions, explain what each change was meant to do, and have it write a merged version. Review the result in the editor before you push — it's your call, not the agent's.
Branch Protection and Repository Settings
Branch protection rules and repository settings stay on GitHub, where they're enforced. What CloudCode adds is visibility: the CI tab lists your GitHub Actions runs and their jobs, and for a failed job, AI Fix reads the job log and suggests a fix. The preview toolbar shows a check-status badge for the repo's open pull request, and the Issues tab lists your repository's issues and lets you open new ones — so you can keep an eye on your repository's health without leaving the IDE.
