thegrif adds OpenAI as a third engine option

Mike already let users pick between Anthropic's Claude and Google's Gemini. Tom Griffin's fork makes OpenAI a peer.

integrationinfrastructure

The fork plugs OpenAI into the same slot the other two providers already occupy: streaming chat, tool use, the works. Users get a new field on their account page to drop in an OpenAI API key, and a model picker that now lists GPT alongside the existing options.

Nothing changes by default. Gemini stays the out-of-the-box choice, and existing installs are untouched until a user actively switches. The shift is about optionality - if your firm has an OpenAI contract, a preferred vendor relationship, or just wants a third opinion on a draft, the door is now open. Worth noting the specific GPT model identifiers wired in are forward-looking guesses and may need swapping once OpenAI ships whatever it actually ships next.

So what Useful for any team running Mike that's already paying OpenAI and would rather not juggle two vendor relationships to use it.

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

Commits in this thread

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

SHA	Subject	Author	Date
`860e6ff5`	Add OpenAI as third LLM provider (GPT-5.5, GPT-5.4 Nano)	Tom Griffin	2026-05-01	↗ GitHub
commit body Adds full OpenAI support across backend and frontend, following the existing Claude/Gemini provider pattern: streaming chat with tool use, text completion, model selection UI, API key management, and DB schema. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

SHA

Subject

Author

Date

860e6ff5

Add OpenAI as third LLM provider (GPT-5.5, GPT-5.4 Nano)

Tom Griffin

2026-05-01

↗ GitHub

commit body

Adds full OpenAI support across backend and frontend, following the
existing Claude/Gemini provider pattern: streaming chat with tool use,
text completion, model selection UI, API key management, and DB schema.

Co-Authored-By: Claude Opus 4.6 (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-135.md from inside the repo you want the changes in.