Meta's Muse coding agent appears to route some tasks to an OpenAI model labeled muse-special

Meta's Muse appears to use an OpenAI model labeled muse-special

A developer digging through Muse's local files found a model called azure/muse-special that uses OpenAI's GPT Responses API. Nearly all sessions run on Meta's in-house Avocado model, but at least one sub-agent task was routed externally. The shipped daemon also bundles clients and API keys for Claude Opus 4.6/4.7/4.8, Sonnet 4.6, and GPT-5.5/5.6, with a kill switch to disable the external proxy. The author believes muse-special is likely a GPT model on Azure, though the exact version isn't disclosed. External reasoning chains are encrypted and unavailable to Meta, so distillation seems unlikely; Avocado's reasoning is stored in plaintext and usable for RL.

Why it matters: First-hand reverse-engineering find with concrete file names and routing evidence — not speculation. Meta's in-house Avocado handles most tasks but at least one sub-agent routes to OpenAI, plus bundled Claude Opus versions. Docked because it's a single-source blog without Meta...