fabiotaroc adds OpenAI as a third brain

The fork wires up OpenAI alongside the Claude and Gemini engines already powering Mike, giving users a third model family to pick from.

integrationinfrastructure

Until now, Mike has run on two AI providers: Anthropic's Claude and Google's Gemini. fabiotaroc's fork adds OpenAI as a peer, with users bringing their own API key and choosing per-conversation which engine answers. The plumbing is cleanly isolated - the existing Claude and Gemini paths are untouched - and the account screen, model picker, and key-storage all extend naturally to a third option.

A few rough edges: the OpenAI model names baked in are forward-dated and will need swapping for whatever's actually shipping when this lands, and the database migration touches a baseline file in a way that could trip up fresh installs. But the overall pattern is the kind of thing other forks could lift wholesale if they want OpenAI parity without rethinking their provider layer.

So what Worth watching if you're running Mike and your team prefers OpenAI's models, or if you want optionality across all three major AI vendors rather than betting on one.

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

Commits in this thread

1 commit from fabiotaroc/mike, oldest first. Source extracted verbatim from the harvested git log.

SHA	Subject	Author	Date
`02111e0e`	Add OpenAI support, migration, model UI, and Turbopack root	taro	2026-04-30	↗ GitHub
Wire OpenAI in the LLM layer with optional user-provided keys, schema migration, model availability/account UI updates, add next.config turbopack root for mono-repo workspaces, and refresh deps. Made-with: Cursor

SHA

Subject

Author

Date

02111e0e

Add OpenAI support, migration, model UI, and Turbopack root

taro

2026-04-30

↗ GitHub

Wire OpenAI in the LLM layer with optional user-provided keys, schema
migration, model availability/account UI updates, add next.config turbopack
root for mono-repo workspaces, and refresh deps.

Made-with: Cursor

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