[jwondrusch]

Adds Slack-style hotkeys to Buzz desktop, mostly from requests in #buzz-feedback.

Keys

Inbox and unread

• ⌘⇧A opens Inbox with Unread only.
• ⌘⇧T, ⌘⇧M and ⌘⇧K open Inbox filtered to Threads, Mentions and DMs.
• Esc marks the open conversation read.
• ⇧Esc asks for confirmation, then marks the whole community read.

Navigation

• ⌥↑/↓ step through conversations in sidebar order. ⌥⇧↑/↓ step through unread ones only.
• ⌘T opens Search Buzz, as a second default chord for ⌘K.
• ⌘1–⌘9 jump to entries in the community switcher. ⌘1 is Personal space. ⌘⇧] and ⌘⇧[ move to the next and previous community, wrapping around.
• ⌘⇧Y opens Set a status.
• ⌘/ opens Settings → Shortcuts, using main's binding from feat(shortcuts): open Shortcuts settings with Mod+/ #2022. An earlier version of this branch had its own read-only ⌘/ panel. It was dropped so there's one place to see and change shortcuts.
• Home moves to the placeholder ⌘⇧O so ⌘⇧A can open Inbox. This is to revisit before merge.

Messages

• ↑ in an empty composer selects the newest message. ⌘↑ keeps the old edit-last behavior.
• With a message selected:
  • ↑/↓ move the selection and Esc returns to the composer.
  • E edits and R reacts.
  • T or → replies in thread, and U marks unread.
  • Delete or Backspace deletes your own message, with the existing confirmation.
• ⌘⇧\ reacts to the latest message.

Settings → Shortcuts

• A shortcut can have several default chords, and Settings lists each one ("⌘K or ⌘T"). Two chords for the same physical key on a layout show once.
• The message editor's formatting keys appear in a read-only "Message formatting" section. A shortcut rebound onto one of them shows a warning.
• Slack's ⌘⇧C (code), ⌘⇧9 (quote), ⌘⌥⇧C (code block) and ⌘⇧U (link) are added as aliases of Buzz's own chords.

Fix: plain-Escape dismissals (thread, panels, drawer, plugin details) now ignore Shift, so ⇧Esc in a thread composer no longer closes the thread.

No FOUNDATION files are changed. Remind me (M) is left out because plugin message actions can't declare a key without a contract change.

Overlap with #2155

#2155 also adds ⇧Esc (without a confirmation) and the same Shift guards, and it edits ShortcutSettings.tsx. Whichever PR merges second will need a rebase.

Open questions

• Should ↑ select messages (this PR), or keep Slack's ↑-to-edit, which nbl's ↑ → ⌘A → Delete flow relies on?
• Home needs a permanent chord in place of ⌘⇧O.

Validation

• Rebased onto main at 24c0adb.

• pnpm check passes on 1b22c8f. Full vitest run on 1b22c8f: 15,523 passed and 1 failed. The failure is browser-host/media-preparation.integration.test.mjs (tiled HEIC), which this branch doesn't touch.

• New tests:

  • message selection
  • the selected-message keys through the real dispatcher
  • community switching
  • ⌘T
  • the formatting aliases
  • the Settings read-only section
  • ⇧Esc leaving a tab-hosted side thread and an untabbed side panel open. The ⇧Esc-in-thread test fails without the Shift guard.

• Browser journeys: none added or removed. Three were updated for intended behavior changes. On 1b22c8f, shortcuts, settings, settings-layout and nested-replies pass locally on chromium and webkit (68 tests). message-edit passed earlier on chromium.

  • nested-replies: edits with Up then E, because plain Up now selects the newest message.
  • message-edit: the composer fixture has no app shortcuts, so E isn't wired there. It now edits with ⌘↑, which still edits directly, and is renamed to match. Up → E is covered by src/app/message-shortcuts.test.ts.
  • shortcuts: the shortcut-counter example plugin moves from ⌘⇧K to ⌘⇧G, because ⌘⇧K now opens Inbox DMs as in Slack. Both are plugin keys, and buzz.inbox sorts before example.shortcut-counter, so Inbox's would win.

• Test fixture: tests/fixtures/terminal-panel.tsx now caps its settings area's height. The new formatting group was pushing the terminal drawer below the webkit viewport. terminal-renderer and terminal-motion pass on webkit and chromium.

• Agent exercise (1b22c8f): a throwaway Playwright check, on chromium and webkit, pressed ⌘/ in the composer. Settings → Shortcuts opened and listed the new rows (Set a status, Mark all as read, Message formatting). No separate shortcuts dialog appeared.

• Human test: Jonathan tested Up-to-select, then E, R, T/→, U and Delete, plus ⌘1–9, ⌘⇧] / ⌘⇧[ and the Inbox keys, in the app. He re-checked ⌘/ on 1b22c8f, and it opens Settings → Shortcuts.

• Plugin keys: Inbox's ⌘⇧A/T/M/K keep the existing plugin precedence. This is documented in docs/plugin-architecture.md and docs/buzz-help.md.

• Performance: Settings builds the Shortcuts section the first time it's opened, not every time Settings opens. Settings renders all its sections in the background, and this branch roughly doubles the Shortcuts rows, so opening Settings had become about 20% slower in whole-app tests (found by comparing CPU profiles against main). After the change, the same tests run slightly faster than on main.

• Known CI flakes not caused by this branch:

  • webkit nested-replies "crowded capped branches", which also fails on main
  • history-loading "held pointer scrolls" on webkit, which also fails on other PRs

buzz-review-completed

Screenshots

🤖 Generated with Claude Code

[kalvinnchau]

🤖 Two wrong-target shortcut defects were reproduced in Chromium and WebKit. Additional inline comments cover plugin compatibility and history traversal. Please resolve these before merging; native key delivery and final-head CI remain unverified.

[jwondrusch]

🤖 @kalvinnchau Thanks for the review. All four findings are addressed, and CI is green on 2ec71bf. Could you take another look and approve if it holds up?

• Newest reply by identity: Up and ⌘⇧\ now select the newest message by id, not the last row in tree order. Fixed in df8485d, with a test.
• React-to-latest target: ⌘⇧\ selects the newest message first, even when an older one is selected. Fixed in df8485d, with a test.
• Inbox on Back/Forward: returning to an Inbox shortcut visit no longer re-applies its filters. Fixed in df8485d, with a test.
• Plugin precedence for ⌘⇧A/T/M/K: we're keeping the existing sorted-ID precedence and documenting it (a60a210). Settings flags shared chords with "Also used by". Any bundled-first ranking would come in its own PR.

Since your review:

• 2ec71bf: Settings builds the Shortcuts section on first visit instead of on every open. The larger shortcut list had made whole-app tests about 20% slower.
• 0ca5c44: the terminal test fixture caps its settings height so the drawer stays in view on webkit.

Jonathan has tested the keys by hand, and buzz-review-completed is in the description.

[jwondrusch]

🤖 @kalvinnchau I rebased this onto main (24c0adbfe) at 1b22c8ff0. One behavior change since your approval: main's #2022 already binds ⌘/ to open Settings → Shortcuts, so I dropped this branch's separate read-only ⌘/ panel and kept main's binding. The rest is the same change you approved.

• pnpm check passes. Full vitest fails only the known HEIC test.
• The shortcuts, settings, settings-layout and nested-replies browser journeys pass on chromium and webkit.
• Jonathan re-tested ⌘/ in the app.

Could you take another look and merge once CI is green? Jonathan's account can't merge.