L06 · New project · 4 min

Local and remote: your computer and GitHub

In one sentence

Your project has two twins: the local repo on your computer, where you and your agent work, and the remote repo on GitHub, a safe copy you can reach from anywhere.

Think of it like this

Your computer is the workshop; GitHub is the safe, shared warehouse. You build in the workshop and send finished pieces to the warehouse.

How it works

Unlike Dropbox, the twins don't sync themselves. Your agent sends checkpoints up with a DefinitionpushSending your commits from your computer up to GitHub.Open in the glossary → and brings changes down with a DefinitionpullBringing changes down from GitHub to your computer.Open in the glossary →.

The remote twin is your backup if your laptop dies, your time machine, and the place DefinitionVercelThe service that turns your code on GitHub into a live site, with a Preview for every change.Open in the glossary → watches: every push can become a DefinitionPreviewA private test link Vercel makes for each change, so you can try it before it goes live.Open in the glossary →.

A · Your computerThe workshopYou and your agent work here, in the local repo: a folder with a memory.
B · GitHubThe warehouseThe remote twin: a safe, shared copy with its full history.
C · VercelThe shop windowA private Preview for each change, and your live app once you approve it.
FIG. 1 · Local and remote are twins that don't sync themselves: your agent pushes checkpoints up and pulls changes down.

What it looks like in your project

After each task, your agent pushes. Open your repo on github.com and you'll see the same files and the same commits as on your computer.

Copy for your agent

Check whether my local repo and GitHub are in sync, and explain what you'd push or pull, in plain words.

Quick check · 1 question

You just made a commit. Is it on GitHub yet?

Go deeper

Next lessonBranches, pull requests and merging

Last reviewed Nov 8, 2026