Skip to content

[Bug]: Links to archived threads look the same as live ones (regression since 0.1.7) #40685

Open

Description

@clintebbesen

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

  1. In one thread, have the agent reply with a list of thread links (for example, "these 40 threads are finished and ready to archive").
  2. Click one of the links, archive that thread, then go back to the list.
  3. Repeat for a few more.

Expected behavior

Links to archived threads look different from links to live threads, as they did in 0.1.7: the project icon is replaced by the plain thread icon and the tooltip says "Thread no longer available". Then you can work down a long list and see at a glance which threads are done and which are still left.

Actual behavior

From 0.1.11, a link to an archived thread looks exactly like a link to a live one: same title, same project icon, same "Open thread" tooltip. The chip now gets its title and project from threadLinkMetadata even when the thread is archived, so nothing shows that it is archived.

Clicking an archived link doesn't open the archived thread either. It lands on the new-thread screen, so you can't see or unarchive it from there. The link looks live but goes nowhere useful.

The result: once a list has 20 to 50 links, there is no way to tell which ones you've already archived without clicking each one. A workflow that used to be easy (open, archive, come back, take the next unmarked one) no longer works.

I think this came from the fixes for #26467 and #32541, where live but unloaded threads wrongly showed as unavailable. Those fixes were right for live threads. Archived threads just need their own state.

Suggested fix: have threadLinkMetadata return whether the thread is archived, and give archived links a distinct state (muted or struck-through chip, an "Archived" tooltip). Better still, clicking one should open the archived thread read-only with an Unarchive button instead of the new-thread screen.

Impact

Major degradation or frequent failure

Version or commit

Regression between 0.1.7 (worked) and 0.1.11 (broken)

Environment

Self-hosted server on Linux, web client in Chrome on macOS

Workaround

Ask the agent to post the list again without the archived threads.

Activity

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