foolish-bandit is putting gary on the open web

Most Mike forks live as code on GitHub. This one is wiring itself up to run as a hosted app anyone can click on.

infrastructure

The team behind the gary fork has spent a handful of commits on the unglamorous-but-telling work of getting the frontend running on Cloudflare Workers - Cloudflare's serverless platform that runs web apps on servers spread around the world, close to whoever's loading the page. That involves pinning the right framework version, dropping in the configuration file Cloudflare expects, and adding clean build and deploy commands so the platform can pick the project up without ceremony.

None of this changes what gary does. What it changes is who can see it. A hosted demo means a managing partner or legal-ops lead can be sent a link and form their own opinion in thirty seconds, rather than asking an engineer to spin it up. Forks that take this step are the ones to watch - they're the ones whose owners are thinking about an audience beyond themselves.

So what If you track Mike forks to spot which ones might harden into real products, foolish-bandit just moved from experiment to something demo-able.

View this fork on GitHub →

Spotted something wrong? Or know the PR text has fresher detail than the writeup above?

Commits in this thread

6 commits from foolish-bandit/gary, oldest first. Source extracted verbatim from the harvested git log.

SHA	Subject	Author	Date
`97471172`	Merge pull request #2 from foolish-bandit/claude/fix-next-cloudflare-compat	Zack Brenner	2026-05-07	↗ GitHub
Upgrade Next.js from 16.0.3 to 16.0.11
`8c8dbba6`	Merge pull request #3 from foolish-bandit/claude/remove-frontend-bun-lockfile	Zack Brenner	2026-05-07	↗ GitHub
Remove frontend/bun.lock so Cloudflare uses npm
`b6dc0e42`	Bump next to 16.0.11 for Cloudflare deploy compatibility	Claude	2026-05-07	↗ GitHub
commit body @opennextjs/cloudflare requires next ~16.0.11 or ^16.1.5; the pin at 16.0.3 broke install on the Cloudflare deploy. Bumping to 16.0.11 satisfies the peer range with the smallest possible version change. React, React DOM, @opennextjs/cloudflare, and other deps are unchanged - the lockfile churn beyond the next version bump is just npm renormalizing dev/devOptional flags and deduping transitive deps. https://claude.ai/code/session_01McEfVnpbGdMs5TgeTM7P3R
`f01df75f`	Add minimal wrangler.jsonc for Cloudflare deploy	Claude	2026-05-07	↗ GitHub
commit body After bumping next to satisfy the peer range, the next failure on the Cloudflare deploy was that opennextjs-cloudflare build couldn't find a wrangler config. Adding the canonical default the @opennextjs/cloudflare CLI emits: project name "gary", nodejs_compat + global_fetch_strictly_public flags, ASSETS binding, the OpenNext self-reference service binding (required for the OpenNext caching layer per opennext.js.org/cloudflare/caching), and the IMAGES binding for image optimization. https://claude.ai/code/session_01McEfVnpbGdMs5TgeTM7P3R
`befcd221`	Add cf:* scripts and Workers deploy docs	Claude	2026-05-07	↗ GitHub
commit body The frontend deploys to Cloudflare Workers via @opennextjs/cloudflare, not Cloudflare Pages. Add explicit cf:build, cf:deploy, cf:preview scripts so the Cloudflare project's build/deploy commands map directly to npm scripts (the existing combined preview/deploy/upload scripts are kept for backward compatibility). Document the Workers deploy flow in the README so contributors don't reach for the Pages path. wrangler.jsonc already satisfies the OpenNext-on-Workers requirements (main: .open-next/worker.js, assets.directory: .open-next/assets, assets.binding: ASSETS, compatibility_flags includes nodejs_compat). https://claude.ai/code/session_01McEfVnpbGdMs5TgeTM7P3R
`9de83b4a`	Remove frontend/bun.lock so Cloudflare uses npm	Claude	2026-05-07	↗ GitHub
commit body Cloudflare's framework auto-detection picks Bun whenever a Bun lockfile is present, even though the project is npm-managed and ships with package-lock.json. Removing bun.lock makes the build agent fall back to npm. package-lock.json is unchanged (npm install reports "up to date"). https://claude.ai/code/session_01McEfVnpbGdMs5TgeTM7P3R

Capture this thread into my fork

Download a single Markdown prompt that tells Claude how to port every commit above into your working tree — adapting paths and structure to match your repo. Run it via claude -p < capture-thread-158.md from inside the repo you want the changes in.

⬇ Download capture-thread-158.md