An inspection of Muse's runtime uncovered a model ID azure/muse-special used in one agent session amid a majority of Meta’s Avocado sessions. Logs contain a gpt_responses_v1 signature with an encrypted payload starting gAAAAA (an OpenAI marker) and tool-call IDs formatted like OpenAI's Responses API. The shipped model catalogue includes many Avocado variants plus Claude (Anthropic), Sonnet/Haiku, GPT-5.5/5.6 variants via OpenAI/Azure/Codex and other Meta-hosted routes. Repository files include an Anthropic client, prompt conversion and SSE parsers, API key files restricted to an inference-proxy, and an environment reverse-proxy kill-switch.
Those traces show Muse routes some requests to frontier providers rather than running solely on Avocado, enabling selective use, A/B testing, or behind-the-scenes routing for tasks where external models perform better. Encrypted reasoning blobs produced by muse-special are forwarded to Azure and are unreadable to Meta’s RL server, while Avocado sessions write unencrypted chain-of-thought text into transcripts that can be used for training unless users opt out. The runtime therefore supports server-side provider selection and telemetry; the observed evidence shows muse-special is an OpenAI model served through Azure, with only a single outlier session observed.
Summary generated by AI from the linked article. hn.today is not affiliated with Hacker News or Y Combinator.