Skip to content

Links to older settled threads show "Thread no longer available" #26467

Closed

Description

@gabimoncha

What happened

In an agent reply, a link to a thread shows as "Thread no longer available". The thread still exists. It is settled, not archived. The link should show the thread's title.

Image

Diagnosis

To keep the thread list small, the server leaves older settled threads out of the list that it sends to the client (omitOlderSettled). MarkdownThreadLink looks for the thread only in that list. If the thread is not there, the link shows as an UnresolvedChip with the text from unknownThreadLinkLabel, which is "Thread no longer available". ThreadContextChip (composer and user-message chips) has the same gap: its tooltip shows "Thread no longer available", and the chip has no project icon.

Chat view loads threads that are not in that list with useThreadFamily (the getThreadFamily read). That read includes settled threads (ProjectionStore.ts, familyOf filter), but the link chips never call it.

Archived threads have the same symptom, but the family read skips archived threads, so the fix for them is different.

Steps to reproduce

  1. Settle a thread, and let it become old enough that the thread list leaves it out (it moves to the Settled shelf).
  2. In another thread, have an agent reply with a link to that thread.
  3. The link shows "Thread no longer available" and not the thread's title.

Version

0.1.4-nightly.20261028.3822

Environment

macOS (Darwin 27.2), T3 Code

Related issues

#16443 (opening an archived thread from its link). That issue is about navigation, not about how the link shows.

Fix applied or workaround

None on the machine. A fix is ready: call useThreadFamily in MarkdownThreadLink and ThreadContextChip when the thread is not in the local list (6 lines).

Filed by

claude (opus-5.5) via t3 triage with @gabimoncha's permission

Activity

  1. added a commit that references this issue on Oct 28, 2026
    57108a4
  2. ViaxCo commented on Nov 3, 2026

    @ViaxCo
    Contributor

    Same bug on 0.1.7-nightly.20261103.4106 (macOS 26, desktop app, local server), so it still happens on the newest nightly. The fix in #26472 is not merged yet.

    A Codex agent reply had 4 autolinks (<t3-thread://v2/<env>/<id>>). All 4 show "Thread no longer available". All 4 threads exist, are not archived, and t3_thread_read reads them without problems. In this user's database, they rank 81st, 92nd, 104th and 142nd among settled, listed threads by settledAt. NEWEST_SETTLED_KEPT is 25, so the shell stream leaves all of them out, and MarkdownThreadLink finds no shell. One of the ids has an mcp: prefix (a thread created by t3_thread_launch). It fails in the same way as the plain UUIDs, so the id format is not the cause.

    This happens most often in audit or summary replies. Those replies link to older work, so most of their links break.

    Thread links in an agent reply showing Thread no longer available

    Comment drafted by Claude (claude-opus-5-5) in Claude Code via t3 triage.

  3. sebstrgg-agent commented on Nov 7, 2026

    @sebstrgg-agent

    Claude Opus 5.5 · on behalf of sebstrgg

    This may be connected to #32541. The same "Thread no longer available" chip appears on 0.1.8-nightly.20261106.4288 for a thread that is not settled or archived. So omitOlderSettled probably isn't the only way a thread drops out of the list the chip checks. If #26472 falls back to the thread-family read for any thread it can't find, settled or not, it may fix both.

  4. sebstrgg-agent commented on Nov 7, 2026

    @sebstrgg-agent

    Claude Opus 5.5 · on behalf of sebstrgg

    On impact: our agents now settle their thread when the work is done, since settling is the clean way to finish (archiving your own thread mid-turn fails the turn, #15135). With this bug, every link to such a thread goes dead once it falls out of the newest settled threads, so most thread-to-thread handoffs ("I asked the X thread to message me when …") end up as dead links. Merging #26472 would fix that common path.

  5. Yash-Singh1 commented on Nov 8, 2026

    @Yash-Singh1
    Collaborator

    Note

    Generated by GPT 6.1 Sol

    Fixed on main by merged PR #32830. Thread links and context chips now look up the title and project ID when the thread is absent from the loaded list, so older settled threads can show their title and project icon and open without first being found through search. The lookup excludes deleted threads but does not exclude older settled or archived threads. Closing as completed.

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