author here. I kept digging through the Muse filesystem after my first post hit the front page here this week.
Going through my logs I found a background agent that used a model called azure/muse-special while building my website. I found this interesting and dug a little deeper.
The transcript and daemon binary point to an OpenAI model running on Azure. Still unclear which one or why it was selected.
The runtime also ships with an Anthropic client and a catalogue listing Claude, GPT and Kimi models. I didn’t observe Claude being used in my own sessions, but this is my Part 2 of exploring the Muse file system.
If it's using the same weird (and awful) "backend prompt encryption" pattern and mechanism that Codex also uses (https://news.ycombinator.com/item?id=48905028), then I'd also say it points to OpenAI being involved. Hopefully that shit isn't becoming a more popular pattern, absolutely awful for troubleshooting stuff.
I'm not no. Someone from meta would have to chime in... but its very openai shaped and served differently from all the other models listed in the daemon, under a mysterious name.
a fine-tuned OpenAI model on Azure for the purpose of compaction or something could make sense I guess but that would still be OpenAI's weights with meta ontop, and they already have a compaction model served under azure/avocado-compaction-v1
The Muse public APIs seem to be heavily inspired by OpenAI's, they even support the richer "responses" API. They have a similarly shaped compaction API, they have the same "encrypted" reasoning. Even the Muse harness seems heavily inspired by (open source) Codex. Considering Azure's historic involvement w/ OpenAI, it seems more plausible that Azure is used as spill-over capacity, and the same Azure infra used to encrypt GPT models encrypts Muse models.
My guess that the generally visible Anthropic/OpenAI details are leftovers from the whole meta "move fast" behavior. There are a few rough edges on the product where it leaks internal codenames (eg. signing in w/ WhatsApp required consenting to using "hatch" on one screen), so I'd believe that this was a leftover on the VM from the prototyping stage, before the Muse models were ready, or because the dev's got to benchmark against different models.
I think they were asking, "If this is a model produced by Meta with an API designed to be compatible with OpenAI models, but it's not actually an OpenAI model, why is Meta hosting it on Azure?"
Meta already serves its own models on Azure under their real names. azure/avocado-compaction-v1 and azure/avocado-memory-flush-v1 are in the same catalog. Those sessions do not come back as gpt_responses_v1 items with rs_ ids and encrypted reasoning.
I'm not sure I understand why they would route it to other models. It can't be that they don't have enough compute. Maybe worried that the answer from their own models would be bad? Doesn't really make sense, but I could be missing something.
i agree, and it's what made me spend time exploring today.
fair q. call_ ids and gAAAAA blobs arent damning but the rs_ reasoning ids embed a unix timestamp that matches the session to the second, then OpenAI's 819x marker. plus the summary is in OpenAI's summarizer voice.
Depends on the size of the deal. OpenAI would have to disclose it in their S-1 if it crossed the threshold of being material information for investors.
I had a totally benign chat with OpenAI and it titled it as “amateur porn” in Chinese characters, it was very alarmed when I pointed the conversation name out to it. It almost never misses these days, but when it does the failure modes are very strange.
I remember getting a bunch of „Thanks for watching! Subscribe and smash that like button“ in the middle of chat sessions a few times (like, more than 3 times over the past 3y)
It kind of makes sense when you think about it. If the training data is YouTube transcripts, people often abruptly switch from content to asking for a subscription.
Every engineer at Meta is using Claude (and in some cases Codex) to do their work. Willing to bet that Muse itself was ~100% written by Claude/Codex. Pride goes out of the window when business is involved.
[OP] Aeroi | 3 hours ago
Going through my logs I found a background agent that used a model called azure/muse-special while building my website. I found this interesting and dug a little deeper.
The transcript and daemon binary point to an OpenAI model running on Azure. Still unclear which one or why it was selected.
The runtime also ships with an Anthropic client and a catalogue listing Claude, GPT and Kimi models. I didn’t observe Claude being used in my own sessions, but this is my Part 2 of exploring the Muse file system.
original post: https://x.com/heypeterjames/status/2103545183400800746
pete at mouse dot dev
haolez | 3 hours ago
Are you sure this isn't just a custom model that is API-compatible with OpenAI?
embedding-shape | 3 hours ago
junofan | 2 hours ago
hobofan | 56 minutes ago
[OP] Aeroi | 2 hours ago
a fine-tuned OpenAI model on Azure for the purpose of compaction or something could make sense I guess but that would still be OpenAI's weights with meta ontop, and they already have a compaction model served under azure/avocado-compaction-v1
VygmraMGVl | an hour ago
Source 2: I work on AI at Meta.
verdverm | an hour ago
vineyardmike | an hour ago
The Muse public APIs seem to be heavily inspired by OpenAI's, they even support the richer "responses" API. They have a similarly shaped compaction API, they have the same "encrypted" reasoning. Even the Muse harness seems heavily inspired by (open source) Codex. Considering Azure's historic involvement w/ OpenAI, it seems more plausible that Azure is used as spill-over capacity, and the same Azure infra used to encrypt GPT models encrypts Muse models.
My guess that the generally visible Anthropic/OpenAI details are leftovers from the whole meta "move fast" behavior. There are a few rough edges on the product where it leaks internal codenames (eg. signing in w/ WhatsApp required consenting to using "hatch" on one screen), so I'd believe that this was a leftover on the VM from the prototyping stage, before the Muse models were ready, or because the dev's got to benchmark against different models.
binlog | an hour ago
xmcp123 | 35 minutes ago
thinkling | 14 minutes ago
alexgoodhart | an hour ago
Tiberium | 3 hours ago
[OP] Aeroi | 2 hours ago
catchnear4321 | 2 hours ago
definitely tracks with alexandr’s hand-wavey influencer turn.
VygmraMGVl | an hour ago
https://dev.meta.ai/docs/overview
Source: I work on AI at Meta.
GenerWork | 2 hours ago
[OP] Aeroi | 2 hours ago
fair q. call_ ids and gAAAAA blobs arent damning but the rs_ reasoning ids embed a unix timestamp that matches the session to the second, then OpenAI's 819x marker. plus the summary is in OpenAI's summarizer voice.
its just a best guess.
fg137 | 13 minutes ago
How do you know?
Every cloud provider (AWS, Azure etc) is struggling with meeting LLM demand.
Source: first hand info
6thbit | 2 hours ago
meric_ | 2 hours ago
micromacrofoot | an hour ago
binlog | an hour ago
manav | 2 hours ago
sroussey | 2 hours ago
tclancy | 2 hours ago
Still sleeping with one eye open.
wincy | 2 hours ago
dgellow | 53 minutes ago
xmcp123 | 34 minutes ago
If AI is typeahead on crack, then this tracks.
fg137 | 18 minutes ago
ChickeNES | 2 hours ago
arshxyz | 2 hours ago
tehjoker | an hour ago
sourcecodeplz | 37 minutes ago
binlog | 12 minutes ago
sejje | 28 minutes ago