thegrif gives Mike a third AI engine with OpenAI

Mike could already run on Claude or Gemini; thegrif adds OpenAI as a third option you can switch to.

integrationinfrastructure

thegrif wires OpenAI in as a third AI provider, built the same way as the two already there. The practical upshot is choice: the model picker now lists OpenAI, and there's a field to drop in your own OpenAI key. Nothing changes for existing setups unless you opt in - the defaults still point at the current engines, so no one gets quietly moved onto OpenAI.

One thing to check before going live: the specific OpenAI model names baked into this fork are forward-looking, so confirm they match what OpenAI actually offers when you adopt it.

So what Worth a look for anyone running Mike who'd rather shop AI vendors on price, performance, or procurement comfort than stay locked to one.

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.