Fix cross-pod membership notification fanout#1291
Merged
Merged
Conversation
Co-authored-by: npub1mprnacetjua2xx3p5eddmhxyk6wv929ymm5py8kd2xfxurxahspqqlgyta <d8473ee32b973aa31a21a65adddcc4b69cc2a8a4dee8121ecd51926e0cddbc02@sprout-oss.stage.blox.sqprod.co> Signed-off-by: npub1mprnacetjua2xx3p5eddmhxyk6wv929ymm5py8kd2xfxurxahspqqlgyta <d8473ee32b973aa31a21a65adddcc4b69cc2a8a4dee8121ecd51926e0cddbc02@sprout-oss.stage.blox.sqprod.co>
tellaho
pushed a commit
that referenced
this pull request
Jun 25, 2026
…ebar * origin/main: fix(sidebar): non-selectable channel names + copy/leave context menu actions (#1260) fix(runtime): sweep node wrapper processes hosting managed agent shims (#1296) fix(buzz-agent): follow symlinks when discovering skill directories (#1295) chore: add grab-emoji.sh to register Slack emoji in Buzz (#1292) Fix cross-pod membership notification fanout (#1291) fix(buzz-acp): strengthen agent communication rules in base prompt (#1293) chore(release): release Buzz Desktop version 0.3.34 (#1289) feat(desktop): refresh Agents tab live on inbound relay sync (#1256) fix(buzz-acp): inject Codex network allowlist for relay hostname at spawn time (#1287) Co-authored-by: Taylor Ho <taylorkmho@gmail.com> Signed-off-by: Taylor Ho <taylorkmho@gmail.com> # Conflicts: # desktop/src-tauri/src/commands/agent_models.rs
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
Root cause
ACP harnesses subscribe globally to kind 44100/44101 membership notifications with #p=[agent_pubkey], then dynamically subscribe to newly-added channels from that notification timestamp. The relay stored those notifications globally but only fanned them out to local WebSocket subscribers. In a multi-pod deployment, an add-member write handled by pod A did not reach an agent harness connected to pod B, so the harness never subscribed to the new channel and missed subsequent mentions.
Test plan