## Summary
lawyered0/mike
A security-minded fork of Mike where @lawyered0 hardens access control, safer deletes, and smoother integrations for legal workspaces.
This is Mike as maintained by @lawyered0, and the throughline is unmistakable: locking down who can do what to shared work. Most of the effort here goes into authorization - making sure that deleting folders, editing a review's title or document list, or generating a tabular review is something only the right person can do, not anyone who happens to have a share link into a shared project. Alongside that, @lawyered0 has smoothed off some sharp edges, like a folder-delete in the assistant chat explorer that quietly removed everything under it without warning.
There's a second, quieter track too: keeping connected tools working without friction. That includes silent token refresh for Model Context Protocol integrations, so a session doesn't force you through a full reconnect when a token expires, and a fix that lets a fresh checkout build cleanly even before the environment is fully wired up.
Notably, none of this work has diverged the fork - @lawyered0's changes read as contributions aimed back at Mike itself rather than a separate product. If you're evaluating Mike for a team that shares projects and cares who can delete or edit shared material, this is a good fork to click through to on GitHub.
What's in it
- Owner-only folder deletion Deleting a folder - which cascades through everything nested inside it - is restricted to project owners, not everyone with shared access.
- Confirmed, synced deletes in chat The assistant chat explorer no longer removes a folder and its contents silently; the destructive action is confirmed and the UI stays in sync with what actually happened.
- Locked-down tabular reviews Editing a review's title or document list is limited to the review's owner, and the generation path enforces real document access rather than a share alone.
- Silent MCP token refresh Connected tools using Model Context Protocol can refresh an expired token in the background instead of dragging you through a full reconnect.
- Reliable fresh-checkout builds A clean checkout can complete a production build even when the backend environment isn't fully configured yet.
Direction
securityintegrationinfrastructure
Activity
🟢 #174 Confirm destructive folder deletes in chat explorer +161 -24 19d ago by
lawyered0 ↗ analysis ↗ GitHub ## Summary
## Summary
🟢 #177 Filter project documents before tabular generation +16 -1 19d ago by
lawyered0 ↗ analysis ↗ GitHub ## Summary
⛔ #176 Restrict project folder deletion to project owners +1 20d ago by
lawyered0 ↗ analysis ↗ GitHub ## Summary
## Summary
## Summary
📝 Fix fresh-checkout frontend build failure when Supabase env is absent 0 commits — minor change
📝 lawyered0 puts a seatbelt on the chat explorer's delete button 0 commits — chat-uiknowledge-management draft
Deleting a folder in the assistant chat used to permanently wipe every document inside it with no warning - and then lie about what happened.
Collaborators could quietly rename a review or swap out its documents by going straight to the API, even though the screen treats those as the owner's call.
A collaborator on a shared project could wipe out documents they never owned, just by deleting the folder they sat in.
A fix that stops a single shared review from becoming a skeleton key to an entire project's private documents.
A permissions fix so that being invited to a shared project no longer means you can wipe out its folders.
📝 lawyered0 wants Mike's outside connections to stop logging themselves out 0 commits — integrationworkflow draft
A proposed fix so expired credentials renew quietly in the background instead of dragging users back through a reconnect.
Threads of work (detailed view)
lawyered0 wants Mike's outside connections to stop logging themselves out
A proposed fix so expired credentials renew quietly in the background instead of dragging users back through a reconnect.
lawyered0 locks folder deletion to project owners
A permissions fix so that being invited to a shared project no longer means you can wipe out its folders.
lawyered0 closes a back door in shared document review
A fix that stops a single shared review from becoming a skeleton key to an entire project's private documents.
lawyered0 wants folder deletes locked to the owner
A collaborator on a shared project could wipe out documents they never owned, just by deleting the folder they sat in.
lawyered0 closes a back door on shared document reviews
Collaborators could quietly rename a review or swap out its documents by going straight to the API, even though the screen treats those as the owner's call.
lawyered0 puts a seatbelt on the chat explorer's delete button
Deleting a folder in the assistant chat used to permanently wipe every document inside it with no warning - and then lie about what happened.
Pull requests (detailed view)
🟢 Open (6)
by
lawyered0 · opened 1mo ago by
lawyered0 · opened 1mo ago by
lawyered0 · opened 1mo ago by
lawyered0 · opened 1mo ago by
lawyered0 · opened 21d ago by
lawyered0 · opened 21d ago ⛔ Closed without merge (1)
by
lawyered0 · opened 1mo ago · closed 20d ago