Meta Muse Spark 1.4 surfaces in RocksDB pull request
An unreleased Meta model identified as muse-spark-1.4-internal appeared in a public pull request on Meta’s RocksDB repository. The request added logging to the experimental live-tuning feature, and apparently auto-generated test notes reportedly recorded a call to the model through Meta’s internal muse service; the pull request was later closed without merging.
The reference provides preliminary evidence that Meta may already be evaluating the next Muse Spark version inside internal database-tuning tooling, although Meta has not confirmed the model, deployment status, release timing, or capabilities.
An unreleased Meta model called muse-spark-1.4-internal has appeared in a public GitHub pull request on Meta’s RocksDB repository. First spotted by @LuminaBench, the reference points to the next version of Meta’s Muse Spark line already running in internal production tooling.
META 🔥: Muse-Spark-1.4-internal has been spotted in one of the PRs on Github. > The PR is a small logging change to RocksDB's experimental "live tuning" feature. > The mention appears to be in the PR notes, which seem to be auto-generated. It's expected that Muse Spark 1.4… https://t.co/VhEpXRseC0 pic.twitter.com/k8fjXYYnY7— 🚨 AI News | TestingCatalog (@testingcatalog) November 13, 2026
The pull request makes a small logging change to RocksDB’s experimental “live tuning” feature. With live tuning, an AI advisor watches a running database and recommends configuration changes. At Meta, that advisor is an LLM accessed through an internal service called muse. The change adds two fields to every recommendation: the name of the model that answered and its usage, including tokens and seconds. The stated goal is to compare a frontier model with small on-host models across the same tuning cycles, measuring both cost and outcome.