fayerman-source wants Mike to stop logging privileged material by default

A small, pointed PR tried to flip the default from "persist everything" to "persist nothing unless you ask."

securityinfrastructure

Mike's backend was quietly writing every raw event from its AI stream to a plaintext file on disk - and those events carry user prompts, document context, and the assistant's responses. For a tool aimed at legal work, fayerman-source argued that's a confidentiality and retention problem nobody opted into.

The proposed fix was narrow: stop writing the file by default, and keep a debug path available only when an operator deliberately turns it on. Posture shift, not feature work. The PR sat for six days and was closed without merging on May 10, 2026; whether the underlying concern got addressed another way isn't spelled out.

So what Anyone evaluating a Mike fork for real client matters should ask what their vendor's default logging actually captures - and where it lives.

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