WEBSITESfor Normal People2026

Part I: Setup (accounts, then the agent)03

Chapter 03

Step 2: Set up the agent (and let it set up everything else)

4 min read, 1 cheat sheet, 3 things to tick

Did you just click YOLO mode? Good.

You have the accounts. Now set up Claude Code to build locally. When the site is ready to share, sign in to Cloudflare in your browser and put it on a preview address. No domain and no copied Cloudflare token required.

The settings that matter

Open the Claude desktop app → Code tab.

Model: Opus 5.5. Not Sonnet, not Haiku. Opus is the one that designs well, and design is the whole point. Pick it from the model menu.

Effort: High for setup and the first build. Medium for small changes later. Higher effort means the agent thinks longer before it acts, which means fewer "that's not what I meant" rounds. It's slower. It's worth it.

Permission mode: Bypass permissions. Yes, the YOLO one.

By default the agent asks before every command. "Can I install this? Can I run this? Can I create this file?" On a site build that's a few hundred clicks, and you'll click yes to every one because you don't know what half of them do. That isn't safety, it's friction.

Turn it on: profile menu (bottom left) → Settings → Claude Code → enable Allow bypass permissions mode. Then choose Bypass permissions from the mode menu when you start a session.

Work in one folder. Make one called Websites in your Documents and open every session there.

Watch itCode tab → pick folder → model → effort → settings toggle → permission mode.

Personal details are covered or swapped for examples. Press play, it's silent and loops.

The setup prompt

Paste this into a new session in your Websites folder.

PromptCheat sheet 0137 lines
Set this computer up so Claude Code can build websites for me with
Cloudflare's cf CLI. Start with a local preview. No domain, API token,
secrets vault or automatic deployment from GitHub before my first build.

1. Check for Node LTS (at least 22.18), git and the GitHub CLI. Install what
   is missing. Install Cloudflare's CLI with npm install -g cf. Check its
   version and current docs: https://developers.cloudflare.com/cf/
2. For new sites use cf with cloudflare.config.ts. Start with a supported
   plain Vite/static site, using React only where it helps the interactions.
   Run cf init in the new site folder, review its configuration and pin
   the tested cf version in that project. Ignore .cloudflare build output.
3. Build and preview locally before signing in. When I want to save the
   code, use GitHub's browser sign-in. When I want to share a Cloudflare
   preview, start cf auth login. Tell me which account and permissions to
   review, then wait for my approval. Check cf auth whoami afterwards.
   Never print or copy login credentials.
4. Add these rules to ~/.claude/CLAUDE.md, preserving existing instructions:
   - Use cf for new Cloudflare projects and account tasks. Find unfamiliar
     commands with cf cli search, inspect their help/schema, then act.
     Keep search queries generic; leave out account names and private data.
   - For cf projects, run type checks and tests separately from cf build.
     Prove the build with cf deploy --dry-run before an actual deployment.
     For an approved framework deployment exception, keep its recorded
     build and validation commands through launch and CI.
   - Share a workers.dev staging address only when I ask. It is public;
     keep it noindex and keep private data out of it.
   - Do not buy a domain or change existing domain/email records during
     setup. Those are pre-launch tasks. Production waits for my approval.
   - Only add a vault when a feature needs service secrets. Never put
     secrets in chat, committed files or browser code.
   - Ask before adding a paid service. Tell me the actual plan and cost.
   - Existing Wrangler projects are a separate case: do not run cf's
     project commands against them without a reviewed migration. If a
     framework is unsupported, explain the specific limitation first.

Report what is ready for a local build and which sign-ins can wait until
I share the preview. Do not create remote resources in this setup step.

Why cf is the path now

Cloudflare's new cf CLI gives the agent a searchable way to work with its services. It can find commands, inspect what they need, and run them. Less key-hunting, more building. Claude Code is still the agent and Opus is still the designer. Cloudflare's launch announcement.

The first preview runs on your computer. To share it, approve cf auth login in your browser and let the agent deploy. No manually copied Cloudflare token or Bitwarden machine account is needed for that local workflow. CI and other services have separate credential needs, covered in the appendices. Cloudflare's first-project walkthrough.

Beta note, checked 4 October 2026: cf is in open beta. Pin the version the agent tests, review the login permissions, and remember that a browser login still grants real access. Credentials are stored by the CLI; this does not make it a password manager. Installation and sign-in, agent setup.

Existing site or unsupported framework?

For a new site, follow the cf path above. If you already have wrangler.jsonc or wrangler.toml, do not paste cf dev, cf build or cf deploy into it and hope. Have the agent review cf migrate --dry-run and explain the changes first. Keep that existing project's working commands until its migration is checked. Cloudflare's migration guidance.

Framework detection is not proof that a build works. Start with the supported plain Vite/static route here; Astro 6 and later is unsupported in the current beta. The CMS chapter calls out its own framework check. Wrangler is a troubleshooting option for a specific unsupported task, not the starting point for a new site. Supported project behaviour.

Why the instructions file matters

Checklist

Next: give Opus something worth building. Path A, building the website with Claude Code, starts with the brief.

On a phone, swipe left and right to turn pages.