foolish-bandit points Gary at Cloudflare's edge

A modest-looking Next.js bump is really a deploy-target decision in disguise.

infrastructure

On the surface, foolish-bandit's change to the Gary fork reads as a routine version bump. Underneath, it's a hosting choice. The version bump was the prerequisite; the real move is getting Gary running on Cloudflare Workers - Cloudflare's edge platform that runs code close to users rather than from a central server.

Alongside the upgrade, foolish-bandit added a small worker configuration file, a set of build-and-ship scripts, and contributor docs. Nothing flashy, but together they answer the question every fork eventually has to answer: where does this thing actually run? Gary's repo-level answer is now Cloudflare's edge, not the Vercel default that usually ships with Next.js apps.

So what Anyone evaluating Gary as a starting point for their own legal-AI build should note the hosting opinion is now baked in at the repo level.

View this fork on GitHub →

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

Commits in this thread

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

SHA	Subject	Author	Date
`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

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-277.md from inside the repo you want the changes in.

⬇ Download capture-thread-277.md