Skip to content

[Bug]: "Connecting to WSL" infinite loading #5967

Description

@QuentinScDS

Before submitting

  • I searched existing issues and did not find a duplicate.
  • I included enough detail to reproduce or investigate the problem.

Area

apps/web

Steps to reproduce

Don't know exactly but m wsl connection seems broken.
Other soft have no problem to access wSL, just T3 CODE.
Launching (stable or nightly) and get this screen

Image

Unable to do anything, infinite loading, no other window...

Expected behavior

T3 code launched and connected to WSL

Actual behavior

Infinite loading

Impact

Blocks work completely

Version or commit

No response

Environment

Windows 11 latest, bun latest, node latest

Logs or stack traces

Screenshots, recordings, or supporting files

No response

Workaround

No response

Activity

  1. added
    bugSomething is broken or behaving incorrectly.
    needs-triageIssue needs maintainer review and initial categorization.
    on Aug 10, 2026
  2. changed the title [-][Bug]: "Conntecting to WSL" infinite loading[/-] [+][Bug]: "Connecting to WSL" infinite loading[/+] on Aug 10, 2026
  3. arturskruze commented on Aug 10, 2026

    @arturskruze

    I get this a lot also.

    For me what helps sometimes is that I start up a fresh WSL session in a terminal, and then it loads in. If that doesn't work, then I open PowerShell, run wsl --shutdown, and then wsl. Once the WSL boots back up, then I restart T3 and then it works.

    I posted about this bug here: #3709

  4. emilhe commented on Aug 11, 2026

    @emilhe

    Similar issue here. Just installed T3 code. After having heard Theo talk about how amazing it is, I am a bit disappointed that it's just stuck on "Connecting to WSL" before i even got to use it. Claude Code and Codex was at least able to start up.

  5. t3dotgg commented on Aug 22, 2026

    @t3dotgg
    Member

    Note

    🤖 GPT-5.6 Sol in Codex responding on behalf of Theo

    Closing because the report does not have the current details needed to investigate. The report does not identify the cause of the WSL connection failure. Current diagnosed WSL failures are tracked in #5211 and #6465.

    A new issue can be opened with the current application version, reproduction steps, and relevant logs if the problem still occurs.

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

    bugSomething is broken or behaving incorrectly.needs-triageIssue needs maintainer review and initial categorization.

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions