Skip to content

[Bug]: Thread from a disconnected remote environment cannot be settled, deleted or reordered, and blocks pinning in the whole sidebar #12140

Closed as not planned

Description

@yaniv-fink

Before submitting

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

Area

apps/desktop

Steps to reproduce

Image

Setup

  • Two Windows 11 machines on the same network, both running T3 Code (desktop app, 0.0.40).
  • Machine A is my main machine. Machine B was connected to A as a remote environment for a while, and one thread was created from A that runs on B.
  • I later stopped using B. I turned off "serve this computer" on B (Settings → Connection → local environment) as the app suggested.

What happens on machine A

  1. The thread that lives on B still appears in A's sidebar, in its project, forever.
  2. Any action on that thread fails with Failed to pin thread. <machine B> is not connected. Settle, archive, delete and pin all fail the same way.
  3. The side effect is bigger than one thread: while that thread exists I cannot reorder or pin any thread in the sidebar. Every attempt ends with the same "is not connected" error. So one dead environment freezes sidebar ordering for the whole app.
  4. There is no way to remove the remote environment from A. The Connection page lists it with a "connect" button only. No "forget", "remove" or "disconnect" option.
  5. On machine B the thread does not appear at all, not under "All projects", not in search, so it cannot be cleaned up from that side either.

Expected

  • A remote environment can be forgotten from the Connection page when it is offline.
  • A thread whose environment is offline can still be settled, archived or deleted locally, or at least hidden.
  • Ordering and pinning of other threads should not depend on an offline environment.

Workarounds tried

  • Reconnecting B and turning its server off: no change.
  • Looking for the thread on B: not present.

Happy to send logs from either machine if you tell me which file.

Expected behavior

A thread can always be settled, archived, deleted or reordered locally, even when its remote environment is disconnected or gone. An offline remote environment can be forgotten from the Connection page. Ordering and pinning of other threads never depend on an offline environment.

Actual behavior

Settle, archive, delete and pin on the thread all fail with "Failed to pin thread. is not connected." While that thread exists, reordering or pinning any other thread fails with the same error. The Connection page offers only "connect" for the offline environment, no forget or remove.

Impact

Minor bug or occasional failure

Version or commit

Desktop app 0.0.40

Environment

Windows 11 Home, T3 Code desktop app 0.0.40 on both machines, same LAN

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 Sep 16, 2026
  2. juliusmarminge commented on Sep 16, 2026

    @juliusmarminge
    Member

    Closing as a duplicate of #4852, which tracks threads that cannot be settled, stopped, or deleted when their environment is offline (same "… is not connected." failure path). #8924 was closed the same way.

    Extra detail from this report that belongs on #4852: while the orphan remote thread exists, pin/reorder of any sidebar thread fails with that error, and the Connection page still only offers Connect (no forget/remove) for the offline LAN environment.

  3. added
    duplicateThis issue or pull request already exists
    and removed
    needs-triageIssue needs maintainer review and initial categorization.
    on Sep 16, 2026
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.duplicateThis issue or pull request already exists

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions