Skip to content

New conversation from a Dot's home screen hangs on "Connecting to your conversation…" #59

Open

Description

@raoofaltaher

Sending the first message from a Dot's home composer creates the thread (it appears in Recent Chats), but the view stays on "Connecting to your conversation…" and the message is not shown. The run continues in the background; clicking the thread in Recent Chats attaches the live view.

How we hit it: reproduced 2/2 on two different Dots. Starting a page conversation from a page's chat box recovered on its own.

Env: Docker Compose (compose.yml + computers overlays), main @ c2569bb, OPENAI_MODEL=gpt-5.4-mini, Chromium.

Activity

  1. NathanTarbert commented on Oct 7, 2026

    @NathanTarbert
    Collaborator

    Thanks @raoofaltaher for writing this up so clearly, and for all the other reports in this batch. Most of them are fixed on main now.

    We tried to reproduce this one and couldn't. Each time, starting a first conversation from a Dot's home screen connected straight away, showed the message, replied, and settled on "Here with you". Here's what we ran:

    • Current main with npm run dev, on a fresh Dot.
    • Current main as a production build (npm run build and npm start), on two fresh Dots back to back.
    • c2569bb, the commit in your report, as a production build with a clean database, again on two fresh Dots back to back.

    All three used hosted Intelligence and a local OpenAI-compatible model, in Chrome. One side note: on c2569bb, pressing Enter in the home composer doesn't send at all. That's the first point in #70, and #95 has since fixed it on main.

    The main thing we haven't matched is your Docker Compose setup with the computer overlays, plus gpt-5.4-mini. "Connecting to your conversation…" means the browser's connection to the conversation never finished, so the network path between the browser, the container and the Intelligence gateway is our best guess.

    If you're still seeing it on current main, could you share two things from a stuck attempt? The browser console output, and the /api/copilotkit/agent/<dot-id>/connect request from the Network tab, with its status and timing. That should tell us quickly whether the connection is hanging or failing. Thanks again!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions