Models / muse-wonder
Muse Wonder
Meta's model, with closed weights. Forcebench has run it in 4 configurations on the API board. API is models reached through a hosted service; Local, models served on Forcebench’s own hardware.
On the API board
Models reached through a hosted service. Muse Wonder is ranked by the highest-scoring of its 4 configurations: the 12th-highest score of 29 models, not clearly different from 10 other models. Scores are within 3 attempts (c@3) with 95% intervals; each configuration is compared with the highest-scoring one by whether their 95% intervals overlap. Every configuration on the board → Cost and speed →
- 95% interval
Show the numbers
| Configuration | Rank all configs | Within 3 attempts c@3 · 95% CI | Against the highest by 95% interval overlap | Tokens mean · median · p90 | No answer | Latency median per task, every attempt counted | Cost per task | Cost per solved task |
|---|---|---|---|---|---|---|---|---|
| OpenRouter · lowhighest score | 19 | 87%95% CI 84–91 | — | 2k1.6k · 3.5k | 0% | 15 s | $0.061 | $0.069 |
| OpenRouter · medium | 19 | 87%95% CI 84–91 | not clearly different | 3.1k2.4k · 5.9k | 0% | 22 s | $0.084 | $0.096 |
| OpenRouter · max | 19 | 87%95% CI 84–91 | not clearly different | 8.2k5.8k · 20k | 1% | 55 s | $0.22 | $0.25 |
| OpenRouter · high | 23 | 86%95% CI 82–89 | not clearly different | 4.4k3.1k · 9.2k | 0% | 33 s | $0.13 | $0.15 |
- 95% interval
- API board median
Show the numbers
| Suite | c@3 95% CI | API median | Tasks |
|---|---|---|---|
| Apex | 95%95% CI 76–99 | 90% | 20 |
| Salesforce APIs | 83%95% CI 61–94 | 72% | 18 |
| CI/CD | 88%95% CI 66–97 | 88% | 17 |
| Salesforce CLI | 100%95% CI 84–100 | 90% | 20 |
| Salesforce docs | 35%95% CI 17–59 | 29% | 17 |
| fflib Enterprise Patterns | 89%95% CI 67–97 | 61% | 18 |
| Flow | 83%95% CI 61–94 | 78% | 18 |
| Governor limits & pushback | 100%95% CI 83–100 | 89% | 19 |
| Lightning Web Components | 100%95% CI 82–100 | 100% | 18 |
| Nonprofit Success Pack | 100%95% CI 82–100 | 83% | 18 |
| Packaging | 89%95% CI 67–97 | 72% | 18 |
| Permissions & access | 93%95% CI 70–99 | 87% | 15 |
| Scratch org definitions | 67%95% CI 44–84 | 50% | 18 |
| SOQL | 95%95% CI 76–99 | 100% | 20 |
| Trigger Actions Framework | 94%95% CI 74–99 | 89% | 18 |
By reasoning effort
The same configuration at several efforts, each against its lowest reasoning effort on the same tasks (a paired 95% interval), and charted against the effort tier and against the output tokens it costs. These scores are pass@1, the first answer alone: a paired comparison needs both efforts' answers to the same tasks, and not every effort has had its retries. Lite-subset sweeps (4 tasks per suite) are never plotted with the full benchmark. The effort study has every model.
| Configuration · effort · full benchmark | pass@1 95% CI | Against the lowest reasoning effort same tasks, paired | Tokens |
|---|---|---|---|
| lowbaseline | 70%95% CI 65–75 | — | 2k |
| medium | 77%95% CI 73–82 | clearly higher (+7 pts, 95% CI +3 pts to +12 pts) | 3.1k |
| high | 69%95% CI 64–74 | no clear difference (−1 pt, 95% CI −5 pts to +4 pts); this data can't rule out a change of up to 5 points | 4.4k |
| max | 74%95% CI 69–78 | no clear difference (+4 pts, 95% CI −0.7 pts to +8 pts); this data can't rule out a change of up to 8 points | 8.2k |
Show the numbers
| Model | Effort (tier) | pass@1 | 95% CI | Tasks | No answer | Tokens: mean | median | Reasoning tokens | Latency: median per answer |
|---|---|---|---|---|---|---|---|---|---|
| Muse Wonder | low | 70% | 65–75 | 272 | 0% | 2k | 1.6k | 1.4k | 15 s |
| Muse Wonder | medium | 77% | 73–82 | 272 | 0% | 3.1k | 2.4k | 2.5k | 22 s |
| Muse Wonder | high | 69% | 64–74 | 272 | 0% | 4.4k | 3.1k | 3.8k | 30 s |
| Muse Wonder | max | 74% | 69–78 | 272 | 1% | 8.2k | 5.8k | 7.6k | 53 s |
In the studies
- Reasoning effort: its score against effort and against output tokens.
- Max effort: what its max effort did against the effort below it.
- Local vs API: where it lands among the configurations of both boards.
- Pushback: whether it pushed back on requests that break at scale.
Private evaluations
Want this for your team?
Azul Labs runs Forcebench privately for two kinds of Salesforce team.
Choosing a model to run yourself?
A private benchmark of your shortlist
Open-weight models at the quantisations and reasoning efforts you could run on infrastructure you control, tested on your kind of Salesforce work, with a written recommendation.
- Private tasks written from your work only ever run on local models; they are never sent to an API.
- Re-testing after any change of model, quantisation or engine is available.
- Typical turnaround is 2–3 weeks; large models take about a day of machine time per configuration.
Building or buying a Salesforce AI tool?
A private evaluation of your tool
Your tool on held-out tasks it has never seen, against API baselines (models reached through a hosted service) and Local ones (served on Forcebench’s own hardware), with a written report on where it holds up and where it fails.
- It can start as a smaller pilot, about 30 held-out tasks with your tool against two baselines, before a full evaluation.
- Repeat evaluations after your releases are available.
- Typical turnaround is 2–3 weeks.
Fixed fee, quoted up front. The quote depends on the number of tasks and the number of models, tools or configurations tested.
Or email leo@azl.au · azl.au