[GH-ISSUE #13] TypeError: Could not convert argument of type symbol to string. #4

Closed
opened 2026-02-16 08:17:10 -05:00 by yindo · 8 comments
Owner

Originally created by @jiarongkoh on GitHub (Mar 17, 2025).
Original GitHub issue: https://github.com/langchain-ai/create-agent-chat-app/issues/13

I was getting started with this repo and I was thrown the following error when i ran npm run dev.

Steps to reproduce:

  1. Clone the repo - ie npx create-agent-chat-app@latest
  2. I selected just "ReAct agent"
  3. Added my Tavily and Anthropic API keys
  4. Ran npm run dev

Message/error:

[1] agents:dev: info:    ▪ Starting server...
[1] agents:dev: info:    ▪ Initializing storage...
[1] agents:dev: info:    ▪ Registering graphs from /Users/me/Desktop/Python Projects/agent-chat/agent-chat-app
[1] agents:dev: info:    ┏ Registering graph with id 'agent'
[1] agents:dev: info:    ┗ [1] { graph_id: 'agent' }
[1] agents:dev: info:    ▪ Starting 10 workers
[1] agents:dev: info:    ▪ Server running at ::1:2025
[0] web:dev:  ✓ Ready in 1701ms
[1] agents:dev: info:    ▪ <-- GET /info
[1] agents:dev: info:    ▪ --> GET /info 200 1ms
[1] agents:dev: info:    ▪ <-- POST /assistants/search
[1] agents:dev: info:    ▪ --> POST /assistants/search 200 2ms
[1] agents:dev: info:    ▪ <-- GET /assistants/123/graph?xray=true
[1] agents:dev: info:    ▪ --> GET /assistants/123/graph?xray=true 200 2ms
[1] agents:dev: info:    ▪ <-- GET /assistants/123/subgraphs?recurse=true
[1] agents:dev: info:    ▪ <-- GET /assistants/123/schemas
[1] agents:dev: info:    ▪ <-- POST /threads/search
[1] agents:dev: TypeError: Could not convert argument of type symbol to string.
[1] agents:dev:     at webidl.converters.DOMString (node:internal/deps/undici/undici:1940:15)
[1] agents:dev:     at webidl.converters.ByteString (node:internal/deps/undici/undici:1945:35)
[1] agents:dev:     at Object.record<ByteString, ByteString> (node:internal/deps/undici/undici:1857:30)
[1] agents:dev:     at webidl.converters.HeadersInit (node:internal/deps/undici/undici:3397:67)
[1] agents:dev:     at Object.ResponseInit (node:internal/deps/undici/undici:1914:21)
[1] agents:dev:     at new Response (node:internal/deps/undici/undici:4398:34)
[1] agents:dev:     at [getResponseCache] (file:///Users/me/.npm/_npx/f7d2da157c771680/node_modules/@hono/node-server/dist/index.mjs:214:36)
[1] agents:dev:     at _Response.get (file:///Users/me/.npm/_npx/f7d2da157c771680/node_modules/@hono/node-server/dist/index.mjs:254:36)
[1] agents:dev:     at set res [as res] (file:///Users/me/.npm/_npx/f7d2da157c771680/node_modules/hono/dist/context.js:76:18)
[1] agents:dev:     at dispatch (file:///Users/me/.npm/_npx/f7d2da157c771680/node_modules/hono/dist/compose.js:38:21)
Originally created by @jiarongkoh on GitHub (Mar 17, 2025). Original GitHub issue: https://github.com/langchain-ai/create-agent-chat-app/issues/13 I was getting started with this repo and I was thrown the following error when i ran `npm run dev`. Steps to reproduce: 1. Clone the repo - ie npx create-agent-chat-app@latest 2. I selected just "ReAct agent" 3. Added my Tavily and Anthropic API keys 4. Ran `npm run dev` Message/error: ``` [1] agents:dev: info: ▪ Starting server... [1] agents:dev: info: ▪ Initializing storage... [1] agents:dev: info: ▪ Registering graphs from /Users/me/Desktop/Python Projects/agent-chat/agent-chat-app [1] agents:dev: info: ┏ Registering graph with id 'agent' [1] agents:dev: info: ┗ [1] { graph_id: 'agent' } [1] agents:dev: info: ▪ Starting 10 workers [1] agents:dev: info: ▪ Server running at ::1:2025 [0] web:dev: ✓ Ready in 1701ms [1] agents:dev: info: ▪ <-- GET /info [1] agents:dev: info: ▪ --> GET /info 200 1ms [1] agents:dev: info: ▪ <-- POST /assistants/search [1] agents:dev: info: ▪ --> POST /assistants/search 200 2ms [1] agents:dev: info: ▪ <-- GET /assistants/123/graph?xray=true [1] agents:dev: info: ▪ --> GET /assistants/123/graph?xray=true 200 2ms [1] agents:dev: info: ▪ <-- GET /assistants/123/subgraphs?recurse=true [1] agents:dev: info: ▪ <-- GET /assistants/123/schemas [1] agents:dev: info: ▪ <-- POST /threads/search [1] agents:dev: TypeError: Could not convert argument of type symbol to string. [1] agents:dev: at webidl.converters.DOMString (node:internal/deps/undici/undici:1940:15) [1] agents:dev: at webidl.converters.ByteString (node:internal/deps/undici/undici:1945:35) [1] agents:dev: at Object.record<ByteString, ByteString> (node:internal/deps/undici/undici:1857:30) [1] agents:dev: at webidl.converters.HeadersInit (node:internal/deps/undici/undici:3397:67) [1] agents:dev: at Object.ResponseInit (node:internal/deps/undici/undici:1914:21) [1] agents:dev: at new Response (node:internal/deps/undici/undici:4398:34) [1] agents:dev: at [getResponseCache] (file:///Users/me/.npm/_npx/f7d2da157c771680/node_modules/@hono/node-server/dist/index.mjs:214:36) [1] agents:dev: at _Response.get (file:///Users/me/.npm/_npx/f7d2da157c771680/node_modules/@hono/node-server/dist/index.mjs:254:36) [1] agents:dev: at set res [as res] (file:///Users/me/.npm/_npx/f7d2da157c771680/node_modules/hono/dist/context.js:76:18) [1] agents:dev: at dispatch (file:///Users/me/.npm/_npx/f7d2da157c771680/node_modules/hono/dist/compose.js:38:21) ```
yindo closed this issue 2026-02-16 08:17:10 -05:00
Author
Owner

@bracesproul commented on GitHub (Mar 17, 2025):

@jiarongkoh did this occur after making a request, or just from starting the server?

Also are you running on Windows/Mac/Linux?

@bracesproul commented on GitHub (Mar 17, 2025): @jiarongkoh did this occur after making a request, or just from starting the server? Also are you running on Windows/Mac/Linux?
Author
Owner

@bracesproul commented on GitHub (Mar 17, 2025):

I just ran a test (see trace here) and it worked without throwing that error (running on MacOS)

If you could provide more details that would be great. Thanks

@bracesproul commented on GitHub (Mar 17, 2025): I just ran a test ([see trace here](https://smith.langchain.com/public/c93b7b31-4e7e-44db-a326-967186e7c3f7/r)) and it worked without throwing that error (running on MacOS) If you could provide more details that would be great. Thanks
Author
Owner

@jiarongkoh commented on GitHub (Mar 18, 2025):

@bracesproul it happened after starting the server, and when Langsmith is opened automatically.

I'm running MacOS Sonoma 14.7, M2 chip

@jiarongkoh commented on GitHub (Mar 18, 2025): @bracesproul it happened after starting the server, and when Langsmith is opened automatically. I'm running MacOS Sonoma 14.7, M2 chip
Author
Owner

@ibbybuilds commented on GitHub (Mar 26, 2025):

@jiarongkoh Did you find any solution I am facing similar issue on windows.

@bracesproul Any update?

@ibbybuilds commented on GitHub (Mar 26, 2025): @jiarongkoh Did you find any solution I am facing similar issue on windows. @bracesproul Any update?
Author
Owner

@bracesproul commented on GitHub (Mar 26, 2025):

@jiarongkoh @mibrahim2001 I believe this is due to the node version you're running. if you switch to 20.9.0 does it still happen?

@bracesproul commented on GitHub (Mar 26, 2025): @jiarongkoh @mibrahim2001 I believe this is due to the node version you're running. if you switch to `20.9.0` does it still happen?
Author
Owner

@ibbybuilds commented on GitHub (Mar 26, 2025):

@bracesproul I am currently on v20.15.1, am I supposed to downgrade it? Shouldn't the thing (that is causing this error) be patched in the version that is greater than 20.9.0?

@ibbybuilds commented on GitHub (Mar 26, 2025): @bracesproul I am currently on `v20.15.1`, am I supposed to downgrade it? Shouldn't the thing (that is causing this error) be patched in the version that is greater than `20.9.0`?
Author
Owner

@ibbybuilds commented on GitHub (Mar 26, 2025):

It works all fine when using node version 20.9.0, thank you @bracesproul. Can you share more details on what causes the error in the later versions?

@ibbybuilds commented on GitHub (Mar 26, 2025): It works all fine when using node version `20.9.0`, thank you @bracesproul. Can you share more details on what causes the error in the later versions?
Author
Owner

@bracesproul commented on GitHub (Apr 1, 2025):

@mibrahim2001 not exactly sure what the issue is. some node versions are simply not supported by our API at this time.

@bracesproul commented on GitHub (Apr 1, 2025): @mibrahim2001 not exactly sure what the issue is. some node versions are simply not supported by our API at this time.
yindo changed title from TypeError: Could not convert argument of type symbol to string. to [GH-ISSUE #13] TypeError: Could not convert argument of type symbol to string. 2026-06-05 17:18:22 -04:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: langchain-ai/create-agent-chat-app#4