zgbrenner makes bring-your-own-key setup something a lawyer can actually do

Connecting your own AI provider account now comes with a one-click check that it actually works before you depend on it.

integrationworkflow

Forks of Mike often let firms plug in their own AI provider account rather than ride on a shared one - cheaper, and your data stays under your contract. The catch has always been that wiring up a key is a developer chore: paste a long secret, save, and pray. zgbrenner has rebuilt that screen into a "Connect AI Account" flow aimed squarely at non-technical users, with a "Test Connection" button that checks the key against the provider and tells you on the spot whether it's live.

The small-but-real upgrade is that verification happens before you rely on the connection, so a typo'd or expired key surfaces immediately instead of mid-matter. The setup guide and in-app terminology were updated to match.

So what If your firm runs Mike on its own AI account, this is the difference between an ops person setting it up confidently and filing a ticket - worth a look on GitHub.

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