Hacktoberfest 2026 : les issues que les mainteneurs ont marquées pour octobre, ouvertes et accessibles aux débutants. Parcourir les issues Hacktoberfest

bug: agent stops responding after multiple concurrent tabs

Ouverte
  • Quelque chose ne va pas ?
#63 0 commentaires 0 réactions 0 personnes assignées Voir sur GitHub

Les mainteneurs répondent en général sous 1 jour

Personne n'a encore pris cette issue.

Évaluation

Difficulté
4/5
Temps estimé
3-5 jours
Accessibilité débutants
35/100
Type d'issue
Bug
Clarté
À clarifier
Activité
Calme
Stack technique
python, typescript
Domaine
api, backend, frontend

Piste de recherche

Start with the deployed reproduction using three browser tabs, then inspect main.py, especially BoundedMemorySaver(max_threads=200) and the streaming request path. Check whether concurrent sessions, connection limits, rate limits, or unsurfaced backend errors explain the hang; done means independent tabs receive responses, and resource failures show an error instead of waiting silently.

Rédigé par le modèle d'indexation à partir du texte de l'issue.

Description

Bug

The agent stops responding when multiple browser tabs are open against the deployed app. On the third tab, the agent hangs after the user sends a message — no response, no streaming indicator, no error.

Steps to reproduce

  1. Open the deployed app in tab 1, send a message (e.g. "visualize a musical chart") — works fine
  2. Open tab 2, send a message — works fine
  3. Open tab 3, send a message (e.g. "I want to understand the difference between BFS and DFS...") — agent never responds

The UI shows the user messages and suggestion chips ("Try these Prompts") but no assistant response arrives. No loading indicator, no error state.

Screenshot

![Production screenshot showing 3 messages sent with no agent response](screenshot attached in issue)

The chat shows:

  • "visualize a musical chart"
  • "Create a 3D animation of a sphere turning into an icosahedron..."
  • "I want to understand the difference between BFS and DFS. Create an interactive comparison on a node graph."

None received a response. Suggestion chips are visible but the agent is unresponsive.

Possible causes

  1. Thread/session exhaustion — The agent uses BoundedMemorySaver(max_threads=200) in main.py. Multiple tabs may be creating separate threads that exhaust the pool or hit a concurrency limit.
  2. WebSocket/SSE connection limit — The browser or server may be hitting a connection limit for streaming responses.
  3. LangGraph checkpoint contention — Multiple concurrent sessions writing to the in-memory checkpointer could cause deadlocks.
  4. OpenAI API rate limiting — Multiple concurrent requests to GPT-5.4 could hit rate limits with no visible error surfaced to the user.
  5. Missing error handling — The frontend may not surface backend errors, making it look like the agent is "thinking" forever.

Expected behavior

Each tab should operate as an independent session. If a resource limit is reached, the user should see an error message rather than silent failure.

Environment

  • Deployed on Render
  • Agent: LangGraph + CopilotKit middleware
  • Model: GPT-5.4 via langchain_openai
  • Checkpointer: BoundedMemorySaver(max_threads=200)
Langage dominant
TypeScript
Étoiles
3.9k
Forks
414
Merge moyen
4 h
PR mergées (30 j)
6

Préparer son environnement

Par où commencer

  1. Lisez l'issue en entier, puis le guide de contribution du projet.
  2. Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
  3. Forkez le dépôt et travaillez sur une branche.
  4. Ouvrez une pull request qui référence le numéro de l'issue.

Autres issues de CopilotKit/OpenIntelligentUI

Toutes les issues de CopilotKit/OpenIntelligentUI

Issues similaires

Plus d'issues TypeScript

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.