Meta's Muse Code update adds another named model surface to the coding-agent release lane. The site signal is not that one more model exists; it is that coding capability is being packaged with plan, feature, and developer access decisions.
That matters because coding models increasingly compete through distribution surfaces, not isolated benchmark claims. The useful follow-up is whether Muse Code becomes a routable component inside external IDEs, gateways, and agent workflows, or remains primarily an in-family Meta developer surface.