CaseMark unlocks the demo so users can bring their own key

Hosted-demo users were trapped on a shared account with a tiny lifetime budget. Now they can plug in their own.

multi-tenantinfrastructure

CaseMark runs a hosted demo of its Mike fork where everyone shares one Case.dev account - Case.dev being the AI provider that powers the assistant - capped at a $5 lifetime budget. Until now that cap was a wall: the demo key was forced on every user, and anyone who tried to add their own account was blocked outright.

This change flips the priority. The system now checks for a personal key first and only falls back to the shared demo key if none is set. Users on the hosted demo can drop in their own Case.dev key from their account settings to bypass the budget entirely, and clearing it returns them to the shared key. The in-app copy was rewritten to say so plainly.

So what Anyone running a shared-fallback-with-bring-your-own-key setup should look at this - it's a clean pattern for letting individual users escape a common budget cap.

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

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

SHA

Subject

Author

Date

4a979679

Allow Case key override in demo mode

kveton

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

CaseMark unlocks the demo so users can bring their own key

Commits in this thread

Capture this thread into my fork