@magpie-community/opencode-zen-free-auth 0.1.9 → 0.1.11

package/README.md

@@ -19,6 +19,12 @@ magpie plugin login opencode-zen-free
 ## Sign in
 
 Enter `public` in the key field. No personal API key is needed.
+
+Whatever is typed in the key field, the plugin signs in with the one
+shared `public` credential: a key made under your own OpenCode account
+does nothing here, and several of them don't make several accounts. Your
+own Zen keys go in magpie's built-in OpenCode Zen provider (or OpenCode's
+`opencode` provider), which takes several keys.
 The credential is kept in OpenCode's `auth.json` or magpie's
 `plugin-auth.json`.
 
@@ -50,15 +56,18 @@ The agent's tools are preserved. Zen's models often call OpenCode's own
 tool names; such a call is given the agent's tool whose name differs only
 in case (`bash` to `Bash`), or else only in case and `_`/`-` (`todowrite`
 to `todo_write`, `webfetch` to `web_fetch`), when exactly one does. A
-call with no such tool (or with no name) is left out of the reply, and
-the reply's text says which name was left out; a turn whose every call
-was left out ends as an ordinary answer. Tools run in the agent.
+call of a tool the agent has no spelling of (`psh` beside `pwsh`, `bedit`)
+reaches the agent as the model called it, as with any other provider: the
+agent answers it with its own unknown-tool error, and the model corrects
+the name and goes on. Only a call with no name is left out, and the
+reply's text says so; a turn whose every call was left out ends as an
+ordinary answer. Tools run in the agent.
 
 Zen's free tier only answers a request that carries tools, so a request
 is sent with the five core OpenCode tools the agent doesn't declare
 itself (`bash`, `edit`, `glob`, `grep`, `read`), described as not
-available. A call of one of them the agent doesn't have is left out like
-any other.
+available. A call of one of them the agent doesn't have reaches the agent
+like any other.
 
 Now and then Zen closes a streamed Chat Completions reply before its
 `[DONE]`. When the reply has said something and no tool call of it is

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@magpie-community/opencode-zen-free-auth",
-  "version": "0.1.9",
+  "version": "0.1.11",
   "description": "OpenCode Zen free models through the public credential, with native streaming protocols",
   "type": "module",
   "main": "./index.mjs",

package/provider.mjs

@@ -257,7 +257,7 @@ async function server(_input, options = {}) {
       methods: [
         {
           type: "api",
-          label: "Zen 免费访问（密钥填写 public）",
+          label: "Zen 免费访问（密钥填 public；自己的 OpenCode Key 请加到内置的 OpenCode Zen）",
           placeholder: "public",
           async authorize() {
             return { type: "success", key: "public" };

package/tool-response.mjs

@@ -48,8 +48,13 @@ function foldsTo(declared, key) {
   return folded;
 }
 
-// nameGuard answers the agent's name for a call, or null for a call of no
-// tool the agent has (a missing name included).
+// nameGuard answers the agent's name for a call: the agent's spelling when
+// one folds to it, else the name as the model wrote it. A call of a tool
+// the agent doesn't have (bedit, psh, mcp__netcatcatty__unused) goes to the
+// agent as called, like any other provider's: the agent answers it with
+// its own unknown-tool error, and the model corrects the name and goes on
+// (#209). Leaving it out ended an agent's turn as a plain answer. Only a
+// call with no name answers null, and is left out.
 function nameGuard(policy) {
   const declared = new Set(policy.declared);
   const lower = (name) => name.toLowerCase();
@@ -61,16 +66,15 @@ function nameGuard(policy) {
     if (declared.has(name)) return name;
     const match =
       byCase.get(lower(name)) ?? (byCase.has(lower(name)) ? null : byShape.get(bare(name)));
-    return match || null;
+    return match || name;
   };
 }
 
-// The models also call tools no agent has: bedit, bcp, ash, a mangled
-// mcp__netcatcatty__unused (#76). Such a call can't be run or named onto
-// one the agent has, and failing the reply for it threw away the whole
-// turn. It is left out instead, and the reply says so in its text, where
-// the agent's user and the model's next turn both read it. A reply left
-// with no call ends as a plain stop.
+// A call with no name can't be answered by any agent, and failing the
+// reply for it threw away the whole turn (#76). It is left out instead,
+// and the reply says so in its text, where the agent's user and the
+// model's next turn both read it. A reply left with no call ends as a
+// plain stop.
 export function droppedNote(name) {
   return typeof name === "string" && name
     ? `(The model called a tool this agent doesn't have: ${JSON.stringify(name.slice(0, 128))}. The call was left out.)`