[Question] Thread History when using API Passthrough #119

Activity

1. bracesproul commented on Apr 28, 2025

   

   Brace Sproul (bracesproul)

   on Apr 28, 2025

   Member

   More actions

   Hi, I noticed after setting up my env variables to test the API Passthrough, my Thread History in sidebar is now empty and appears to stay empty. Is this expected?

   Austin Welch (@austinmw) are you seeing any errors?
2. yasinahmadpoor commented on Jun 9, 2025

   

   yasin ahmadpoor (yasinahmadpoor)

   on Jun 9, 2025

   More actions

   I have same problem
3. eliasbiondo commented on Jun 9, 2025

   

   Elias Biondo (eliasbiondo)

   on Jun 9, 2025

   More actions

   Same problem here. I'll try to fix it.

   👍React with 👍1Reacted by privetin
4. eliasbiondo commented on Jun 9, 2025

   

   Elias Biondo (eliasbiondo)

   on Jun 9, 2025

   More actions

   The current implementation of ThreadProvider uses useQueryState to retrieve apiUrl and assistantId:

   const [apiUrl] = useQueryState("apiUrl");
   const [assistantId] = useQueryState("assistantId");

   This approach breaks when using environment variables to configure the API, as the parameters are no longer included in the URL.

   Solution

   Replace useQueryState with direct access to environment variables:

   const apiUrl = process.env.NEXT_PUBLIC_API_URL;
   const assistantId = process.env.NEXT_PUBLIC_ASSISTANT_ID;

   Brace Sproul (@bracesproul) yasin ahmadpoor (@yasinahmadpoor) chatrtham Austin Welch (@austinmw)

   👍React with 👍2Reacted by privetin and Balázs E. Pataki
5. beepsoft commented on Aug 4, 2025

   

   Balázs E. Pataki (beepsoft)

   on Aug 4, 2025

   Last edited by beepsoft

   More actions

   Solution

   Replace useQueryState with direct access to environment variables:

   const apiUrl = process.env.NEXT_PUBLIC_API_URL;
   const assistantId = process.env.NEXT_PUBLIC_ASSISTANT_ID;
   @bracesproul @yasinahmadpoor @chatrtham @austinmw

   Or the workaround until it gets fixed is to add the apiUrl and assistantId to the URL by hand

   http://localhost:3000/?apiUrl=http://localhost:2024&assistantId=agent

   Elias Biondo (@eliasbiondo), can you maybe submit a PR with your fix?
6. muralidhar-challa commented on Sep 12, 2025

   

   Muralidhar Reddy Challa (muralidhar-challa)

   on Sep 12, 2025

   More actions

   Root Cause Found & Fix Available

   I've identified the root cause of this issue and have a working fix.

   Problem: The ThreadProvider in src/providers/Thread.tsx doesn't fall back to environment variables like the StreamProvider does.

   • StreamProvider correctly uses: useQueryState("apiUrl", { defaultValue: envApiUrl || "" })
   • ThreadProvider only uses: useQueryState("apiUrl") (no fallback)

   This causes thread history to only work with query parameters, not environment variables.

   Fix: Make ThreadProvider consistent with StreamProvider by adding environment variable fallbacks.

   Impact: This affects anyone using environment variables, including API Passthrough users, Docker deployments, and production setups.

   I'll submit a PR with the fix shortly.

   👍React with 👍1Reacted by YU-LAN WANG
7. Muralidhar Reddy Challa (muralidhar-challa)

   added a commit that references this issue on Sep 12, 2025

   fix: add environment variable fallback to ThreadProvider

   ...

   This issue will close once commit ee68192 is merged into the 'main' branch.

   ee68192