Skip to content

feat(board): attention indicators in BoardSwitcher dropdown#1815

Open
tzercin wants to merge 3 commits into
preset-io:mainfrom
tzercin:feat-board-selector-attention-indicators
Open

feat(board): attention indicators in BoardSwitcher dropdown#1815
tzercin wants to merge 3 commits into
preset-io:mainfrom
tzercin:feat-board-selector-attention-indicators

Conversation

@tzercin

@tzercin tzercin commented Jul 6, 2026

Copy link
Copy Markdown
Contributor

Summary

Surfaces "needs attention" signals in the BoardSwitcher dropdown so users can spot boards with waiting work without opening each one. Reuses the same predicate that drives the branch-card glow (from PR #161).

What changed

  • Attention count badge — each board menu item with branches needing attention gets a warning-colored count badge alongside the existing branch-count badge.
  • Trigger dot — the closed switcher's board icon shows a dot when a non-current board needs attention (attention on the current board is already visible on the canvas).
  • Aligned with card glow — the badge counts needs_attention OR any active (non-archived) session that is ready_for_prompt, matching the card-glow predicate so a board whose sessions just finished responding no longer shows glowing cards with no badge. AppHeader now threads the store's sessionById map through.
  • Explicit hover text — the branch-count badge now has matching hover text ("n branch(es) on this board") instead of AntD's bare default.

Testing

Adds BoardSwitcher.test.tsx covering the badge aggregation, the ready-for-prompt predicate, and the trigger dot behavior.

🤖 Generated with Claude Code

Screenshot:
Screenshot 2026-07-06 at 12 29 35

tzercin and others added 3 commits July 3, 2026 09:35
Aggregate per-board counts of branches flagged needs_attention (the same
signal that drives the branch-card glow from PR preset-io#161) and surface them in
the board selector:

- warning-colored count badge on each board menu item that has branches
  needing attention, alongside the existing branch-count badge
- dot on the closed trigger's board icon when a *non-current* board needs
  attention, so users spot waiting work without opening the dropdown
  (attention on the current board is already visible on the canvas)

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
The attention badge already explained itself on hover; the branch-count
badge only showed the bare number (AntD Badge's default title). Give it
matching explicit text: "n branch(es) on this board".

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
The badge previously counted only branch.needs_attention, so a board
whose sessions had just finished responding (session.ready_for_prompt)
showed glowing cards but no badge. Use the same predicate as the card
glow: needs_attention OR any active (non-archived) session ready for
prompt. Archived branches are excluded — they're hidden from boards.

AppHeader now passes the store's sessionById map through.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
@mistercrunch

mistercrunch commented Jul 7, 2026

Copy link
Copy Markdown
Member

Before adding more metrics here, want to point towards a few things:

  • in large environments, "needs attention" isn't currently directed towards specific users who can actually take action
  • been thinking about a notification system for a moment, have design-docs and dev branches pointing in this direction, probably open PRs too I set aside for now.

I think a notification framework is probably more the direction to push this. I set this aside because of a mix of complexity/focus. Feels like a large effort that requires some deep thinking/focus to "get it right".

About the notif framework, it'd be actively managed to target the right people, show a notification bell in navbar, show attention indicators in the right places, to the right target people, ...

See the semi-abandoned PR #1135 for directionality.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants