CaseMark makes the demo meter honest about your own key

Bring your own API key and CaseMark's trial-credit card now tells you plainly that those free credits aren't being spent.

chat-ui

Forks of Mike that run a hosted demo usually show a budget card tracking how much of your free trial allowance you've burned through. The catch: once a user plugs in their own paid key, that meter gets confusing - is it still counting? CaseMark fixed the ambiguity. The card now stays visible whenever demo mode is on, and when a personal key is doing the work it shows a calm gray "Bypassed" badge alongside the usual active and exhausted states, with copy that spells out the difference.

It's a small touch, but it removes a real moment of doubt for anyone evaluating a legal-AI tool: you can see at a glance that you're spending your own credits, not someone else's trial pool.

So what Worth a look for anyone running a trial-to-paid flow who's tired of users asking whether the free credits are still ticking.

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

SHA Subject Author Date
918566b0 Show demo budget when personal key is active kveton 2026-05-04 ↗ GitHub
bae6a181 Clarify bypassed demo budget state 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-280.md from inside the repo you want the changes in.

⬇ Download capture-thread-280.md