Allow personal Case.dev keys in demo mode

✅ merged · #4 · CaseMark/mikeoss-casedotdev ← CaseMark/mikeoss-casedotdev · opened 22d ago by kveton · merged 22d ago by kveton · self · +57-59 across 2 files · ↗ on GitHub

From the PR description

Summary\n- Make hosted Demo Mode use the shared Case.dev key only when a user has not saved a personal Case.dev key.\n- Allow users to save or clear their own Case.dev key in Demo Mode; clearing falls back to the shared demo key.\n- Update Account > Models copy and controls so the demo key is the default, while personal Case.dev keys can override it.\n- Keep Anthropic/Gemini direct-provider keys disabled in the hosted demo UI for now.\n- Removed the production MIKE_DEMO_GLOBAL_BUDGET_USD env var so the hosted demo uses the per-user budget without an accidental shared global cap.\n\n## Verification\n- Prod API currently returns demo source and live Case model catalog for scott@kveton.com.\n- npm run build --prefix backend\n- cd frontend && npx tsc --noEmit\n- git diff --check

Our analysis

Personal Case.dev keys can override the shared demo key — read the full analysis →

Think the analysis missed something the PR description covers?

Commits in this PR (1)

SHA Subject Author Date
4a979679 Allow Case key override in demo mode kveton 2026-05-04 ↗ GitHub

Capture this PR into my fork

Download a Markdown prompt that tells Claude how to port every commit in this PR into your working tree. Run it via claude -p < capture-pull-4.md from inside the repo you want the changes in.

⬇ Download capture-pull-4.md