zgbrenner adds a does-my-key-actually-work button

A one-click test that tells you whether your AI provider key is live - and why it isn't, in plain English.

integrationworkflow

Connecting an AI account to Mike means pasting in an API key, and until now there was no way to know if you'd done it right short of trying a real task and watching it fail. zgbrenner's fork closes that gap. The settings page - newly relabelled from "AI Preferences" to "Connect AI Accounts" - now puts a Test Connection button next to each provider. Click it and the fork fires off a tiny, cheap request behind the scenes, then shows a green "Connection works" or a red error right there on the page.

The smart bit is the error. Instead of a generic "something went wrong," it passes the provider's own message straight through - things like "invalid authentication" or "insufficient quota" - so a non-technical user can actually tell whether they fat-fingered the key or ran out of credit.

So what Anyone shipping Mike to lawyers rather than engineers should care: this is the difference between a clean self-serve setup and a support ticket.

View this fork on GitHub →

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

Commits in this thread

1 commit from zgbrenner/gary, oldest first. Source extracted verbatim from the harvested git log.

SHA Subject Author Date
3fb09bb3 feat: add Connect AI Account flow and Test Connection feature Zack Brenner 2026-05-19 ↗ GitHub

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

⬇ Download capture-thread-529.md