René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"ERROR api.chat DataStream onError triggered: TypeError: Cannot read properties of undefined (reading 'typeName')","articleBody":"### What happened?\n\nwhile rendering response, browser reports error \nError Details: Custom error: Cannot read properties of undefined (reading 'typeName')\n\n### How to reproduce\n\n1. http://localhost:5173/chat/1\n2. enter a request/prompt\n3. wait for response... interupted by reported error\n\n### Environment\n\nchrome\nwindows\nollama: local http://127.0.0.1:11434/\nversion 1.2.3\n\n### Extra info\n\naccording to copilot there's an error with the following\n\nThe error is in zod-to-json-schema when it tries to parse tool definitions. The issue is that one of the tool schemas passed to [streamText](vscode-file://vscode-app/c:/Users/antho/AppData/Local/Programs/Microsoft%20VS%20Code/resources/app/out/vs/code/electron-browser/workbench/workbench.html) is invalid or not a proper Zod schema.\n\nThe error happens in prepareToolsAndToolChoice when the AI SDK tries to convert tool schemas. Let me check how tools are being provided to streamText:\n\nThe issue is on line 224: [const builtInTools = builtInToolService.toolsWithoutExecute;]\n\nThe problem is that [toolsWithoutExecute] is returning tool objects that don't have valid Zod schemas. Let me check the BuiltInToolService to see the tool definitions:\n\nThe JSON has valid parameter schemas. But the issue is that when these are loaded, they're just plain JSON objects, not Zod schemas. The AI SDK expects Zod schemas, not plain JSON schemas.\n\nThe fix is to not pass tools if they don't have valid Zod schemas, or to validate them first. Let me add a check:\n\nThe issue was that the built-in tools defined in the JSON file have JSON schemas (not Zod schemas), and when the AI SDK tries to convert them to JSON schema for tool validation, it fails because the structure isn't compatible.\n\nThe fix disables the built-in tools that are loaded from JSON since they're not proper Zod schemas. The actual tool execution is still handled through the [processToolInvocations] method on the server side, so functionality isn't lost.\n\n_stream-text.ts_\n  if (Object.keys(builtInTools).length \u003e 0) {\n\nremove... allTools ={ ...allTools, ...builtInTools };\nremove... logger.info(`Added ${Object.keys(...\n\nadd...    logger.info(`Filtering built-in tools - checking for valid schemas`);\nadd...    const validBuiltInTools: Record\u003cstring, any\u003e = {};\nadd...    \nadd...    for (const [toolName, toolDef] of Object.entries(builtInTools)) {\nadd...      // Only include tools that have proper definitions (not just JSON schemas)\nadd...      // Built-in tools from JSON don't have Zod validation, so we skip them for now\nadd...      // and rely on MCP and server-side tool processing instead\nadd...      logger.debug(`Skipping built-in tool ${toolName} - JSON schemas not compatible with AI SDK tool format`);\nadd...    }\nadd...    \nadd...    if (Object.keys(validBuiltInTools).length \u003e 0) {\nadd...      allTools = { ...allTools, ...validBuiltInTools };\nadd...      logger.info(`Added ${Object.keys(validBuiltInTools).length} valid built-in tools`);\nadd...    } else {\nadd...      logger.info(`No valid built-in tools with proper schemas found for this model`);\nadd...    }\nadd...  }","author":{"url":"https://github.com/ambbone","@type":"Person","name":"ambbone"},"datePublished":"2026-01-15T22:11:31.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":8},"url":"https://github.com/69/codinit-dev/issues/69"}