feat(desktop): make thread reply notifications traceable - #3754
Draft
daveh-beep wants to merge 3 commits into
Draft
feat(desktop): make thread reply notifications traceable#3754daveh-beep wants to merge 3 commits into
daveh-beep wants to merge 3 commits into
Conversation
Signed-off-by: David Hamilton <daveh@squareup.com>
…n-traceability * origin/main: fix(desktop): remove remaining Projects panel fills (block#3742) feat(mobile): desktop-parity emoji and thread experience (block#3485) desktop: restore direct community member adds (block#3634) fix(desktop): explain open agent access (block#2561) fix(cli): resolve agents from owner records (block#3178) fix(desktop): remove Projects overview card fills (block#3416) feat(replica): portable heartbeat-token fence with snapshot-local reader routing (block#3268) fix(git): channel binding tooling + author remediation for unbound repos (block#3626) feat: configure S3 URL addressing style (block#3400) feat: add first-class OpenRouter provider support (block#1975) feat(agent,acp): wire provider total_tokens through NIP-AM publish chain (block#3593) chore(release): release Buzz Desktop version 0.5.2 (block#3624) docs: add Linux rendering troubleshooting guide (block#3573) fix(desktop): discover bun-installed agent CLIs in ~/.bun/bin (block#3343) feat(tracing): correlate trace IDs in relay logs (block#3608) chore(ci): bump Linux AppImage build container to ubuntu:24.04 (block#3602) feat(cli): mirror Desktop mention delivery (block#3330) Signed-off-by: David Hamilton <daveh@squareup.com>
Signed-off-by: David Hamilton <daveh@squareup.com>
daveh-beep
added a commit
to daveh-beep/buzz
that referenced
this pull request
Jul 30, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Problem
A reply in a followed/participated thread currently makes the channel row bold with a solid numeric badge. Opening that channel produces no visible new message because thread replies are intentionally excluded from the top-level unread divider. The only trace is muted
(N new)metadata under the parent message, which may be off-screen.This creates a signal-strength inversion: the strongest signal points at a surface with no visible payoff, while Inbox—the surface that can resolve the notification—gets the weakest signal.
Design rationale and before/after loop
https://blockcell.sqprod.co/sites/buzz-design-reel/
The reel uses Buzz's dark-theme HSL tokens, Inter Variable font, real sidebar/button dimensions, badge classes, unread divider, thread-summary treatment, and unread pill styling. It includes realistic states for channel messages, thread-only replies, mentions, DMs, muted channels, and read channels.
Test plan
just desktop-checkjust desktop-test(3824 passed)Review status
Draft for design and implementation review. Please treat the Blockcell reel as rationale/fodder, not a final spec.