Workshop 2 of 2 · Mac Only

Made by Chris Downs · chris@datadowns.com

Put your agent on the internet. Get a real URL that anyone can visit — no technical background needed.

Workshop 1 Build it on your computer
Workshop 2 Put it on the internet

You have a working agent on your laptop. In Workshop 1, you built something with Claude Code that runs on your machine. Now we'll put it online so that anyone with the link can use it.

What you'll set up today

Two new things, both free:

  1. GitHub — saves your code online (like Google Drive, but for code)
  2. Cloudflare Pages — gives your agent a real URL on the internet that anyone can visit

Two free accounts. Sign up for both before starting. They're free and take a couple of minutes each.

A

GitHub Account

github.com ↗

Think of GitHub as Google Drive for code. It stores your project online so it's safe and accessible from anywhere. It's also how Cloudflare will know what to put on the internet.

  1. Go to github.com and click Sign up
  2. Pick a username, enter your email, set a password
  3. That's it — you have an account
B

Cloudflare Account

cloudflare.com ↗

Cloudflare is what actually puts your app on the internet. It takes your code from GitHub, builds it, and gives you a URL that anyone in the world can visit.

  1. Go to cloudflare.com and click Sign up
  2. Enter your email and set a password
  3. You're done — the free plan is all you need
Checklist
  • GitHub account created
  • Cloudflare account created

Step by step. Follow these in order. Each step builds on the last.

1

Send your code to GitHub

You need to get your code off your laptop and onto GitHub. This uses a tool called git — it's like version history in Google Docs, but for code. It's already on your Mac from Workshop 1.

First, create a repository on GitHub:

  1. Go to github.com and sign in
  2. Click the + in the top right, then New repository
  3. Name it the same thing as your project folder (e.g. my-first-agent)
  4. Leave everything else as default and click Create repository
  5. Stay on the page that appears — you'll need the URL it shows you

Now open Terminal and go to your project folder:

Set up git in your project:
git init
Add all your files (like putting items into a box):
git add .
Save a snapshot (like sealing the box with a label):
git commit -m "first version"
Connect to GitHub — copy the URL from the GitHub page you're looking at and paste it here:
git remote add origin https://github.com/YOUR-USERNAME/YOUR-PROJECT.git
Send your code to GitHub (like shipping the box):
git push -u origin main
The URL in the command above

Don't type YOUR-USERNAME and YOUR-PROJECT literally. On the GitHub page you just created, there's a URL that looks like https://github.com/janedoe/my-first-agent.git — copy that and use it instead.

What just happened

Your code is now saved online at GitHub. If your laptop breaks tomorrow, your code is safe. Go to github.com and click on your repository to see it.

Getting an error about "main" vs "master"?

Some setups use "master" instead of "main" as the default name. If you see an error about this, run:

git branch -M main

Then try git push -u origin main again.

2

Connect Cloudflare to GitHub

Now tell Cloudflare to take your code from GitHub and turn it into a live website.

  1. Go to your Cloudflare dashboard
  2. In the left menu, click Workers & Pages
  3. Click Create, then choose Pages, then Connect to Git
  4. It will ask you to connect your GitHub account — follow the prompts
  5. Select the repository you just created
  6. For build settings — don't guess, ask Claude Code:
I'm putting this project on Cloudflare Pages. What framework preset, build command, and output directory should I use?
Paste this into Claude Code. It knows what it built and will give you the exact settings.

Enter whatever Claude Code tells you, then click Save and Deploy.

If the build fails

Copy the error message from Cloudflare, paste it into Claude Code, and say "I got this error when deploying to Cloudflare Pages. Can you help?" It will know what to fix.

3

Add your API key to Cloudflare

Your agent needs your Anthropic API key to talk to Claude. But you should never put API keys directly in your code — especially code on GitHub where anyone could see it.

Instead, you store it as a secret in Cloudflare. Think of it like a safe deposit box — your agent can access it, but nobody else can see it.

  1. In your Cloudflare Pages project, go to Settings
  2. Find Environment Variables
  3. Click Add variable
  4. For the name, use what Claude Code expects (usually ANTHROPIC_API_KEY — ask Claude Code if you're not sure)
  5. Paste your Anthropic API key as the value
  6. Save, then re-deploy (or push a new change to trigger it)
Check your code too

If Claude Code put your API key directly in the code, ask it: "Can you move my API key to an environment variable so it's not in the code?" It will know what to do.

4

Your agent is live

Once Cloudflare finishes building, it gives you a URL like:

your-project.pages.dev

That's a real URL on the internet. Anyone with that link can use your agent. Send it to someone — right now.

Change it, push it, it's live. Every time you update your agent, Cloudflare picks up the changes automatically.

1
Make changes to your agent locally (with Claude Code)
2
Run git add . to stage the changes
3
Run git commit -m "what changed" to save a snapshot
4
Run git push to send it to GitHub
5
Cloudflare updates automatically — your live site has the new version within minutes
The three commands you'll run every time:
git add . git commit -m "what changed" git push
The pattern to remember

Change → add → commit → push → live.

That's it. It becomes muscle memory fast.

Why do developers use git?

Undo mistakes. Every snapshot you save is permanent. If you break something, you can go back to any previous version. It's like having infinite undo.

Work with other people. Git lets multiple people work on the same code without overwriting each other's work.

Try things safely. You can create a "branch" — like a parallel universe for your code — to experiment without risk.

You don't need to understand all of this right now. Add, commit, push is all you need.

Stuck on something? It's normal to hit a wall. Get in touch.

Stuck? Need help?

If something doesn't work — a build fails, git gives you a confusing error, or you just don't know what to do next — get in touch. I'll respond.

chris@datadowns.com
Workshop 1 Build it on your computer
Workshop 2 Put it on the internet