Skip to content

MISSING FROM BUZZ: working set, labelled work items (not just channels/threads as bags of words) #6067

Description

@apatrida

Motivation
When working on tasks, they end up in channels and reply threads with little find-ability, and no quick way to jump channels and threads. You end up having to find the thread by words (most threads start with @-mentions so you have to jump past that to try and figure out what the thread is about), and you lose context and position with every jump.

We need a way to relabel a thread as a work item, and that adds it to your working set list that can be quickly hopped between without losing your scroll position within the item, your unread items, etc. A 0-lag hop. Bounce between your convos.

NO, INBOX IS NOT THIS, it is just "@yourownname bla bla bla" repeated 1000 times and doesn't help to jump where you want to check on updates.

Try having 3 continuous conversations in 3 channels with bots and hop between them and keep them all moving at same time and suffer, then you will understand this request. Suffering drives innovation?

Proposed solution
Some gesture to relabel a thread as a "work item" within your personal "working set", add it with a title and it goes into a list of those that you can archive and manage with quick hops between your in flight tasks. These are pointers into the channel/threads that retain your scroll, and visual state and are fast hops without having to re-find where you were prior.

Alternatives considered
Other forms of self harm via UX, but decided one was enough.

Additional context
Use Buzz for real work, something like this should be the thing nagging your every awake minute.

Activity

jhedlund commented on Aug 20, 2026

@jhedlund
Contributor

+1 on this, I find it difficult find what a thread is actually doing, seems like each thread should get a chat label just like other chat tools auto-label (but can override the label too)

Giszmo commented on Sep 7, 2026

@Giszmo

I want this feature, too. It can be really low-tech. Just use the last comment from the thread that contained a line "thread name: issue 12" or so. No replaceable events or new server features needed.

With "last to mention" I aim explicitly at agents being able to adjust it on a last-to-act basis on equal footing with any participants.

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

    enhancementNew feature or request

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions