Been reading through the Claude Code leak non stop… The March 31st Claude Code leak revealed a hidden background agent called Auto Dream (internal flag tengu_onyx_plover). It runs a maintenance cycle while the user is idle to prune outdated entries and merge “memory trails” into a persistent MEMORY.md. We’ve been building a local-first equivalent called Bitterbot for the past year. We just published the repo on March 28th — purely by chance, 48 hours before the leak. It’s fascinating (even if a bit surreal) to see how closely their autoDream loop mirrors our Dream Engine. It feels like an inexplicable coincidence considering we spent most of last year feeding our architecture specs into Claude for coding help. Seeing a near-identical “Auto Dream” loop in their leaked source code raises some interesting questions about training data vs. technical necessity. Given the leak, does the Local-First memory (no cloud sync) become the only way for developers to protect their intellectual property? submitted by /u/Doug_Bitterbot
Originally posted by u/Doug_Bitterbot on r/ArtificialInteligence