sean-a-ward unhooks Mike from a single AI vendor
The fork can now point its AI engine at whatever provider you choose - and let each user pick their own.
Out of the box, Mike talks to one AI vendor and one only. sean-a-ward rewired that, so the fork can route its requests to any compatible provider - including marketplaces like OpenRouter, which act as a single doorway to dozens of competing AI models. A behind-the-scenes mapping layer translates Mike's built-in model names into whatever each provider expects, so nothing downstream has to change.
The choice isn't just an admin switch, either. sean-a-ward pushed it down to the individual: a new section under account settings lets each user supply their own provider details and model mapping. There's also a careful fallback so deployments that haven't yet updated their database keep working rather than breaking on the spot.
Spotted something wrong? Or know the PR text has fresher detail than the writeup above?