Files
buzz/desktop
DuncanandWill Pfleger ecbf20a66f feat(workflows): reply in-thread from send_message action
The send_message workflow action could only post new top-level channel
messages. Add reply_in_thread so a message_posted workflow can reply in
the triggering message's thread, and expose trigger_is_reply so a filter
can restrict the workflow to top-level messages only.

Schema rejects reply_in_thread on schedule/webhook triggers, which carry
no message to reply to. The relay sink resolves parent/root/depth from
the known trigger event (mirroring the ingest thread rules), emits NIP-10
root/reply e-tags, and persists real thread metadata instead of the
hardcoded top-level params. The desktop step card gains a checkbox shown
only for message-based triggers, round-tripped through the YAML form.

Co-authored-by: Will Pfleger <pfleger.will@gmail.com>
Signed-off-by: Will Pfleger <pfleger.will@gmail.com>
2026-08-17 18:55:02 -04:00
..
2026-08-03 21:51:17 -04:00

Buzz

Desktop chat shell with:

  • Tauri + React + TypeScript + Vite
  • Tailwind CSS
  • shadcn/ui-ready shared components
  • Biome (lint/format/check)
  • Feature-driven frontend structure

Scripts

  • pnpm dev - run the web frontend
  • pnpm tauri dev - run the desktop app
  • pnpm build - typecheck and build frontend
  • pnpm typecheck - TypeScript checks
  • pnpm lint - Biome lint
  • pnpm format - Biome format (write)
  • pnpm check - Biome check

Structure

  • src/shared - reusable app-wide code (ui, lib, styles)
  • src/features - feature modules (vertical slices)
  • src/app - top-level app composition