@juspay/neurolink 12.17.0 → 12.17.1

package/dist/providers/anthropic/client.js

@@ -34,7 +34,7 @@ import { transformToolExecutions } from "../../utils/transformationUtils.js";
 import { createAnthropicConfig, getProviderModel, validateApiKey, } from "../../utils/providerConfig.js";
 import { composeAbortSignals, composeAbortSignalsScoped, createTimeoutController, mergeAbortSignals, TimeoutError, } from "../../utils/timeout.js";
 import { raceWithAbort } from "../../utils/async/index.js";
-import { resolveToolChoice } from "../../utils/toolChoice.js";
+import { normalizeResolvedToolChoice, resolveToolChoice, } from "../../utils/toolChoice.js";
 import { emitToolEndFromStepFinish } from "../../utils/toolEndEmitter.js";
 import { NoOutputGeneratedError } from "../../utils/generationErrors.js";
 import { buildNoOutputSentinel, stampNoOutputSpan, } from "../../utils/noOutputSentinel.js";
@@ -1074,10 +1074,20 @@ export class AnthropicProvider extends BaseProvider {
                 if (tools && tools.length === 0) {
                     tools = undefined;
                 }
-                let toolChoice = options.toolChoice
-                    ? toolChoiceToAnthropic(options.toolChoice.type === "tool"
-                        ? { type: "tool", toolName: options.toolChoice.toolName }
-                        : options.toolChoice.type)
+                // The value here has already been through `resolveToolChoice`
+                // upstream in `executeNativeGenerate`, so this layer translates
+                // rather than re-resolves — re-resolving would apply the auto/none
+                // defaulting twice, and `toolsRecord`/`shouldUseTools` are not in
+                // scope inside `getAISDKModel` in any case.
+                //
+                // Only the SHAPE varies, and reading `.type` off it was the bug:
+                // a bare `"required"` has no `.type`, so the translator received
+                // `undefined` and the field was dropped from the request entirely.
+                // Normalisation now lives in the shared util rather than being
+                // re-derived here, so this site cannot drift from its siblings again.
+                const normalisedToolChoice = normalizeResolvedToolChoice(options.toolChoice);
+                let toolChoice = normalisedToolChoice
+                    ? toolChoiceToAnthropic(normalisedToolChoice)
                     : undefined;
                 // JSON/structured output: Anthropic has no response_format — emulate
                 // with a forced synthetic tool whose input IS the JSON payload (the

package/dist/utils/toolChoice.d.ts

@@ -2,3 +2,22 @@ import type { Tool, ToolChoice } from "../types/index.js";
 export declare function resolveToolChoice(options: {
     toolChoice?: ToolChoice<Record<string, Tool>>;
 }, tools: Record<string, Tool> | undefined, shouldUseTools: boolean): ToolChoice<Record<string, Tool>> | "none";
+/**
+ * Normalise an already-resolved tool choice into the shape
+ * `toolChoiceToAnthropic` (and its peers) accept.
+ *
+ * A provider's model handle sees a value that has *already* been through
+ * `resolveToolChoice` upstream, so it must translate rather than re-resolve —
+ * re-resolving there would apply the `auto`/`none` defaulting twice, and the
+ * `tools`/`shouldUseTools` inputs it needs are not in scope at that layer
+ * anyway.
+ *
+ * What does vary is the shape. The value arrives either as a bare string
+ * (`"auto"` / `"none"` / `"required"`), as `{ type: "tool", toolName }`, or —
+ * on the native loop's tool-free re-ask — as an injected `{ type: "none" }`
+ * object. Reading `.type` off the string forms yields `undefined`, which is
+ * how string choices were silently dropped from the Anthropic generate
+ * request. This exists so that normalisation lives in one place instead of
+ * being re-derived at each call site.
+ */
+export declare function normalizeResolvedToolChoice(value: unknown): ToolChoice<Record<string, Tool>> | undefined;

package/dist/utils/toolChoice.js

@@ -4,3 +4,42 @@ export function resolveToolChoice(options, tools, shouldUseTools) {
     }
     return options.toolChoice ?? "auto";
 }
+/**
+ * Normalise an already-resolved tool choice into the shape
+ * `toolChoiceToAnthropic` (and its peers) accept.
+ *
+ * A provider's model handle sees a value that has *already* been through
+ * `resolveToolChoice` upstream, so it must translate rather than re-resolve —
+ * re-resolving there would apply the `auto`/`none` defaulting twice, and the
+ * `tools`/`shouldUseTools` inputs it needs are not in scope at that layer
+ * anyway.
+ *
+ * What does vary is the shape. The value arrives either as a bare string
+ * (`"auto"` / `"none"` / `"required"`), as `{ type: "tool", toolName }`, or —
+ * on the native loop's tool-free re-ask — as an injected `{ type: "none" }`
+ * object. Reading `.type` off the string forms yields `undefined`, which is
+ * how string choices were silently dropped from the Anthropic generate
+ * request. This exists so that normalisation lives in one place instead of
+ * being re-derived at each call site.
+ */
+export function normalizeResolvedToolChoice(value) {
+    if (typeof value === "string") {
+        return value;
+    }
+    if (value && typeof value === "object") {
+        const candidate = value;
+        if (candidate.type === "tool") {
+            // A tool choice that names no tool cannot be honoured. Fall through to
+            // the provider default rather than emitting the bare string "tool",
+            // which is not one of the valid auto/none/required forms and would be
+            // rejected downstream.
+            return candidate.toolName
+                ? { type: "tool", toolName: candidate.toolName }
+                : undefined;
+        }
+        if (candidate.type) {
+            return candidate.type;
+        }
+    }
+    return undefined;
+}

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@juspay/neurolink",
-  "version": "12.17.0",
+  "version": "12.17.1",
   "packageManager": "pnpm@10.15.1",
   "description": "TypeScript AI SDK with 24+ LLM providers behind one consistent API. MCP-native (connect any MCP server), voice TTS/STT/realtime, RAG, agents, memory, context compaction. OpenAI · Anthropic · Gemini · Bedrock · Azure · Ollama · DeepSeek · NVIDIA NIM and more.",
   "author": {
@@ -117,6 +117,7 @@
     "test:thinking-config": "pnpm exec tsx test/continuous-test-suite-sdk-thinking-config.ts",
     "test:gemini-thinking-level": "pnpm exec tsx test/continuous-test-suite-gemini-thinking-level.ts",
     "test:gemini-thinking-level-ai-studio": "pnpm exec tsx test/continuous-test-suite-gemini-thinking-level-ai-studio.ts",
+    "test:anthropic-toolchoice": "pnpm exec tsx test/continuous-test-suite-anthropic-toolchoice.ts",
     "test:mcp:spans": "pnpm exec tsx test/continuous-test-suite-mcp-spans.ts",
     "test:mcp:infra": "pnpm exec tsx test/continuous-test-suite-mcp-infra.ts",
     "test:vendor-recovery": "pnpm exec tsx test/continuous-test-suite-native-vendor-recovery.ts",