Repository navigation
Conversation
|
Thank you: the live catalog observation (12 ids including the Wonder variants) is exactly the evidence needed. I am closing in favor of a different direction: discovery is moving to a fully dynamic list driven by the live endpoint (minus known non-chat families), so no per-model code, baseline, or manifest edits are needed going forward. Your report confirmed the Wonder IDs are live. Please test the dynamic release when it lands. |
|
v0.3.0 is out with fully dynamic discovery: every id from the live catalog is served except the verified non-chat families (sam-, muse-image-, muse-voice-*), so the 12-id response you captured — including the 4 Wonder variants — now flows straight through, with the static baseline kept as offline fallback only. Your live verification was the key evidence for this direction. If you get a chance, re-running your checks ( |
Summary
Adds Muse Wonder + Wonder Full (
muse-wonder-1.0[-contributor],muse-wonder-full-1.0[-contributor]) to themuse-codeprovider.Live
GET https://api.meta.ai/v1/modelsnow returns 12 ids including the 4 Wonder variants. Themuse-spark--only allowlist insrc/catalog.tsdropped them from live discovery, and the static baseline +openclaw.plugin.jsononly listed 5x Spark.Changes:
src/catalog.ts:CHAT_FAMILY_PREFIX→CHAT_FAMILY_PREFIXES = ["muse-spark-", "muse-wonder-"]src/baseline.models.ts+openclaw.plugin.json+ rebuiltdist/: 5 → 9 models (context 1048576, maxTokens 131072, text+image, 0 cost — same as Spark; live rows carry nocontext_length)index.tsdescription/comments,README.mdtable,package.json0.2.0 → 0.3.0 + keywordtest/catalog.test.ts,test/modelMapping.test.tsupdatedHow verified
npm run buildpasses and committeddist/is in syncnpm testpasses (39 tests, 3 files)models listshows 9 muse-code models;agent --model muse-code/muse-wonder-1.0→ WONDER-OK;muse-wonder-full-1.0→ WONDER-FULL-OKNotes
muse-spark-1.3(never contributor).