falg23043 moves Mike onto AWS Bedrock

The fork drops the bring-your-own-API-key model and turns Mike into a firm-hosted deployment running Claude through AWS.

infrastructuresecurity

Upstream Mike asks each user to paste in their own Anthropic key. falg23043 has cut that out entirely and routed the AI calls through AWS Bedrock - Amazon's managed service for running models like Claude inside a firm's own cloud account. Credentials live on the server, not on individual desktops, and the user-facing key field is gone from the account screen. A database migration removes the old per-user key column outright.

The default models flip too: main chat runs on Claude Sonnet 4.6, with the faster, cheaper Haiku 4.5 handling background jobs like titles and table work. A companion notes file in the repo reads like a candid deployment diary - useful context, but it also flags that the work isn't fully tested and that one of the model IDs looks unverified.

So what Relevant for any firm or legal-ops lead who wants Mike behind their own AWS perimeter rather than asking lawyers to manage personal AI keys.

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

SHA Subject Author Date
69114a66 feat: replace Anthropic direct API with AWS Bedrock Guillaume Falardeau 2026-05-04 ↗ GitHub
commit body
- Add @anthropic-ai/bedrock-sdk package
- New bedrock.ts provider adapter (mirrors claude.ts, uses AnthropicBedrock client)
- Bedrock model IDs: sonnet-4-6, haiku-4-5 (user-selectable), opus-4-6 (internal)
- Remove per-user claude_api_key; AWS creds are server-side env vars
- Update model defaults: main=bedrock-sonnet, tabular/title=bedrock-haiku
- Frontend: add Bedrock group to model picker, remove Anthropic API key UI
- DB migration 001: drop claude_api_key column, update tabular_model default
4c9bdbdf docs: add BEDROCK.md session recovery reference Guillaume Falardeau 2026-05-04 ↗ 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-132.md from inside the repo you want the changes in.

⬇ Download capture-thread-132.md