AI webmaster (Claude Code + GitHub Actions + preview deploys, texts and email in)
Routine copy, program-fee, and page updates on an Angular 18 teacher-recruitment and TEFL platform required waiting on developer availability for every small edit.
Wired an AI webmaster ("Sunny") combining an agent workspace running Claude Code CLI, a Twilio SMS bridge, AgentMail, GitHub Actions (`webmaster-*.yml`), an automated reviewer bot, and Netlify deploy previews so the director can text or email a change request and inspect the result on a preview link.
Operating live since 2026-09-23 with 22 bot-authored pull requests (PRs #44–#61 in the approval log), each verified on a Netlify preview before merge.
Included in a Claude Max subscription ($100–$200/month) or ~$2–$8 in API tokens per request, plus Twilio SMS (~$1.15/month for the local number + $0.0079/text), GitHub Actions minutes, and Netlify preview hosting ($0–$19/month) (as of 2026-10-22).
Inbound texts (via Twilio SMS bridge) and emails (via AgentMail) trigger a GitHub Actions workflow (`webmaster-*.yml`) that runs Claude Code CLI against the repo, runs the build and a reviewer-bot check, opens a pull request, and sends the Netlify preview URL back to the owner before anything merges.
Our underlying agent host shifted multiple times during early runs (starting on an xAI Grok Bot workspace across 24 sessions before standardizing the execution lane on `claude -p` and GitHub Actions), and unattended edits needed an independent reviewer bot plus a strict preview-approval gate so an unreviewed prompt could never auto-merge to production.
Compared against giving a non-technical owner direct CMS admin access (where accidental layout edits break mobile pages or forms) and traditional developer hourly retainers (slow turnaround for 5-minute copy tweaks). We picked a PR-based AI webmaster because every change gets a git diff, a build check, and a preview link.
