fayerman-source stops Mike from quietly writing privileged material to disk

Every AI exchange was being saved to a plaintext file on the server, forever. Now it isn't.

securitycompliance

In the original code, every interaction with the AI engine - the prompts going in, the document context attached to them, and the model's answers coming back - was written to a plaintext file on the server. It happened on every call, with no off switch, and the file simply kept growing for as long as the deployment ran.

fayerman-source removed it. The disk-writing is gone entirely, and the only logging that remains is an explicit debug mode that stays off unless someone deliberately turns it on. The change also flags that other forks which extended the AI layer likely carry the same hidden logging - worth a look if you're auditing one.

So what Anyone running a Mike fork on live client matters should care: an unbounded plaintext record of privileged prompts and answers is exactly the kind of confidentiality and retention exposure that gets raised in a breach review.

View this fork on GitHub →

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

Commits in this thread

1 commit from fayerman-source/mike, oldest first. Source extracted verbatim from the harvested git log.

SHA Subject Author Date
95cf296f fix claude raw stream logging Eli Fayerman 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-310.md from inside the repo you want the changes in.

⬇ Download capture-thread-310.md