[▲ Vercel Community](/) · [Categories](/categories) · [Latest](/latest) · [Top](/top) · [Live](/live) [AI SDK](/c/ai-sdk/62) # Unable to access AI SDK devtools 68 views · 0 likes · 8 posts Alex Turpin (@alexturpin) · 2026-02-09 Trying to check out AI SDK devtools; I have my middleware wrapper setup, and am running \`npx @ai-sdk/devtools\`. Reports the following > 🔍 AI SDK DevTools API running on port 4983 > Open http://localhost:5173 for the dev UI However, my browser is unable to connect to 5173. ERR_CONNECTION_REFUSED as if there isn’t a server running on that part. 4983 however does show a page saying this is for the API only and sends me to 5173. Is there another server that needs to be running and listening on 5173 to serve the UI interface? Is this meant to be like Drizzle Studio with a proprietary UI served on a Vercel domain and this isn’t setup yet? ```javascript “ai”: “^6.0.78”, “@ai-sdk/devtools”: “^0.0.11”, ``` Pauline P. Narvas (@pawlean) · 2026-02-09 Hey Alex! I think there's a confusion with the ports here. According to the AI SDK documentation, the devtools UI is actually served on port 4983, not 5173. When you run `npx <@ai> -sdk/devtools`, try accessing http://localhost:4983 directly in your browser. That's where both the API and the UI viewer are served. The message saying ```Open http://localhost:5173 for the dev UI``` appears to be incorrect. The devtools runs everything on a single port (4983 by default). Let me know if accessing http://localhost:4983 works for you! https://ai-sdk.dev/docs/ai-sdk-core/devtools Alex Turpin (@alexturpin) · 2026-02-10 This is what I see at 4983:  The link takes me to 5173 which doesn’t seem to exist as you pointed out. Alex Turpin (@alexturpin) · 2026-02-10 I dug into the code a bit. Seems this is a special mode I’m hitting that’s meant to be used to develop ai-devtools itself. The cause is this check which looks for \`src\` in the calling path; all of my repos are checked out under \`\~/src\` on my laptop so I inadvertently get into that condition. https://github.com/vercel/ai/blob/c36a873ce00892a4c587c2e9492220b392aefd09/packages/devtools/src/viewer/server.ts#L242 I Nico Albanese (@nicoalbanese) · 2026-02-10 [quote="alexturpin, post:6, topic:33308"] dug into the code a bit. Seems this is a special mode I’m hitting that’s meant to be used to develop ai-devtools itself. The cause is this check which looks for `src` in the calling path; all of my repos are checked out under `~/src` on my laptop so I inadvertently get into that condition. https://github.com/vercel/ai/blob/c36a873ce00892a4c587c2e9492220b392aefd09/packages/devtools/src/viewer/server.ts#L242 I [/quote] Thanks - put up a fix! https://github.com/vercel/ai/pull/12394 Jesusvalle1 (@jesusvalle1) · 2026-02-16 Hi @nicoalbanese! Thanks for the fix regarding the /src/ path detection. However, I’ve noticed this creates a new conflict for users working with Monorepos (like NX or Turborepo). In these environments, it is very common to have both /src/ and /dist/ folders existing simultaneously within the workspace or even within the same application path (e.g., apps/my-app/src and apps/my-app/dist). Since the current logic relies on the absence of /dist/ to enable dev mode, the DevTools become inaccessible in these projects as soon as a build is generated or if the monorepo manager creates a distribution folder at the root. Perhaps a more robust approach would be to check for an environment variable or a specific flag, rather than relying solely on string patterns in the file path, to avoid these false positives in complex project structures. Is there a recommended way to force-enable DevTools in these cases? Jesusvalle1 (@jesusvalle1) · 2026-02-19 Hi @nicoalbanese, hope you’re doing well! Just wanted to follow up on the message below in case it slipped through. I’m still running into this issue in monorepo setups and wanted to check if there’s a recommended workaround or if this is something that might be addressed going forward. Thanks again for taking a look. Best, Jesús. Nico Albanese (@nicoalbanese) · 2026-03-04 hey! can you try again - i put through a change last week that should fix!
