vadi25 renames Mike to Patronus and locks down who can see what

A rebrand on the surface, but underneath it adds OpenAI as an engine option and tightens data isolation across the whole system.

securityintegration

This fork, renamed from Mike to Patronus, does two things worth a look past the cosmetic name change. First, it wires in OpenAI - the maker of ChatGPT - as a third engine behind the chat and document tools, alongside the Claude and Gemini models the codebase already supported, and flips it to the default. If your team has standardized on OpenAI, this is a working version of that.

The more consequential move is on data security. The original Mike only locked down user-profile records and trusted the application layer to keep one user's matters out of another's view everywhere else. vadi25 turns on per-user access rules at the database itself, across projects, documents, chats, and review tables - so each person sees only their own work, enforced at the data layer rather than assumed.

So what Anyone weighing a Mike-based tool where client confidentiality is the whole point should look here: data isolation is now enforced in the database, not just trusted to the app.

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

Commits in this thread

1 commit from vadi25/patronus, oldest first. Source extracted verbatim from the harvested git log.

SHA	Subject	Author	Date
`908aefd0`	refactor: migrate project API to Patronus client, rebrand UI icons, implement Supabase schema, and add comprehensive project documentation	vadi25	2026-04-30	↗ GitHub

SHA

Subject

Author

Date

908aefd0

refactor: migrate project API to Patronus client, rebrand UI icons, implement Supabase schema, and add comprehensive project documentation

vadi25

2026-04-30

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