Repository navigation
Releases
v0.4.0: Muse Code OAuth settings page
v0.4.0: Muse Code OAuth settings page
The Muse Code sign-in leaves the bottom of Settings → Models and becomes its own DSH settings page, styled like the native pages.
Highlights
- Muse Code OAuth settings page. A new
settings.section(idmuse-code-oauth, order 53) shows the live sign-in state, the device code while Meta waits, the Meta page link, a/muse-loginfallback, and the route facts. The page polls the existing status route, so it flips to Signed in without a reload. - Cleaner Models page. The provider row is labeled
muse-code-oauthand the inline sign-in card is gone. The shippedmetaroute, its models, its credential reference, and the adapter are unchanged. - Upgrade-safe rename. 0.3.x installs stored Muse Code (Meta subscription) as the display name. The plugin rewrites that legacy label on the next boot; a display name edited by hand is preserved.
- Documentation. New
docs/settings-page.mdcovers the states, actions, fallback, and row rename. The README, sign-in notes, troubleshooting, and changelog were updated.
Upgrade
dsh plugin --profile desktop add @thestreamcode/dsh-muse-codeRestart DSH after upgrading, then open Settings → Muse Code OAuth.
Verification
npm run typechecknpm test(44 tests)npm pack --dry-run(15 files, package@thestreamcode/dsh-muse-code@0.4.0)
Companion
The same DSH settings-page design was applied to the community Gemini OAuth bridge (hyqhyq3/dsh-gemini-oauth-bridge) as a companion pull request, so both subscription sign-in pages now share one design language.
Full changelog: https://github.com/TheStreamCode/dsh-muse-code/blob/main/CHANGELOG.md
v0.3.0
What changed
- Local wire adapter in front of
api.meta.ai: it aliases the client tool names that collide with the Muse Code builtin catalog, restores them in the response, and normalizes the Responses parameters. - The
metaroute'sbaseURLpoints at the adapter, so subscription requests keep working after Meta's 2026-10-29 client restriction. ADAPTER_CONTRACT.mdv3 pins the 40-name collision set and the automatic full-aliasing retry.MUSE_CODE_ADAPTER=offkeeps the loopback proxy but disables the reshaping.
Install
dsh plugin --profile desktop add @thestreamcode/dsh-muse-codev0.2.4: report Meta's client restriction
0.2.4
- Meta's client restriction is shown as a policy refusal instead of
API key is invalid. - The sign-in always uses the browser OAuth method; it never falls back to an API-key prompt.
- Sign-in copy now states that model access depends on Meta's subscription policy.
- The README explains the restriction and notes that older DSH versions may label it as an invalid key.
v0.2.3
What changed
- Delete on the Muse Code row now signs out: removing the user-layer route deletes the
llm-pi-ai/metaOAuth record and clears the mirroredMUSE_CODE_SUB_TOKENreference, so no green dot is left behind for a row that no longer exists. The plugin re-declares the row (red dot) on the next refresh or restart. - Prompt-cache facts documented: Meta caches per
prompt_cache_key(DSH sends the session id). Same key → 1521/1600 cached; different or no key → 0. After a 12-minute pause same-key entries still reported 2673/2800 cached, with or withoutprompt_cache_retention: 24h, and a fresh key reported 0 — the default retention is enough, so no knob is exposed.
Upgrade
Reinstall and restart DSH. Existing sign-ins keep working; Delete now performs a real sign-out.
v0.2.2
What changed
- Native credential dot. The route now declares
apiKeyEnv: MUSE_CODE_SUB_TOKEN, so DSH paints its standard red/green credential dot on the Muse Code row. The plugin mirrors the OAuth record's minted key into that reference and re-mints it before Meta's ~24 h expiry (the identity token is preserved, and a concurrent fresh sign-in is never overwritten). - Live catalog fix. The Settings form projects an absent
modelsarray as[]; the sync treated that as a user-owned list and skipped, so Muse Wonder could stay out of the route. Only a non-empty list counts now. - Docs. How Meta caches prompts (
prompt_cache_key= DSH session id: same key 1521/1600 tokens cached, different or no key 0 in a live probe) and what the generic Edit/Delete row actions actually do.
Upgrade
Reinstall the bundle and restart DSH. Existing credentials keep working; the first boot links MUSE_CODE_SUB_TOKEN to the stored key and the row dot turns green.
v0.2.1
What changed
Follow-up to 0.2.0, from real use of the Settings > Models sign-in.
- Live model catalog. The plugin reads the account catalog (
GET https://api.meta.ai/v1/models) with the stored subscription key and declares it on themetaroute, so Muse Wonder 1.0 / Wonder Full 1.0 (+ contributor) and future chat models appear in the picker. Non-chat families (muse-image-*,muse-voice-*,sam-*) are filtered; Muse Spark rows keep the shipped catalog fidelity; a model list you edited is never overwritten. - Live sign-in status. New
GET /muse-code/statusroute; the Settings card polls it and switches from "Waiting for Meta…" to Signed in without a reload. - Card UI. The Settings > Models card is now a proper panel: title, coloured status dot, monospace device-code badge, primary/secondary actions, wrapped text. The old inline footer squeezed the button and link into vertical one-word lines.
/muse-loginnow waits for Meta's confirmation and answers with the final state instead of leaving the chat on "sign-in started".
Upgrade
Reinstall the bundle and restart DSH. The existing llm-pi-ai/meta credential keeps working; the route picks up the full model list on the first boot after upgrading.
v0.2.0
What changed
The bundle now integrates Muse Code through the meta provider that DeepSeek Harness already ships, replacing the second @deepseek-ai/dsh-llm-pi-ai instance that DSH cannot activate.
- Declares the shipped
metaroute in thellm-pi-aisettings section, so the provider appears under Settings → Models and in the model picker as Muse Code (Meta subscription). - Adds a Sign in control under Settings → Models and the
/muse-logincommand. Both run DSH's own Meta device-code flow, open the verification page in the default browser, and show the code. - Ships the Client half as a browser classic script; the previous
lib/client.jscarried an ESMexport {}from tsc that aborted the Web boot withUnexpected token 'export'. - Reads the authorization seam's neutral notice (
message/url/code), so the command no longer reports a spurious timeout. - Removes the hand-written route, the
MUSE_CODE_SUB_TOKENhandling, and themuse-wondermodel ids that DSH's catalog does not serve.
Breaking change: 0.1.x profiles and credentials are replaced. Reinstall the bundle, restart DSH, and sign in again.
Verification
CI: typecheck, build, 17 offline tests on Node 20/22/24, and markdownlint — all green.
v0.1.1: trusted publisher validation
0.1.1
No functional changes. This patch release validates the npm trusted publisher configuration for GitHub Actions.
- Model route and device-code authorization flow unchanged.
- npm package: @thestreamcode/dsh-muse-code@0.1.1.
v0.1.0: Muse Code subscription provider for DSH
0.1.0
- Adds a \muse-code\ model route to DeepSeek Harness through \dsh-llm-pi-ai\ (\openai-responses, \�pi.meta.ai/v1).
- Adds a native device-code authorization flow and stores the minted key under \MUSE_CODE_SUB_TOKEN.
- Pins the shared Muse auth contract; offline tests cover the device flow and plugin wiring.
- Includes the risk notice required by Meta's subscription terms.
Install from npm: \dsh plugin --profile desktop add @thestreamcode/dsh-muse-code
Install from GitHub: \dsh plugin --profile desktop add github:TheStreamCode/dsh-muse-code\