CaseMark lets operators bring their own AI keys

kveton's fork now stores Anthropic and Gemini API keys encrypted so firms can plug in their own model accounts alongside the built-in ones.

integrationsecurity

The change is structural, not cosmetic. CaseMark added encrypted storage for customer-supplied API keys - the kind of credential a firm might already hold with Anthropic (maker of Claude) or Google (maker of Gemini) - and then taught the model picker to read from those credentials to decide what's actually selectable. The platform's own Case.dev models stay in the mix; native Claude and Gemini join them as first-class options whenever a key is configured.

The settings page was reshaped to match: separate sections for Case.dev, model providers, defaults, and storage, with Case Vault kept as the canonical storage backend. Three follow-up commits chasing review feedback suggest the team took the credential and provider semantics seriously before merging.

So what Worth a look for legal-ops leads weighing whether to commit to a vendor's model stack or keep their own AI billing relationship - CaseMark is making space for both.

View this fork on GitHub →

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

Commits in this thread

4 commits from CaseMark/mikeoss-casedotdev, oldest first. Source extracted verbatim from the harvested git log.

SHA Subject Author Date
c0ed073a Add BYOK model provider settings kveton 2026-05-04 ↗ GitHub
2032ca81 Address BYOK review feedback kveton 2026-05-04 ↗ GitHub
b3098e8b Tighten BYOK review fixes kveton 2026-05-04 ↗ GitHub
54f5b8b8 Polish BYOK provider feedback 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-288.md from inside the repo you want the changes in.

⬇ Download capture-thread-288.md