CaseMark is locking the doors before launch

A quiet seven-commit hardening pass turns this Mike fork from a working prototype into something safe to put in front of real users.

infrastructuresecurity

Most of CaseMark's recent work isn't a new feature you'd notice - it's the unglamorous plumbing that decides whether a public deployment embarrasses you. The team fixed a bug that was silently dropping chat history from matters, added rate limits so nobody can hammer the AI endpoints, and tightened how errors reach users: instead of leaking raw internal messages, the system now only returns a vetted set of safe ones.

There's also a correctness fix that matters to anyone reusing this code. The fork was quietly corrupting structured data when run against a standard database rather than the hosted setup it was built on - the kind of failure that doesn't throw an error, it just rots your records. That's now handled, along with cleaner handling of mid-conversation failures so the chat doesn't freeze half-finished.

So what If you're eyeing this fork as the base for a client-facing legal product, this is the pass that makes it deployable - read it closely before you ship.

View this fork on GitHub →

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

Commits in this thread

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

SHA Subject Author Date
3011eb79 Persist workflow metadata for chat messages kveton 2026-05-04 ↗ GitHub
d5539959 Harden document access and request limits kveton 2026-05-04 ↗ GitHub
4e770c9b Normalize document load errors kveton 2026-05-04 ↗ GitHub
a2842e05 Handle streamed chat errors kveton 2026-05-04 ↗ GitHub
e0f2d13d Optimize tabular document access checks kveton 2026-05-04 ↗ GitHub
3aadb6f8 Serialize jsonb values in Postgres compat writes kveton 2026-05-04 ↗ GitHub
8a72b816 Merge pull request #8 from CaseMark/codex/stream-error-review Scott Kveton 2026-05-04 ↗ GitHub
[codex] Handle streamed chat errors and harden document access

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

⬇ Download capture-thread-38.md