opencode-muse-auth 0.5.0 → 0.5.2

package/README.md

@@ -55,8 +55,11 @@ token from the login flow is kept in memory only and is never written to disk.
   with Muse Code's builtins on the way to `api.meta.ai`, restores them in the response, and
   normalizes parameters Meta rejects (`tool_choice`, reasoning effort, output-token floor,
   encrypted-reasoning include). The adapter's `/v1` origin becomes the per-request base URL; on
-  routes that ignore that override the plugin rewrites the assembled request onto the same origin. If Meta still refuses the request, the
-  adapter retries once with every tool aliased. See [ADAPTER_CONTRACT.md](ADAPTER_CONTRACT.md).
+  routes that ignore that override the plugin rewrites the assembled request onto the same origin.
+  Routing does not depend on the credential type: an existing `meta` API key and the V2 Muse OAuth
+  connection both go through the adapter; the OAuth access token only overrides `Authorization`
+  when the V2 sign-in is active. If Meta still refuses the request, the adapter retries once with
+  every tool aliased. See [ADAPTER_CONTRACT.md](ADAPTER_CONTRACT.md).
 - V1 storage: the OpenCode auth store is the primary source, and the loader falls back to the
   legacy cache only when the store has no key.
 - V2 storage: the credential lives in the OpenCode integration store, and no local cache is
@@ -68,10 +71,9 @@ token from the login flow is kept in memory only and is never written to disk.
 
 ## Requirements
 
-- opencode with plugin support, including the v2 plugin module shape accepted by opencode 1.18.29+
-  and 2.x.
-- The loopback adapter requires the V2 plugin API (opencode 2.x). V1 installs keep authenticating
-  but still receive Meta's `client_attestation_denied` 403.
+- opencode 2.2.4 or newer for inference through the adapter (the V2 plugin module shape; 2.2.0
+  loads the plugin but does not invoke its setup). On the V1 plugin API the plugin keeps
+  authenticating but still receives Meta's `client_attestation_denied` 403.
 - Node.js 22.6 or newer for development; CI runs Node.js 22 and 24.
 - An active Muse Code subscription on the Meta account used at login.
 
@@ -125,6 +127,9 @@ collide with Muse Code's builtins. If it appears anyway, one of these is true:
   `the local request adapter could not start`, and the provider stays on the direct endpoint;
 - `MUSE_CODE_ADAPTER=off` is set, which keeps the proxy but disables the reshaping;
 - you are on the V1 plugin API, which has no adapter;
+- the plugin is older than 0.5.1 or opencode is older than 2.2.4: 0.5.0 skipped the adapter when
+  the active `meta` credential was a plain API key, and opencode 2.2.0 loads the plugin without
+  invoking its V2 setup. Check `opencode plugin list` and `opencode --version`, then update;
 - Meta changed the gate, for example to a real per-client signature. Nothing in this plugin can
   forge one.
 

package/dist/index.js

@@ -131,23 +131,23 @@ export async function setupV2(ctx, options = {}) {
         return credential;
     }
     if (adapter) {
-        // Primary mechanism: the provider uses the adapter's /v1 origin as its
-        // request base URL. Native provider drivers honor this override.
+        // Every Meta inference request must reach the adapter: it reshapes the tool
+        // declarations the gate inspects, so the credential type does not matter
+        // (V1 API key or V2 OAuth). Native provider drivers honor this override.
         const baseUrl = adapter.baseUrl;
         await ctx.session.hook("model.request", async (event) => {
-            if (await subscription())
-                event.baseURL = baseUrl;
+            event.baseURL = baseUrl;
         }, { providerID: "meta" });
     }
-    // Meta's native provider expects a bearer inference key, not the
-    // short-lived OAuth token used to mint it. Honor the active connection.
-    // AI SDK routes drop model.request.baseURL (opencode#55984), so this hook
-    // also rewrites the assembled request onto the adapter origin.
+    // Meta's native provider expects a bearer inference key, not the short-lived
+    // OAuth token used to mint it: when the active Muse connection resolves one,
+    // put it on the request. AI SDK routes drop model.request.baseURL
+    // (opencode#55984), so this hook also rewrites the assembled request onto the
+    // adapter origin.
     await ctx.session.hook("http.request", async (event) => {
         const credential = await subscription();
-        if (!credential)
-            return;
-        event.request.headers.set("Authorization", `Bearer ${credential.access}`);
+        if (credential)
+            event.request.headers.set("Authorization", `Bearer ${credential.access}`);
         if (adapter)
             event.request = routeThroughAdapter(event.request, adapter.baseUrl);
     }, { providerID: "meta" });

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "opencode-muse-auth",
-  "version": "0.5.0",
+  "version": "0.5.2",
   "description": "Unofficial and experimental: Muse Spark in opencode using a Muse Code subscription credential, with a local loopback adapter for Meta's subscription wire format. May conflict with Meta's terms; use at your own risk. See DISCLAIMER.md.",
   "main": "./dist/index.js",
   "types": "./dist/index.d.ts",