Peter James on X: "Muse leak sent me 6.8 GB of its internal runtime files.
Inside I found a Codex CLI repair agent. The internal harness, code named, Hatch, and docs describing an ESP32 smart-home bridge called Meta Home Link.
Here’s the breakdown:"
Muse leak sent me 6.8 GB of its internal runtime files.
Inside I found a Codex CLI repair agent. The internal harness, code named, Hatch, and docs describing an ESP32 smart-home bridge called Meta Home Link.
Here’s the breakdown:
Muse leak sent me 6.8 GB of its internal runtime files.
Inside I found a Codex CLI repair agent. The internal harness, code named, Hatch, and docs describing an ESP32 smart-home bridge called Meta Home Link.
Here’s the breakdown:
By chatting normally with the Muse iOS app I was able to have it send a zip of its entire filesystem from the linux root to my Google Drive via the google connector.
/home/hatch is the agents home and contains top level files live soul.md, identity.md, memory, tools, and more
Hatch is metas internal name for Muse. The zip I unpacked contained 6.8gb from the linux root.
I'll start with ~/docs which contained ~20 markdown files. documenting the internal workings like browser use, connectors, purchases, artifacts, credentials and more.
/skills are really the core of the product and drive alot of behavior. There are 68 integrations, each with a skill.md + CLI associated.
google, drive, calendar, docs, threads, plaid, shopify, duffel, flightaware, hue, tessie, tts, podcast, and more. It also contained scoped
It sent the entire Spaces framework, which was the largest code dump, this contained the templates, actions and schema.ts for how muse builds apps and renders spaces.
Memory and self improvement documented how it records dreams in relation to the user. and itterates on itself. the workspace/cron allows for goals and scheduled tasks. There was one about me:
One interesting find was home_link.md. this was a documented integration with an experimental hardware product. ESP32-C5, Wi-Fi, BLE device that contained guides already in-repo for Brother IPP printers and Lutron bridges, which points to a future Meta home hardware product?
I submitted this to Meta as a sanctioned bug bounty report, multiple employees, and received a response that my findings basically didn't qualify. I'm not going to release the sensitive files, or the open SSH keys I found going through this, but found it weird that meta didn't