fayerman-source moves to stop the logs from spilling privileged material

A backend fix that keeps client prompts and document context out of an unguarded plaintext file on disk.

securityinfrastructure

fayerman-source spotted a quiet leak in how the fork's AI layer keeps records. Every raw exchange with the Claude model - the user's question, the document text fed in as context, and the model's answer - was being written, in full, to a plain text file on disk by default. Nobody rotates that file, nobody guards it, and in a legal workflow it is exactly the privileged material you do not want piling up unread on a server.

The proposed change deletes that automatic file and instead only prints the raw stream when an operator deliberately turns on a debug setting. Developers who need to inspect what the model is doing still can; a normal deployment writes nothing sensitive to disk. Worth noting: the change was filed against the main project but closed without being merged, so the default logging it targeted is still in place there.

So what Anyone running a Mike-based tool on client documents should know where their raw prompts and context end up - and this is the kind of default that quietly turns every deployment into a data-retention liability.

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

⬇ Download capture-thread-801.md