foolish-bandit renames Mike to Gary, but only skin-deep

A fresh fork swaps every visible "Mike" for "Gary" - while the plumbing underneath still answers to its old name.

brandinginfrastructure

This is the founding move of foolish-bandit's fork: rename the product. Everywhere a user can see it, "Mike" becomes "Gary." The assistant now introduces itself as Gary in chat, the sidebar and page titles read Gary, and - a nice touch for litigators - tracked-changes edits exported to Word show "Gary" as the author in the Review pane.

What hasn't changed is the machinery behind the curtain. Database tables, storage conventions, and internal naming all still use Mike's original scheme. The team kept the change deliberately shallow to avoid breaking anything, which is sensible - but anyone planning to actually deploy this should know the rebrand is cosmetic. You'll hit a few spots where the old name is baked into infrastructure defaults and have to decide whether to live with it or override at setup.

So what If you're evaluating Gary as a white-label starting point, the public face is clean - just budget time for the back-end rename the team left for later.

View this fork on GitHub →

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

Commits in this thread

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

SHA Subject Author Date
dae6f594 Rebrand user-facing copy from Mike/MikeOSS to Gary/GaryOSS Claude 2026-05-07 ↗ GitHub
commit body
Updates user-visible branding (HTML titles, sidebar/logo text, AI
system prompts, DOCX tracked-changes author, signup links, placeholder
copy) and renames the frontend/backend npm packages to gary and
gary-backend. Default R2 bucket name in env example and storage.ts
fallbacks changes from "mike" to "gary". Internal type names
(MikeDocument, MikeIcon, mikeApi module, drag/drop MIME types,
localStorage key, change-id prefix) are intentionally left unchanged
to keep this PR small; they can be renamed in a follow-up.

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

⬇ Download capture-thread-324.md