punyaslokdutta makes Mike run on your own hardware

A small branch swaps Mike's cloud-only AI plumbing for a setup that talks to any local model runtime - no hosted API key required.

infrastructuresecurity

punyaslokdutta has wired Mike's AI adapter so it can point at a local model server instead of the hosted OpenAI service. The trick: tools like Ollama and vLLM (lightweight runtimes that let you run open-source models on your own machine) already speak OpenAI's protocol, so a few configuration knobs are enough to redirect Mike at them. Crucially, Mike no longer demands a cloud API key to start up - a local runtime now counts as a real provider on its own.

The model picker also grows two Qwen options, an open-weights family from Alibaba, in mid-sized variants that fit on a serious laptop or workstation. And answers now stream token-by-token on the local path, because a blank screen while a local model thinks for a minute is the difference between usable and abandoned. A Docker-plus-Ollama walkthrough is included.

The branch is open against upstream and hasn't landed yet.

So what For any firm that won't put privileged matter through a third-party AI vendor, this is the path to running Mike entirely behind your own firewall.

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 punyaslokdutta/HarveyOss, oldest first. Source extracted verbatim from the harvested git log.

SHA Subject Author Date

39cdf1ca chore: local setup - swap R2 for Supabase Storage, install frontend deps Punyaslok Dutta 2026-05-09 ↗ GitHub

SHA	Subject	Author	Date
`39cdf1ca`	chore: local setup - swap R2 for Supabase Storage, install frontend deps	Punyaslok Dutta	2026-05-09	↗ GitHub
commit body - storage.ts: replaced @aws-sdk/client-s3 + R2 with Supabase Storage (upload, download, delete, signed URLs all via @supabase/supabase-js) - .env.example: removed R2 vars, added STORAGE_BUCKET=mike - frontend/package-lock.json: updated after npm install --legacy-peer-deps Local setup recap: - Backend :3001, frontend :3000 - Supabase project: gbdfkvaigunfvrgurkwk (ap-northeast-1 Tokyo) - Storage bucket: mike (private, Supabase Storage) - DB schema applied via 000_one_shot_schema.sql - AI provider: Gemini - Secrets in .env / .env.local - gitignored, not committed Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
`4e73a45d`	Merge remote-tracking branch 'origin/main'	Punyaslok Dutta	2026-05-09	↗ GitHub

commit body

- storage.ts: replaced @aws-sdk/client-s3 + R2 with Supabase Storage
  (upload, download, delete, signed URLs all via @supabase/supabase-js)
- .env.example: removed R2 vars, added STORAGE_BUCKET=mike
- frontend/package-lock.json: updated after npm install --legacy-peer-deps

Local setup recap:
- Backend :3001, frontend :3000
- Supabase project: gbdfkvaigunfvrgurkwk (ap-northeast-1 Tokyo)
- Storage bucket: mike (private, Supabase Storage)
- DB schema applied via 000_one_shot_schema.sql
- AI provider: Gemini
- Secrets in .env / .env.local - gitignored, not committed

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

4e73a45d Merge remote-tracking branch 'origin/main' Punyaslok Dutta 2026-05-09 ↗ 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-490.md from inside the repo you want the changes in.

⬇ Download capture-thread-490.md