WEBSITESfor Normal People2026

Part V: Keep These Handy (use them when you need them)A

Appendix A

Appendix A: The key vault, when you need it

4 min read, 2 cheat sheets, 3 things to tick

Wait, where do I paste the key? Here. Only here.

Skip this for a basic local build and Cloudflare preview. Come here when you add a CMS, Stripe, a Google service-account key or automatic deployments. Browser sign-in handles local Cloudflare access; it does not store every other service's secrets for you.

People adding more services often hit the same wall. The agent says "create a key, paste it here." You paste it into the chat. Next session, it's gone. You paste it again. Then you paste the wrong one. Then you've got keys scattered across chat history, sticky notes and a file called keys-FINAL-2.txt on your desktop.

The fix: one vault. The agent reads keys from it when it needs them and writes new ones into it when it creates them. You almost never touch it. Nothing sits in a chat, nothing sits in your code.

What to use

Bitwarden Secrets Manager. Free plan: unlimited secrets, 3 projects, 3 "machine accounts" (the login your agent uses). Built exactly for this.

Already pay for 1Password? That works too. See the end of this chapter.

Set it up (the only clicking in this chapter)

This part has to be you, because it's the account the agent logs in with. Five minutes.

  1. Go to bitwarden.com and create an account (or log in).
  2. Create an organization. Bitwarden needs one even if it's just you. Free.
  3. Switch to Secrets Manager with the product switcher (top left).
  4. Create a project called websites.
  5. Create a machine account called claude. Give it Can read, write access to the websites project.
    • Read and write, because the agent is going to create most of your keys itself and needs somewhere to put them.
  6. In the machine account → Access tokens → Create access token. Copy it.
Watch itBitwarden sign-up → organization → switch to Secrets Manager → project → machine account (read, write) → access token.

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

Put the master token in your computer's keychain

That access token unlocks the vault, so it's the one key that doesn't go in the vault. It goes in your computer's own keychain, where your passwords already live.

Mac: open Terminal, paste this, press Enter. It asks for the token: paste it and press Enter. Nothing shows while you paste. That's normal.

TerminalCheat sheet 011 lines
security add-generic-password -a "$USER" -s bitwarden-secrets-token -w
Watch itKeychain command in Terminal.

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

Windows: Start → Credential Manager → Windows Credentials → Add a generic credential. Internet or network address: bitwarden-secrets-token. User name: anything. Password: the token.

How the agent uses it

Bitwarden has a small command-line tool called bws. The agent installs it and wraps it in a helper called withkeys. When a command needs one of these service secrets, the agent runs it through withkeys, which pulls the keys out of the vault and hands them to that one command. They never get printed, never saved to a file in your project, never land in the chat.

PromptCheat sheet 0214 lines
Set up Bitwarden Secrets Manager for the extra services on my site. My
project is "websites". Its machine account has read/write access, and the
access token is in my system keychain as "bitwarden-secrets-token"
(macOS generic password or Windows Credential Manager generic credential).

Install the bws CLI. Make a helper called withkeys that loads only the
needed secrets into a child command with bws run. Never print values or
put them in chat, shell history, project files or commits. Also provide a
safe way to save newly created secrets without printing them.

Verify vault access without revealing values. Add the vault location,
helper usage and secret-handling rules to my Claude instructions, preserving
existing instructions. Keep Cloudflare's local browser login separate;
do not create a Cloudflare API token just to populate this vault.

1Password instead? Replace the vault paragraph with: My keys are in 1Password, vault "websites", one item per key, value in the password field. The 1Password CLI integration is enabled. Use op and op run instead of bws and bws run.

What ends up in the vault

Only add what your chosen features need. Appendix B covers optional tokens for automatic deployments.

SecretWho puts it thereUsed for
CLOUDFLARE_DEPLOY_TOKENYou, with the agent specifying the scopeOptional automatic deployments from GitHub
CLOUDFLARE_ACCOUNT_IDAgentTells Cloudflare which account
TURNSTILE_SECRET_KEYAgentSpam protection on your forms
PAYLOAD_SECRETAgentThe CMS (Path B)
STRIPE_SECRET_KEYYouPayments (Path C)
STRIPE_WEBHOOK_SECRETAgentConfirms payments actually happened (Path C)
GOOGLE_SERVICE_ACCOUNT_JSONAgentAnalytics and Search Console

If you'd rather use 1Password

1Password's command-line tool, op, does the same job and hooks into the desktop app, so the agent triggers a Touch ID or Windows Hello prompt when it needs a key. Some people love that. Some people find it annoying on the 40th deploy.

  1. Create a vault called websites.
  2. 1Password app → Settings → Developer → turn on Integrate with 1Password CLI.
  3. Use the 1Password replacement above in this appendix's prompt.

Checklist

Return to the chapter that sent you here. You do not need the next appendix unless you want automatic deployments.

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