@theokit/sdk 2.12.0 → 2.13.1

package/CHANGELOG.md

@@ -1,5 +1,17 @@
 # Changelog
 
+## 2.13.1
+
+### Patch Changes
+
+- 65763b9: Trim leaked-dialect tool-call parameter values during recovery. Models that leak the Hermes dialect as text (qwen3-coder) emit each parameter on its own line, so the recovered value carried the formatting newlines: `<parameter=path>\npackage.json\n</parameter>` produced `{ path: "\npackage.json\n" }`. Untrimmed, `read_file` / `glob_files` / `search_text` received a path/pattern wrapped in newlines and failed `not_found` (only `shell_exec` tolerated it, since bash ignores blank lines), so a multi-read investigation loop kept re-reading, never converged, and appeared to hang. The recovery extractor now trims each parameter value (leading/trailing whitespace only — internal newlines of a legitimate multi-line command survive), matching the native `tool_calls` path where such formatting noise never occurs. Values remain strings; downstream schema coercion is unchanged.
+
+## 2.13.0
+
+### Minor Changes
+
+- 958a81f: Add per-route opt-in for leaked-dialect safe-parse (`ProviderRoute.extractToolCallsFromContent`, default off). The 2.12.0 release exposed the recovery flag only on a static `ProviderProfile`; enabling it required redeclaring a provider profile. This adds the same flag at the routing layer, so a consumer can opt a single chat route into recovery without cloning the built-in provider: `providers: { routes: [{ capability: "chat", provider: "openrouter", extractToolCallsFromContent: true }] }`. The router clones the resolved profile with the flag for that run (built-in profiles still ship the flag off), so the OpenAI-compatible transport recovers the Hermes `<function=…></tool_call>` dialect leaked as text by models like qwen3-coder. Derived from `routes[0]` (mirrors how the primary provider is derived) and applied to the resolved chat chain; fail-open and default-off, so a non-leaking route is unaffected. This is the enablement path consumed by `@theokit/agents`' `recoverLeakedToolCalls` knob.
+
 ## 2.12.0
 
 ### Minor Changes

package/dist/a2a/index.cjs

@@ -10119,7 +10119,7 @@ function parseHermesParams(inner) {
     const key = param[1];
     const value = param[2];
     if (key === void 0 || value === void 0) continue;
-    input[key.trim()] = value;
+    input[key.trim()] = value.trim();
   }
   return input;
 }
@@ -10255,6 +10255,14 @@ var init_openai2 = __esm({
       name = "openai";
       baseUrl;
       fetchImpl;
+      /**
+       * Whether this client recovers leaked Hermes tool-call dialect from assistant
+       * text (theokit#58 follow-up). Observability for the route→client wiring of
+       * `extractToolCallsFromContent`. @internal
+       */
+      get recoversLeakedToolCalls() {
+        return this.options.extractToolCallsFromContent ?? false;
+      }
       // biome-ignore lint/complexity/noExcessiveCognitiveComplexity: HTTP+SSE handshake + accumulator is intentionally one block
       async *stream(request, signal) {
         const headers = {
@@ -10840,8 +10848,9 @@ function buildChain(options) {
   return clients;
 }
 function buildClient(name, routerOptions) {
-  const profile = getProviderProfile(name);
-  if (profile === void 0) return void 0;
+  const baseProfile = getProviderProfile(name);
+  if (baseProfile === void 0) return void 0;
+  const profile = routerOptions.extractToolCallsFromContent === true && baseProfile.extractToolCallsFromContent !== true ? { ...baseProfile, extractToolCallsFromContent: true } : baseProfile;
   const ambient = currentCredentialPool(name);
   if (ambient !== void 0) {
     return new PoolAwareLlmClient(ambient, (apiKey) => selectTransport(profile, apiKey));
@@ -11270,11 +11279,13 @@ function buildLoopInputs(options, runId, userText) {
   const fallback = options.agentOptions.providers?.fallback;
   const apiKeys = options.agentOptions.providers?.apiKeys;
   const credentialPoolStrategy = options.agentOptions.providers?.credentialPoolStrategy;
+  const extractToolCallsFromContent = options.agentOptions.providers?.routes?.[0]?.extractToolCallsFromContent;
   const chain = resolveProviderChain({
     primary,
     ...fallback !== void 0 ? { fallback } : {},
     ...apiKeys !== void 0 ? { apiKeys } : {},
-    ...credentialPoolStrategy !== void 0 ? { credentialPoolStrategy } : {}
+    ...credentialPoolStrategy !== void 0 ? { credentialPoolStrategy } : {},
+    ...extractToolCallsFromContent === true ? { extractToolCallsFromContent: true } : {}
   });
   const llm = chain.length === 1 ? chain[0] : new FallbackLlmClient(chain);
   return {