contractCouncil rebrands Mike to MatrixAI - and quietly turns auth off
A cosmetic rename ships alongside a dev-mode stub that signs every visitor in as the same hardcoded user.
On the surface, this is a wholesale rebrand: the "Mike" name is swept out of the chat, projects, tables, and workflow surfaces and replaced with "Matrix AI" - logo, placeholders, labels, the lot. Pure paint job, no behaviour change in any of those screens.
Buried in the same commit is something more consequential. The fork rips out the authentication layer wired to Supabase (the hosted backend service many AI side-projects use for login) and replaces it with a hardcoded "always signed in" user. Every visitor lands as the same fake developer account, no login screen, no sign-out. The commit message doesn't mention it. It reads as a local-development shortcut, but there's no flag or environment guard keeping it out of production.
If you're tracking how forks diverge on safety basics, this is a useful cautionary tale: a routine-looking rebrand commit can carry a load-bearing security change that a casual reviewer would miss entirely.
Spotted something wrong? Or know the PR text has fresher detail than the writeup above?