manueljpconde teaches Mike to run on your own hardware

A fourth AI option lets the fork point at a self-hosted or local model instead of the big cloud providers.

infrastructuresecurity

Until now, Mike's brain had to be one of three cloud services - Anthropic, Google, or OpenAI. manueljpconde adds a fourth path: point the system at a model running on your own server or a local setup (think Ollama, a popular tool for running AI models on your own machine), and client data never has to leave your walls. From a user's seat it's just another model name in the dropdown.

There are honest limits. Local models often can't reliably drive Mike's tool-using features, so when that's the case the fork quietly switches them off and tells the user why. There's also no automatic retry or fallback if the local model misbehaves, and the setup trusts whatever you declare about its capabilities rather than checking. This is a foundation, not a turnkey deployment.

So what For firms and legal-ops teams who can't send client matter to a third-party cloud, this is the difference between Mike being usable and being a non-starter.

View this fork on GitHub →

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

Commits in this thread

2 commits from manueljpconde/mikept, oldest first. Source extracted verbatim from the harvested git log.

SHA Subject Author Date
c0361944 feat: add self-hosted local llm provider Manuel Conde 2026-05-09 ↗ GitHub
c8ef360f Merge pull request #2 from manueljpconde/codex/local-llm-provider Manuel Conde 2026-05-09 ↗ GitHub
Add self-hosted local LLM provider support

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

⬇ Download capture-thread-209.md