Skip to content
Permalink

Comparing changes

Choose two branches to see what’s changed or to start a new pull request. If you need to, you can also or learn more about diff comparisons.

Open a pull request

Create a new pull request by comparing changes across two branches. If you need to, you can also . Learn more about diff comparisons here.
base repository: block/buzz
Failed to load repositories. Confirm that selected base ref is valid, then try again.
Loading
base: desktop-v0.5.22
Choose a base ref
...
head repository: block/buzz
Failed to load repositories. Confirm that selected head ref is valid, then try again.
Loading
compare: desktop-v0.5.23
Choose a head ref
  • 18 commits
  • 180 files changed
  • 17 contributors

Commits on Sep 3, 2026

  1. Configuration menu
    Copy the full SHA
    2ac0aa1 View commit details
    Browse the repository at this point in the history

Commits on Sep 4, 2026

  1. Configuration menu
    Copy the full SHA
    4b0744d View commit details
    Browse the repository at this point in the history
  2. feat(desktop): preserve mentions across copy and paste (#7228)

    Copying a message out of the timeline lost the mention. The rendered
    chip drops
    the `@` for display, so the clipboard carried "John Smith" — two
    ordinary words
    no composer could bind back to a pubkey. Pasting into another channel
    produced
    dead text, and sending it tagged nobody.
    
    ## What changed
    
    Every Buzz copy now writes two clipboard flavors in one transaction:
    
    - **`text/plain`** — readable anywhere, sigils restored, no pubkeys.
    This is what
      TextEdit, Slack, and every other external app receive.
    - **`text/html`** — the same content with each mention wrapped in a span
    carrying
      `data-mention-pubkey` / `-label` / `-kind`.
    
    On paste, the composer harvests those records, registers each `name →
    pubkey`
    with the existing mention machinery, and inserts the content: the chip
    re-lights
    and the send path recovers the identity the author tagged. A marker
    attribute
    records what the plain flavor holds, so a Markdown copy pastes through
    the text
    pipeline and a rendered copy through the HTML one.
    
    **Covered surfaces:** timeline selection copy, thread-panel selection
    copy,
    forum post/reply selection copy, "Copy message", and composer copy/cut —
    plus
    paste in both the channel and forum composers.
    
    ## Trust boundary
    
    Clipboard HTML is untrusted, and the branch treats it that way:
    
    - Records are capped (50), labels bounded (200 chars), and a pubkey must
    be
      64 hex before it can become a `p` tag.
    - **Only mentions the paste actually shows are registered.** An empty
    `<span data-mention-pubkey=… -label="Jane Doe">` would otherwise rebind
    that
    display name for the rest of the composer session, so a later
    hand-written
    @jane Doe would chip-light convincingly against the attacker's key. Each
      branch registers only the records whose label appears in the text *it*
    inserts, matched with `getMentionOffsets` — the same matcher the
    send-time
      extractor uses.
    - **The visibility gate reads only what ProseMirror will insert.**
    `DOMParser` hard-drops `script`, `style`, `title`, `noscript`, `object`,
    and
    `head` content, so `visible<style>@jane Doe</style>` beside an empty
    chip span
    used to smuggle a binding past the gate. Those elements are stripped
    before
      either output is derived.
    - **A partial chip never gains a sigil.** A selection crossing a chip
    boundary
    falls through to the browser's default copy, which serializes the full
    identity
    attributes around a slice of the text — pasting that invented "@smith"
    out of
    "John Smith". Paste now leaves a fragment as plain text, tolerating only
    what a
    whole chip picks up in transit (restored sigil, author casing, U+00A0
    swaps,
      and the label cap's own ellipsis).
    
    Both clipboard sides share one `matchChipTextToLabel` helper, in the
    module that
    owns the label attributes, so copy and paste cannot drift on what counts
    as a
    whole chip.
    
    ## Notes
    
    - Mention matching reuses `getMentionOffsets`, so code spans and fences
    are
      excluded and the longest display name wins.
    - The plain flavor inlines chip boxes before reading `innerText`; a chip
    is a
    flex container, so the browser's own copy split "@john Smith" onto its
    own line.
    - `MarkdownMention` and `MacEmacsTextShortcuts` are extracted verbatim
    from
    `markdown.tsx` and `useRichTextEditor.ts` to keep both files under the
    size gate.
    
    ## Testing
    
    - ~40 unit tests over the flavor builder/parser, the visibility filter,
    the
      ignored-tag sweep, and the chip-match verdicts.
    - A Playwright spec (`desktop/tests/e2e/mention-clipboard.spec.ts`)
    driving real
      copy/cut/paste DOM events: timeline and "Copy message" of a multi-word
    non-member mention pasted into another channel and sent with the
    original
    pubkey in its `p` tag; the forum copy → forum reply round trip; composer
      copy/cut; plain flavor asserted to contain no 64-hex string; the
    boundary-crossing drag; and the hidden-record and `<style>` smuggling
    vectors.
    - Every regression test is bound to a production seam and fails with its
    guard
      removed.
    - `just ci` / pre-push lanes green (5927 desktop unit tests, typecheck,
    lint,
      file-size gate).
    
    ---------
    
    Signed-off-by: Matt Toohey <[email protected]>
    Co-authored-by: Claude Fable 5 <[email protected]>
    matt2e and claude authored Sep 4, 2026
    Configuration menu
    Copy the full SHA
    b1f6b7e View commit details
    Browse the repository at this point in the history
  3. chore(release): release Buzz Desktop version 0.5.22 (#7308)

    ## Buzz Desktop release v0.5.22
    
    - **Frozen main:** `75f101d8b4f5b4b26f9891b73b87c67fedac25a0`
    - **Reviewed candidate:** `9ceb1f79bbc21785a0a075c40aecb3c058b1ea15`
    - **Previous desktop release:** `desktop-v0.5.20`
    - **Proposed immutable tag:** `desktop-v0.5.22`
    
    This PR may be **squash merged** after the Desktop Release Candidate
    check and all protected-branch checks pass. Merging authorizes
    publication of the exact reviewed candidate; later or unrelated changes
    on `main` cannot alter it.
    
    The checked-in changelog accounts for every non-merge commit in the
    release range. The Desktop tag points to the reviewed candidate commit,
    not the later squash commit. Publication remains bound to that immutable
    candidate tag.
    
    Signed-off-by: Will Pfleger <[email protected]>
    Co-authored-by: Release Automation <[email protected]>
    wpfleger96 and release-automation authored Sep 4, 2026
    Configuration menu
    Copy the full SHA
    01bacb8 View commit details
    Browse the repository at this point in the history
  4. refactor(relay): extract NIP-29 membership authorization (#7285)

    ## Why
    
    NIP-29 membership authorization for kinds 9000, 9001, and 9022 was
    embedded in a large async handler, requiring Postgres and Redis to test
    and repeating the last-owner rule across five call sites. This addresses
    [TheSentinel454#24](TheSentinel454#24)
    without adding the broader state/repository abstraction suggested there
    because HTTP and WebSocket writes already share ingestion.
    
    ## What
    
    - Extract pure, typed membership authorization decisions while leaving
    database reads and mutations in `validate_admin_event`.
    - Preserve existing client-visible errors and independent database
    last-owner safeguards.
    - Collapse five last-owner policy restatements into one predicate and
    share the identical self-departure policy.
    - Include the relay decision modules in `just test-unit`, so these tests
    execute in CI.
    
    ## Risk Assessment
    
    Medium-low. This touches production relay authorization, but
    intentionally preserves wire behavior and database defense in depth;
    exhaustive decision tables and relay-backed tests cover the affected
    paths.
    
    ## Simplification
    
    This removes repeated policy from the orchestration path and makes the
    rule set directly testable without introducing a repository trait or
    second transport path.
    
    ## Verification
    
    Verified at `15255a090797f85874921120003c645962fefaed`:
    
    - `just test-unit` — all 10 package summaries passed. An initial run hit
    two unrelated timing-sensitive `buzz-acp` failures; the complete retry
    passed 905/905 in that package.
    - `cargo fmt --all -- --check`
    - `cargo clippy --workspace --all-targets -- -D warnings`
    - `just file-size-check` — 10/10 policy tests passed.
    - `just security-review-check` — 13/13 tests passed.
    - Push preflight — `push-head-scope`, `branch-skew`, `file-size-check`,
    `rust-tests`, and `desktop-tauri-checks` passed.
    - Blox Postgres relay lane — 84/84 at the byte-identical source patch;
    full live `e2e_relay` behavior matched the clean base (45 pass and the
    same pre-existing kind:9002 failure on each).
    
    Generated with Claude Code
    
    ---------
    
    Signed-off-by: tornquist <[email protected]>
    Co-authored-by: Claude Opus 5 <[email protected]>
    Co-authored-by: Codex <[email protected]>
    3 people authored Sep 4, 2026
    Configuration menu
    Copy the full SHA
    cd02b69 View commit details
    Browse the repository at this point in the history
  5. fix(desktop): bind duplicate mention selections to exact recipients (#…

    …7133)
    
    ## Summary
    
    Selecting two people or agents named Scout could replace the first
    recipient with the second even though the message still looked right.
    This binds each selection to its exact identity: the first keeps
    `@Scout`, and a conflicting selection gets `@Scout (<full public key>)`.
    Removing one no longer removes or redirects the other.
    
    - Reuse the existing **@ suggestion list**; team selection and automatic
    agent addressing reserve and reuse distinct labels too. Typing an
    ambiguous name manually shows an instruction to use the picker and
    preserves the draft without publishing—in chat, edits and standalone
    forums.
    - Share literal mention matching across recipient extraction, removal,
    display and editing so a shorter name cannot claim another recipient's
    longer or qualified label.
    - Rebuild authored references when a message is edited, and use the
    latest authorized snapshot when reopening or forwarding.
    Rendering/editing can recover qualified identities only from the
    message's recorded references, not from a key typed into its body.
    Unresolvable historical names remain literal rather than guessed
    recipients.
    - Wrap full-key labels within narrow/zoomed layouts while keeping their
    complete accessible label and ordinary mention icons. Edit activation
    waits for the action menu's focus cleanup before focusing the editor.
    
    ### Related issue
    
    Targets `main`; mention spacing (#7128) is already merged. Split from
    #7114. This is independent of the #7124 → #7125 remote-invitation stack
    and does not expand agent eligibility or invitation permissions. The
    separate Enter-selection suffix issue remains tracked in #7253.
    
    ### Testing
    
    The desktop unit suite and focused mock-Chromium checks passed on the
    published integration candidate, including pending-paste selection,
    edit/forwarding, copy and narrow-layout cases; formatting, types and
    frontend builds passed. On `0b3b18c0`, 64 focused trust/paste/selection
    unit tests and six mock-Chromium tests passed with zero browser retries,
    including actual timeline chip copy → fresh channel paste → send and
    mismatched-key rejection; TypeScript, changed-file Biome and an isolated
    E2E build passed. The broader browser run had copy failures before the
    focused repairs and is not claimed as wholly green. See [live
    CI](https://github.com/block/buzz/pull/7133/checks) for current-head
    results. No full local `just ci` pass, native/live-relay or
    cross-browser validation is claimed.
    
    To try it: select two same-name recipients, remove one, send, then
    edit/reopen and forward; only the intended identities should remain.
    Type an ambiguous name without choosing a suggestion and check that
    sending retains the draft with an error. Inspect full-key labels in a
    narrow window at 150% text size, and open Edit and type immediately.
    
    ![Ambiguous mention keeps the chat
    draft](https://raw.githubusercontent.com/block/buzz/c48053209b36b3b1bf7197cf2d606d27b48a27c0/pr-7133--ambiguous-general.png)
    
    ![Full-key label in a narrow, zoomed
    composer](https://raw.githubusercontent.com/block/buzz/ac262f00de6fe3860bff2f87dc0e98165ed6b651/pr-7133--layout-1.5-composer.png)
    
    *Earlier mock-browser captures, not current-head runtime proof. No new
    before-state capture; screenshots alone do not prove recipient
    delivery.*
    
    **Clipboard trust:** generated full-key-qualified mentions now retain
    their exact recipient after copy/paste when the full key matches the
    clipboard record and community directory/profile state independently
    vouches for the base alias, including numeric collision suffixes. A
    qualifier alone does not establish trust. Arbitrary historical labels
    still cannot always be reconstructed.
    
    ---------
    
    Signed-off-by: Logan Johnson <[email protected]>
    Co-authored-by: Larry <627498bd4bd1f281a16431e3c6cce3b5c25b6692798c78672298aefbf2f8f8b5@buzz.block.builderlab.xyz>
    Co-authored-by: Bad Janet <150b20bdf6130418df9239dd1bd082c71612c8d653b47c277200365b9be215dc@buzz>
    3 people authored Sep 4, 2026
    Configuration menu
    Copy the full SHA
    ee883d7 View commit details
    Browse the repository at this point in the history
  6. fix(acp): rename system tag to agent-instructions (#7332)

    ## Summary
    
    Rename the paired persona prompt boundary from `<system>` to
    `<agent-instructions>` in both modern and legacy ACP delivery paths.
    Update Desktop diagnostics to label the new boundary as Agent
    Instructions while keeping archived `<system>` captures readable.
    
    `system` is confusing (esp with system role) and agent instructions is
    what shows up in the UI today
    
    <img width="767" height="298" alt="Screenshot 2026-09-04 at 11 37 54 AM"
    src="https://github.com/user-attachments/assets/4e34ac06-db50-461e-a555-ce17885b0031"
    />
    
    ### Related issue
    
    Follow-up to #6701. No duplicate open issue or PR found.
    
    ### Testing
    
    - `cargo test -p buzz-acp`
    - `cargo clippy -p buzz-acp --all-targets -- -D warnings`
    - `node --import ./desktop/test-loader.mjs --experimental-strip-types
    --test
    desktop/src/features/agents/ui/agentSessionTranscriptHelpers.test.mjs
    desktop/src/features/agents/ui/agentSessionTranscript.test.mjs`
    - `pnpm --dir desktop typecheck`
    - Pre-push hook: 6,237 Desktop tests, 3,164 Tauri tests, and all 13 Rust
    unit-test lanes passed
    
    Generated with Codex
    
    Signed-off-by: Salman Mohammed <[email protected]>
    salman1993 authored Sep 4, 2026
    Configuration menu
    Copy the full SHA
    ce9decb View commit details
    Browse the repository at this point in the history
  7. fix(desktop): authorize remote mentions at publication (#7124)

    🤖
    
    ## Summary
    
    In Buzz Desktop, you could own an agent running on another device but be
    unable to mention it in a channel where it had not yet joined: it was
    filtered out before you could invite it. A selected agent could also
    disappear from the message's recipients when permissions changed. This
    lets you select an eligible agent in the existing **@ menu**, invite it
    from the message composer, and send to that agent—or see an error and
    keep your draft rather than silently sending without it.
    
    #### Where the experience changes
    
    | Screen / control | Before → after |
    | --- | --- |
    | A channel's **Message #…** composer, or a message's **Reply in thread
    to …** composer | Type `@` (or use the existing @ button), choose your
    agent, write the message and press **Send message**. An owned agent not
    yet in the channel can now reach the existing **“Mention people outside
    this channel?”** dialog when its response settings allow you to address
    it. |
    | That dialog's **Invite** button | Previously the membership
    requirement could block the agent before the invitation. Now Invite
    checks permission to add it, adds it as an agent member of the
    **channel** (not just the thread), then rechecks membership and response
    permission before sending the waiting message. An agent already in the
    channel needs no invitation. |
    | Existing direct message, or the new-message screen with the **To:**
    field | A mention is checked against the conversation the message will
    actually enter, including a newly created direct message, rather than
    the old or not-yet-created destination. This does not add an Invite
    control to direct messages. |
    | Editing a message / sending attachments | The selected agent remains
    part of the send or edit attempt through attachment upload and the final
    permission check. Lost permission produces a visible error instead of
    dropping that recipient. |
    
    **Invite is not the only chat choice.** The existing **Do nothing**
    button sends the message *without inviting or notifying the nonmembers*;
    their names remain references in the text. Where you cannot invite, that
    choice is labelled **Send anyway**. To abandon the send instead, dismiss
    the dialog with Escape. Invitation actions are disabled while
    preparation is pending, preventing duplicate clicks.
    
    **Leaving and returning must not resurrect a cancelled send.** Switching
    threads or leaving the composer cancels its pending invitation, even if
    you return to the same thread. Cancellation before dispatch sends no
    message; an accepted membership change cannot be automatically undone.
    An ordinary send without a pending invitation remains bound to its
    original destination rather than following you into another
    conversation.
    
    **Failed sends must not overwrite your next draft.** If you leave a
    thread, return and replace or deliberately clear its draft while an
    older send is pending, the older failure cannot restore deleted text,
    recipients or files; success cannot erase the newer draft—even if its
    text is identical. An untouched draft cleared automatically for sending
    remains recoverable on failure. This protection also covers reopening
    the composer and starting a newer send.
    
    The channel timeline also keeps its existing **new-messages / Jump to
    latest** button available when newer messages are waiting to be
    displayed. For example, after sharing a reply to the channel and closing
    the thread panel, you can click the catch-up button to reveal buffered
    messages. Closing the thread does **not** guarantee the shared row
    appears automatically or force you away from reading history.
    
    ### Related issue
    
    Built on [#7122](#7122), base branch
    `split/owned-agent-discovery`, which lets Desktop find and verify owned
    agents independently of this device. Current integration head:
    `1144465d00273cf74b7c22544ae5a3299bd98560`, built on exact published
    root `3a56d17824522580fe04cae463b54f4c7ba66021`. Root #7122 has its own
    CI and security gates; this PR must not land ahead of that dependency.
    Finding an agent is not channel membership, online status or a promise
    of a reply. This PR changes what the existing message controls can do
    with those agents; it adds no profile, presence, cloud marker or remote
    start/stop UI.
    
    Standalone forum post/reply **Invite / Cancel** is added separately in
    [#7125](#7125); here those composers
    only gain visible authorization errors. Same-name selection/binding
    fixes ([#7133](#7133)) and mention
    spacing ([#7128](#7128)) are not
    included.
    
    Extracted from [#7114](#7114)
    (historical source `98fe33ec`). [Behavior and draft-recovery
    contract](https://github.com/block/buzz/blob/1144465d00273cf74b7c22544ae5a3299bd98560/docs/remote-mention-routing.md)
    · [Originating
    discussion](buzz://message?channel=f7a9536a-1738-4bad-a888-b3ea25010ef1&id=7aa1f0ab23dce514bd8a0221441cf005bf428914621171472b79747c50820848).
    
    ### Testing
    
    ![Channel composer after Send: RemoteScout is not a channel member;
    Invite adds it before sending, while Do nothing sends without inviting
    or notifying
    it](https://raw.githubusercontent.com/block/buzz/b20345da0bd648ecbc78988637c89893a33ca2f3/pr-7124--remote-invite.png)
    
    *Earlier candidate, mock desktop browser: the existing channel dialog
    now reachable for an eligible owned agent on another device. The two
    buttons have different send outcomes; Do nothing is not Cancel.*
    [Success and denial
    captures](#7124 (comment))
    · [Pending-state
    capture](#7124 (comment)).
    These show the relevant UI, not live agent availability, native
    authorization or the later draft-storage/catch-up repairs. No
    before-state screenshot is available.
    
    Existing coverage exercises exact recipients, invitation
    rejection/cancellation, new direct-message destinations, uploads, edits,
    thread re-entry and stored-draft deletion. The timeline regression
    checks the shared reply becomes visible using the available catch-up
    action.
    
    **Integration validation (2026-09-02):** independently reviewed the
    routing delta onto root `3a56d178`: seven original patches unchanged;
    two reconciliations retain generic publication-error toasts alongside
    authorization errors and retain non-authored editability updates. Added
    two production-hook regression tests (normal and queued-media
    publication) requiring visible generic error, recovered draft and
    released pending state.
    
    - Writer validation: **5,995 Desktop tests**, **42 focused tests**, **22
    mock-IPC browser journeys** (18 routing, 2 root provenance, 2
    destination binding), and **1 voice-note failure journey** passed; lint,
    types, size guards and E2E build also passed.
    - The broad suite ran before the final formatting-only test amendment,
    not as an exact-final-head rerun. Independent AST comparison confirmed
    that amendment is semantics-preserving; **4 fresh assertions at final
    `1144465d`** passed. Publication rechecked final-head TypeScript,
    amended-test formatting and `git diff --check` successfully. No new full
    repository `just ci` run is claimed.
    - Browser tests use an isolated E2E build and **mock IPC**, not live
    relay/native authorization. Historical screenshots above are explicitly
    earlier UI evidence, not exact-head runtime certification. Packaged
    Tauri/live-relay behavior was not independently witnessed.
    - **Published-head gates:** [current CI
    run](https://github.com/block/buzz/actions/runs/33657948560) and
    [renewed exact-head formal review
    request](#7124 (comment))
    must clear before landing. [Earlier CI
    run](https://github.com/block/buzz/actions/runs/33438436438) and the two
    earlier approvals cover `7ffead0f`, not this new head. Root CI/security
    clearance remains separate; the independent scoped integration approval
    is not merge authorization.
    
    To try it: in a channel or thread, select an owned nonmember agent,
    Send, then Invite or Escape and retry. Deny the add or revoke its
    response permission before sending: expect a visible error and
    recoverable draft, not a message missing the agent. During a pending
    send, return to the source thread, edit or clear the draft, then leave
    again: late completion must not overwrite that choice.
    
    **Limits:** permission checks and sending are separate operations;
    cancellation cannot retract a dispatched message. Draft protection is
    same-window, not new cross-window deletion synchronization. Standalone
    forum transport failure can still restore text/media without the exact
    selected recipients. Native compatibility is inherited: open-source
    builds may still recognize a valid legacy, self-declared agent already
    in the channel when verified ownership is absent or rejected; that does
    not establish ownership or unlock this owned-nonmember invitation path.
    Invalid policy from a verified owner is still rejected. No agent
    response is guaranteed.
    
    ---------
    
    Signed-off-by: Logan Johnson <[email protected]>
    Co-authored-by: Larry <627498bd4bd1f281a16431e3c6cce3b5c25b6692798c78672298aefbf2f8f8b5@buzz.block.builderlab.xyz>
    loganj and Larry authored Sep 4, 2026
    Configuration menu
    Copy the full SHA
    d595806 View commit details
    Browse the repository at this point in the history
  8. feat(desktop): invite owned agents from standalone forums (#7125)

    ## Summary
    
    In Desktop's standalone Forums, selecting an owned agent from another
    device could leave a post or reply unsendable if the agent had not
    joined the forum. This adds **Invite / Cancel** to the send flow so you
    can resolve membership without leaving your draft.
    
    - **Invite** checks response policy and your permission to add members,
    adds the agent to the forum, waits for refreshed membership, then
    rechecks authorization before posting to the original destination.
    Membership is forum-wide, not limited to one post.
    - **Cancel / Escape** keeps the text, attachments and selected
    recipients for retry. Unlike chat's **Do nothing / Send anyway**, this
    dialog has no reference-only send choice. Invite is disabled while
    pending; Cancel remains available.
    - Leaving the source post/reply cancels its pending invitation, even if
    you return. Errors remain visible, focus returns to the initiating
    editor when appropriate, and late completion cannot resume a cancelled
    post or interfere with a newer attempt.
    - A rejected send restores text, uploaded media and exact selected
    recipients to the source draft only if no newer edit, deletion, upload
    intent or send supersedes it. Clipboard verification settles before
    recipient capture, with stale edits/navigation fenced out.
    
    ### Related issue
    
    Targets `main` after #7124 merged. This PR reuses its publication checks
    and draft protection; the five forum commits have been replayed
    unchanged onto the merged parent. Owned-agent discovery (#7122) is
    already merged. Split from #7114.
    
    Forum creation/templates, channel-less Notes and local-agent management
    are unchanged. Duplicate-name binding from #7133 is already merged and
    retained by this stack. Inviting does not start a remote agent or
    promise that it is online or will reply.
    
    ### Testing
    
    Forum composer lifecycle tests, including clipboard-settlement cases,
    and TypeScript/changed-file formatting checks passed after the restack.
    Earlier invitation, focus and transport-recovery browser coverage is
    retained, not claimed as a fresh full browser run on this head. See
    [live CI](https://github.com/block/buzz/pull/7125/checks) for
    current-head results. Browser evidence uses mock IPC; no full local
    `just ci` pass or native/live-relay validation is claimed.
    
    To try it: open a forum post or reply, select an owned nonmember agent
    and send. Cancel, then retry without reselecting; Invite should add that
    agent before posting. Deny the add to check the visible error and
    retained draft. Navigate away/back during a pending invitation or
    rejected send; no stale publication or overwrite of a newer draft should
    occur.
    
    ![Forum invitation with Invite and
    Cancel](https://raw.githubusercontent.com/block/buzz/6481bd088d661975672addcc834231df6ac88705/pr-7125--forum-invite.png)
    
    *Earlier mock-browser capture, not current-head runtime proof. [Error
    and successful-post
    captures](#7125 (comment));
    no before-state/native capture available.*
    
    **Limits:** cancellation cannot undo accepted membership changes or
    dispatched posts; authorization and publication are not atomic. Recovery
    is same-window, subject to browser storage limits, and is not a durable
    in-flight send journal: reload/crash can lose a pending snapshot.
    Cross-window coordination and in-flight upload custody are unchanged.
    The parent's legacy member-agent compatibility does not establish
    ownership for nonmember invitations.
    
    ---------
    
    Signed-off-by: Logan Johnson <[email protected]>
    Co-authored-by: Larry <627498bd4bd1f281a16431e3c6cce3b5c25b6692798c78672298aefbf2f8f8b5@buzz.block.builderlab.xyz>
    loganj and Larry authored Sep 4, 2026
    Configuration menu
    Copy the full SHA
    e7e2993 View commit details
    Browse the repository at this point in the history
  9. fix(buzz-acp): bound busy-owner hold to prevent cross-channel starvat…

    …ion (#7337)
    
    ## Problem
    
    #6732 added a busy-owner hold to the ACP harness: when a scope's
    recorded session owner (`session_owners`) is checked out on **any**
    turn, `dispatch_pending` holds the scope's batch instead of dispatching
    it. The hold was added to keep one provider session per thread — but it
    is unconditional: it applies to `Conversation` scopes too, and it has no
    time bound.
    
    Under the default `session_policy=channel`, every channel collapses to a
    single `Conversation` scope, so once two channels' sessions land on the
    same worker (pass 2 of `try_claim` picks the first idle worker by index,
    so this happens quickly after any restart), channel A's mention starves
    behind channel B's in-flight turn — for up to the full
    `max_turn_duration` (7200s by default) — while other workers sit idle.
    The only signal is a DEBUG-level log, and the 👀 seen-reaction is added
    at queue admission *before* the hold decision, so the user sees the
    agent acknowledge the mention and then nothing.
    
    Observed in production on the first day of the v0.5.22 rollout: three
    separate incidents where a mention got 👀 but no turn started until an
    unrelated channel's turn ended on the shared worker (in the worst case
    the blocking turn sat in a single tool call for 6+ minutes).
    
    ## Fix
    
    One new seam, `AgentPool::hold_decision`, replaces the raw
    `should_hold_for_busy_owner` check in `dispatch_pending` (the predicate
    itself is unchanged and remains the inner check):
    
    - **`Conversation` scopes never hold.** Channel-policy channels and all
    DMs dispatch immediately; a busy owner means forking onto an idle
    worker, exactly the pre-#6732 behavior. This removes the cross-channel
    head-of-line blocking entirely for the default policy.
    - **`Thread` scopes hold for a bounded window.**
    `HOLD_BUSY_OWNER_TIMEOUT` (10s) is measured from the first time the
    batch is held (`held_since` stamp); once elapsed, the batch stops
    holding and forks a fresh session on an idle worker, rebuilding thread
    context from the relay. This preserves #6732's session-continuity intent
    for the momentary-busy case while capping the worst-case wait. No new
    timer is needed: held batches are requeued with preserved timestamps and
    re-evaluated on every dispatch trigger (turn end, relay event, 30s
    maintenance tick), so the effective worst-case re-check gap on a fully
    silent system is one maintenance tick.
    - **Holds are observable.** Holding logs at INFO and a hold expiry logs
    at WARN (previously DEBUG-only), and both emit observer-feed events
    (`busy_owner_hold`, `busy_owner_hold_forked`) with the scope, owner
    index, and held duration.
    
    `held_since` is derived state and is cleared on every removal path:
    dispatch/fork (inside `hold_decision`), `invalidate_channel_sessions`,
    `invalidate_scope_session`, and `switch_idle_agent_model`.
    
    ## Accepted trade-offs
    
    - A fork after an expired hold leaves the old owner's now-orphaned
    thread session in its session map until natural rotation/invalidation —
    benign, and identical to pre-#6732 fork semantics (`loadSession: false`;
    sessions are worker-pinned, so migration is not an option).
    - Under sustained pool exhaustion the hold stamp is cleared on the fork
    attempt and re-stamped next cycle, so the bound is effectively "timeout
    after a worker frees up," not absolute wall clock.
    
    ## Tests
    
    - New table test `hold_decision_covers_variant_session_busy_and_timeout`
    over the full input space (scope variant × idle-session presence × owner
    busyness × elapsed vs. window). The `Conversation` + busy-owner row is
    the cross-channel regression guard; the past-window row guards the
    bound. Both were mutation-checked: removing the variant gate or the
    timeout branch fails the suite.
    - `busy_session_owner_holds_batch_instead_of_forking_session` extended
    with the Hold → ForkAfterHold transition, the `Conversation` dispatch
    guard, and `held_since` pruning on channel invalidation.
    - Scope-invalidation and idle-model-switch tests extended to cover
    `held_since` cleanup alongside the existing `session_owners` assertions.
    
    Signed-off-by: Will Pfleger <[email protected]>
    wpfleger96 authored Sep 4, 2026
    Configuration menu
    Copy the full SHA
    b17c077 View commit details
    Browse the repository at this point in the history
  10. Verify ACP relay events before prompt routing (#7010)

    ## What changed
    
    Verify every Nostr EVENT received by buzz-acp immediately after
    deserialization. Events with an invalid NIP-01 ID or Schnorr signature
    are dropped before subscription routing, deduplication, replay-watermark
    updates, membership handling, or either harness queue.
    
    ## Safety
    
    Signature verification runs on the blocking pool so cryptographic work
    does not block the relay task. A verification failure drops only that
    event and keeps the connection available for subsequent valid traffic.
    The existing observer-control verification remains as defense in depth.
    
    Regression tests cover valid delivery; changed content, ID, signature,
    pubkey, tags, and timestamp; a forged owner shutdown command with a
    recomputed ID; forged membership notifications; and forged
    observer-control events.
    
    ## Testing
    
    cargo test -p buzz-acp
    
    cargo clippy -p buzz-acp --all-targets -- -D warnings
    
    just ci
    
    ---------
    
    Signed-off-by: Jordan Mecom <[email protected]>
    jmecom authored Sep 4, 2026
    Configuration menu
    Copy the full SHA
    e09f715 View commit details
    Browse the repository at this point in the history
  11. Persist video playback speed preference (#7336)

    ## Summary
    
    - persist the selected desktop video playback speed as a device-level
    preference
    - apply the shared preference to inline and review video players,
    including after a reload
    - cover persistence, validation, cross-window updates, and the
    end-to-end playback flow
    
    ## Verification
    
    - `node --test
    desktop/src/shared/lib/videoPlaybackSpeedPreference.test.mjs`
    - `cd desktop && pnpm exec tsc --noEmit`
    - `cd desktop && pnpm check:px-text`
    - `cd desktop && pnpm test`
    - `cd desktop && pnpm build:e2e && pnpm exec playwright test
    --project=smoke video-attachment.spec.ts`
    - pre-push: desktop check, file-size check, typecheck, and 6,416 desktop
    tests
    
    ---------
    
    Signed-off-by: morgmart <[email protected]>
    morgmart authored Sep 4, 2026
    Configuration menu
    Copy the full SHA
    5d10783 View commit details
    Browse the repository at this point in the history
  12. fix(desktop): restore mention chip identity icons (#7338)

    ## Summary
    
    Restore the missing **@ glyph for people and robot icon for agents**
    after #7133, and incorporate the requested compact public-key display.
    
    - Wrapping mention chips render their existing bounded icon-bearing
    leading fragment.
    - Readonly chips show bound keys using the same `8 leading…4 trailing`
    formatter as the channel member list: `Scout (150b20bd…15dc)`.
    - Full literal labels and exact keys remain authoritative in metadata,
    profile targets, title/accessible-name attributes, editor text, saved
    bodies and recipient tags. Display abbreviations are never used for
    recipient lookup.
    - Copy/paste restores the full literal label for a complete compact
    chip; partial selections remain plain text. Two keys sharing the same
    abbreviation still round-trip to their separate exact recipients.
    - No recipient-resolution, authorization, wire-format, composer, or CSS
    changes. Existing labels, icons, cloud markers and ordinary mentions
    remain intact.
    
    ## Verification
    
    Published candidate `9365ab9bc9d9c5d10802580cd576f8e378ff492f`, based on
    main `e09f715c9d0ee2cb7bf8a39061e601f3a502f588`:
    
    - **6,444 desktop unit tests passed** on this candidate's final source
    tree.
    - **44 mock-Chromium tests passed, zero retries in the final run**
    across mention recipients, clipboard and cloud provenance: exact
    recipient selection, ambiguity rejection, send/edit/reopen, forwarding,
    full/partial copy, mismatched-key rejection, matching-abbreviation
    collisions and 100%/150% narrow-window geometry.
    - TypeScript, desktop Biome/check guards, protected-feature production
    build and E2E build passed.
    - The compact-renderer regression fails with the formatting call
    removed. Original missing-icon and hidden-text accessibility regressions
    have red/green evidence.
    - Fresh self-review traced rendering, full-key metadata, copy
    classifier, paste normalization and identity trust. The same display
    formatter owns the accepted compact form on both clipboard sides.
    
    Iteration exposed an existing team-insertion separator flake (passed
    final full run) and two new fixture assumptions: non-member sends
    require invitation, and Chromium rich paste may retain an NBSP
    separator. Tests now exercise invitation and normalize only that
    separator when comparing the captured full body and exact tags; no
    product change was needed for either.
    
    Earlier local repository-wide `just ci` completed in two invocations
    because its initial call hit the ten-minute tool limit during Tauri
    compilation. Unchanged native/mobile/backend evidence is reused; the
    desktop delta received the full checks above and new remote CI. Native
    VoiceOver, real Tauri selection, dark theme and non-Chromium observation
    were not performed. Browser artifacts exercise real frontend with mocked
    Tauri/relay boundaries, not an installed release.
    
    ## Review and visual evidence
    
    Current-head CI and automated review must complete after this update;
    the old `2997bfb5` green results do not establish this new head.
    Required human review remains separate from agent approvals. No
    merge/install/restart authorization.
    
    Before/after icon evidence:
    #7338 (comment)
    
    Updated compact-key screenshots are posted below. The editor
    intentionally retains the full literal address; only readonly chip
    display is abbreviated.
    
    Origin:
    buzz://message?channel=3355d33a-b72a-423a-b064-a58275f9a8af&id=38b3a27e689f5a9604e273d45f4e3122fceba76081e7bcd3bbdbf439524a5a18
    
    ---------
    
    Signed-off-by: Logan Johnson <[email protected]>
    Co-authored-by: Larry <627498bd4bd1f281a16431e3c6cce3b5c25b6692798c78672298aefbf2f8f8b5@buzz.block.builderlab.xyz>
    loganj and Larry authored Sep 4, 2026
    Configuration menu
    Copy the full SHA
    4afef86 View commit details
    Browse the repository at this point in the history
  13. feat(buzz-acp): update base prompt; add buzz context and skills to Pi…

    … agents (#7335)
    
    ## Summary
    
    - launch Pi through a private Buzz wrapper so managed Pi agents receive
    Buzz's base prompt plus the configured thread/channel session model via
    `--system-prompt`
    - load the Buzz workspace skill directory with Pi's repeatable `--skill`
    flag, making `~/.buzz/.agents/skills/buzz-cli` available alongside Pi's
    normal global skill discovery
    - report Pi and `pi-acp` installation states separately so setup
    guidance points to the missing component
    
    `pi-acp` does not currently consume the ACP `session/new` system prompt,
    but its normal new-session and restore paths do honor
    `PI_ACP_PI_COMMAND` as the executable used to launch Pi. Buzz reserves
    that variable and sets it to a private generated launcher. The launcher
    invokes `pi` from Buzz's effective `PATH`, adds `--system-prompt <file>`
    and `--skill <workspace>/.agents/skills`, and forwards `pi-acp`'s RPC
    and session arguments unchanged. This keeps the integration entirely in
    `block/buzz`, without changes to Pi or `pi-acp`.
    
    ### How PI_ACP_PI_COMMAND works in `pi-acp`
    
    `PI_ACP_PI_COMMAND` selects one executable; it does not accept
    arguments. Therefore:
    
    ```bash
    # Does not work
    PI_ACP_PI_COMMAND="pi --skill ~/.buzz/.agents/skills"
    ```
    
    Buzz does not expose this variable as user configuration. It creates a
    private launcher and sets `PI_ACP_PI_COMMAND` only on the `pi-acp`
    child. Conceptually, that launcher executes:
    
    ```sh
    #!/bin/sh
    exec pi \
      --system-prompt "$PRIVATE_SYSTEM_PROMPT" \
      --skill "$HOME/.buzz/.agents/skills" \
      "$@"
    ```
    
    ### Related issue
    
    Follow-up to #7208. No duplicate issue or open PR found.
    
    ### Testing
    
    - `just ci`
    - `cargo test -p buzz-acp pi_launcher`
    - `cargo test --manifest-path desktop/src-tauri/Cargo.toml
    managed_agents::env_vars::tests`
    - `cargo test --manifest-path desktop/src-tauri/Cargo.toml
    managed_agents::discovery::presets::tests`
    - pre-push branch checks
    
    No screenshots: the UI change is state-dependent setup guidance only.
    
    ---
    **Update Sep 4, 13:35:** Made `PI_ACP_PI_COMMAND` entirely Buzz-owned.
    - Managed agent configuration now rejects the variable as a user
    override.
    - Buzz always launches `pi` from its effective `PATH` and rejects
    inherited values before creating its private launcher.
    - Removed the custom Pi executable discovery path and its internal
    environment alias.
    
    ---
    **Update Sep 4, 14:03:** Reject inherited `PI_ACP_PI_COMMAND` values
    instead of replacing them.
    - Pi startup now fails with an actionable message telling the user to
    unset the variable.
    - Removed the Pi-specific exception from the generic ACP environment
    injection path.
    
    Generated with Codex
    
    ---------
    
    Signed-off-by: Salman Mohammed <[email protected]>
    salman1993 authored Sep 4, 2026
    Configuration menu
    Copy the full SHA
    4beffef View commit details
    Browse the repository at this point in the history
  14. Add generic information-flow control core (#7293)

    Adds a dependency-free `ifc-core` crate implementing reader-set
    confidentiality labels and monotonic per-computation flow state.
    
    - Defines flow ordering, join, and meet over caller-supplied principal
    universes.
    - Fails closed for unknown or cross-universe input and checks reader
    widening at egress.
    - Includes property tests for lattice laws and monotonic taint, plus the
    design paper that motivates the broker integration.
    
    The crate deliberately contains no Buzz, Nostr, channel, membership, or
    grant policy; those remain in the Buzz adapter.
    
    ---------
    
    Signed-off-by: Jordan Mecom <[email protected]>
    jmecom authored Sep 4, 2026
    Configuration menu
    Copy the full SHA
    4d447b9 View commit details
    Browse the repository at this point in the history
  15. fix(sidebar): simplify unread indicators and emphasize priority activ…

    …ity (#7134)
    
    **Category:** fix
    **User Impact:** The sidebar now presents unread activity consistently:
    unread rooms are bold, offscreen activity is counted by destination, and
    DMs or directed activity receive stronger emphasis.
    
    **Problem:** Sidebar unread state was split across competing signals:
    agent work could trigger overflow, message totals inflated its count,
    non-DM rows showed redundant numerals, and routine room activity looked
    as urgent as DMs or directed messages. This made the sidebar noisy and
    made the overflow value harder to interpret.
    
    **Solution:** Use one stable offscreen unread control that counts rooms
    and DMs—not messages—and remove agent work from that signal. Keep
    ordinary room activity quiet; promote DMs, mentions, broadcasts, and
    relevant thread replies; preserve DM avatars and targeting; bold every
    unread room; and retain thread dots while removing non-DM numerals.
    
    <details>
    <summary>File changes</summary>
    
    **desktop/src-tauri/src/unread_catch_up.rs**
    Classifies relevant thread replies as priority activity during native
    unread catch-up so startup state matches live rendering.
    
    **desktop/src/app/AppShell.tsx**
    Passes the priority unread destination set into the sidebar.
    
    **desktop/src/features/channels/useUnreadChannels.ts**
    Projects unread destinations, priority state, and thread replies
    consistently while keeping Dock badge behavior separate from sidebar
    emphasis.
    
    
    **desktop/src/features/sidebar/lib/useOffscreenActivityChannelIds.test.mjs**
    Removes tests for the superseded agent/activity overflow projection.
    
    **desktop/src/features/sidebar/lib/useOffscreenActivityChannelIds.ts**
    Removes the old agent-plus-message overflow projection so agent work
    alone no longer creates the unread indicator.
    
    **desktop/src/features/sidebar/lib/useSidebarActivityOverflow.ts**
    Replaces activity-volume overflow state with unread-destination overflow
    state.
    
    **desktop/src/features/sidebar/lib/useSidebarUnreadOverflow.test.mjs**
    Covers priority detection and destination-count labels for the new
    overflow projection.
    
    **desktop/src/features/sidebar/lib/useSidebarUnreadOverflow.ts**
    Counts distinct offscreen unread destinations and determines quiet
    versus primary treatment per direction.
    
    **desktop/src/features/sidebar/ui/AppSidebar.tsx**
    Renders one stable overflow control, preserves protected-DM visibility
    filtering, and prioritizes visible unread DMs for previews and
    navigation.
    
    **desktop/src/features/sidebar/ui/AppSidebar.types.ts**
    Adds the priority unread destination set to the sidebar contract.
    
    **desktop/src/features/sidebar/ui/CustomChannelSection.tsx**
    Stops forwarding non-DM unread counts into custom channel rows.
    
    **desktop/src/features/sidebar/ui/MoreUnreadButton.test.mjs**
    Updates control coverage for explicit emphasis, destination labels, and
    DM targeting.
    
    **desktop/src/features/sidebar/ui/MoreUnreadButton.tsx**
    Applies quiet or primary treatment without changing geometry,
    accessibility text, DM avatars, or click behavior.
    
    **desktop/src/features/sidebar/ui/SidebarSection.tsx**
    Removes non-DM row numerals while retaining unread weight and thread
    preview affordances.
    
    **desktop/src/shared/ui/UnreadPill.tsx**
    Shares one composition between quiet and primary states so only color
    treatment changes.
    
    **desktop/tests/e2e/badge.spec.ts**
    Covers destination counting, promotion without count inflation,
    DM/thread priority, row bolding, and removed numerals; also captures the
    reviewed UI states.
    
    **desktop/tests/e2e/channel-activity-popover.spec.ts**
    Updates channel activity assertions for the numeral-free row treatment.
    
    **desktop/tests/e2e/channels.spec.ts**
    Updates channel unread expectations to use bold text rather than a row
    count.
    
    **desktop/tests/e2e/thread-unread.spec.ts**
    Keeps thread unread-dot and popover coverage while asserting the room
    itself is bold.
    
    </details>
    
    ## Reproduction steps
    
    1. Open a workspace with enough sidebar destinations to scroll rooms
    above or below the viewport.
    2. Receive ordinary unread activity in an offscreen room; verify one
    quiet `N unread` indicator appears and counts the room once regardless
    of message volume.
    3. Receive a mention, broadcast, or relevant thread reply in an
    offscreen room; verify the same count becomes primary without changing
    its geometry or adding a badge.
    4. Receive an unread DM, including thread-only activity; verify the
    indicator is primary, shows the DM avatar when available, and navigates
    to that DM.
    5. Scroll the destination onscreen or mark it read; verify the count and
    treatment update from the remaining offscreen destinations.
    6. Inspect unread non-DM rows; verify their names are bold, numeric
    badges are absent, and thread dots still open the unread-thread preview.
    
    ## Screenshots
    
    ### Ordinary unread room
    Routine offscreen room activity uses the quiet treatment.
    
    ![Quiet unread overflow
    indicator](https://d24qwcpro867f5.cloudfront.net/repos/buzz/prs/7134/sidebar-unread-overflow-default.png)
    
    ### Directed unread activity
    The same destination count becomes primary when an offscreen room has
    directed activity; geometry and label remain unchanged.
    
    ![Primary unread overflow
    indicator](https://d24qwcpro867f5.cloudfront.net/repos/buzz/prs/7134/sidebar-unread-overflow-primary.png)
    
    ### Thread-only unread DM
    A DM stays primary and retains its avatar even when only its thread has
    unread activity.
    
    ![Primary DM thread overflow
    indicator](https://d24qwcpro867f5.cloudfront.net/repos/buzz/prs/7134/sidebar-dm-thread-overflow-primary.png)
    
    ---------
    
    Signed-off-by: Taylor Ho <[email protected]>
    Co-authored-by: Rizz <302abe414ca6e3134763d2539bfcf145aea2a63fe5f8455204ed602fd40cf381@buzz.block.builderlab.xyz>
    Co-authored-by: Carl <acda9e433d19dcd0e6b6840f7f4b98f3a56f1fab98049d444c087019e6d36560@buzz.block.builderlab.xyz>
    3 people authored Sep 4, 2026
    Configuration menu
    Copy the full SHA
    f038cbb View commit details
    Browse the repository at this point in the history

Commits on Sep 5, 2026

  1. fix(desktop): keep packaged frontendDist relative so Windows embeds a…

    …ssets (#7177)
    
    ## Root cause
    
    `tauri-command.mjs` points `frontendDist` at a `mkdtemp` directory so
    concurrent OSS/internal packages cannot overwrite each other's assets.
    On Windows that is an absolute path with a drive letter.
    
    `FrontendDist` is an untagged serde enum whose **first** variant is
    `Url(Url)`, and `C:\Users\...` is a valid WHATWG URL with scheme `c:`,
    so serde selects `Url`. `tauri-codegen` then does:
    
        FrontendDist::Url(_url) => Default::default(),   // embed nothing
    
    A missing *directory* panics with a clear message; a URL is silent. The
    build exits 0 and produces an installable app with no frontend assets,
    which boots to `ERR_FILE_NOT_FOUND` in the WebView.
    
    Linux and macOS are unaffected — `/tmp/...` has no scheme, so it falls
    through to `Directory`.
    
    This affects every Windows build that goes through `pnpm tauri build`,
    including `release.yml`'s NSIS job and `windows-canary.yml`.
    
    ## Fix
    
    Pass the path relative to the config's own directory. `tauri-codegen`
    resolves `frontendDist` with `config_parent.join(path)`, so a relative
    path reaches the same directory and cannot parse as a URL. When the temp
    directory is on another drive there is no relative form, so the scratch
    root is created beside the config instead.
    
    `BUZZ_PROTECTED_BUILD_OUTPUT` still receives the absolute path, and
    cleanup is unchanged.
    
    ## Testing
    
    `tauriCommand.test.mjs` asserted against the value it had just been
    handed, so it could not observe this. Its fake CLI also resolved
    `frontendDist` against the process cwd, which is not what Tauri does.
    
    - Fake CLI now resolves against the config directory, matching
    `config_parent.join(path)`.
    - New case asserts the packaged `frontendDist` is not absolute and does
    not parse as a URL. The absolute check is what fails on Linux/macOS, so
    the regression stays covered on every platform.
    - Verified the new case fails on the unpatched wrapper and passes with
    the fix; the two existing cases pass either way.
    - Desktop suite: 5844 passed. `useDocumentVisible` has a pre-existing
    load-dependent flake that also reproduces on an unmodified checkout.
    - Biome check clean on both files.
    
    Verified end to end by rebuilding the Windows NSIS installer: embedded
    asset keys in `buzz-desktop.exe` went from 0 to 490, and the app
    launches.
    
    ---------
    
    Signed-off-by: Jeff Hedlund <[email protected]>
    Co-authored-by: Claude Opus 5 (1M context) <[email protected]>
    jhedlund and claude authored Sep 5, 2026
    Configuration menu
    Copy the full SHA
    dad5a33 View commit details
    Browse the repository at this point in the history
  2. chore(release): release Buzz Desktop version 0.5.23

    Co-authored-by: Release Automation <[email protected]>
    Signed-off-by: Wes <[email protected]>
    wesbillman and release-automation committed Sep 5, 2026
    Configuration menu
    Copy the full SHA
    b9392d9 View commit details
    Browse the repository at this point in the history
Loading