easterbrooka relaunches Mike as Michelle

A fork operator is rebranding the open-source legal-AI codebase under a new product name and quietly wiring up the plumbing for a real launch.

brandinginfrastructure

Across the user-facing surface - browser title, sidebar, workflow badges, modal prompts, the error page, the account screen - every visible mention of "Mike" has been swapped for "Michelle." The icon and the underlying code names are left alone, so this is purely a customer-facing relabel rather than a deeper rework.

Alongside the rename, the team has widened how the app handles web traffic so it can serve more than one domain at once. In plain terms, that lets a temporary hosting URL from AWS Amplify (Amazon's managed app-hosting service) keep working at the same time as a new custom domain - the kind of dual-running setup you do right before you flip a product live.

So what If you're tracking which Mike forks are heading toward a commercial launch under their own brand, easterbrooka just raised a hand.

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 easterbrooka/mike, oldest first. Source extracted verbatim from the harvested git log.

SHA Subject Author Date
5bc4211a Rebrand UI from Mike to Michelle + multi-origin CORS andrew 2026-05-05 ↗ GitHub
commit body
Renames the 8 user-facing brand strings (browser title, logo text,
sidebar nav, workflow badges, modal placeholders, error page,
account page help text). Logo icon is unchanged. Code identifiers
(types, file names, comments) intentionally untouched in this pass.

Backend CORS now accepts a comma-separated FRONTEND_URL so the
amplifyapp.com fallback URL keeps working alongside new custom
subdomains during testing.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

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

⬇ Download capture-thread-59.md