Skip to content

Accept mention tags in buzz-acp mention filter - #8014

Open
hunchulchoi wants to merge 1 commit into
block:mainfrom
hunchulchoi:acp-mention-tag-filter
Open

hunchulchoi wants to merge 1 commit into
block:mainfrom
hunchulchoi:acp-mention-tag-filter

Conversation

@hunchulchoi

@hunchulchoi hunchulchoi commented Oct 1, 2026 •

Copy link
Copy Markdown

Problem

Buzz clients emit ["mention", pubkey] tags for agent-address mentions in channel messages (see desktop/src/features/messages/lib/agentAddressMention.mjs), while ["p", pubkey] remains the notification mechanism.

buzz-acp's require_mention subscription filter only looked for p tags, so a mention delivered solely via a mention tag was silently ignored — the agent never saw the prompt and never responded.

Change

In match_event, treat ["mention", <agent_pubkey>, ...] the same as ["p", <agent_pubkey>] when require_mention is set. Any extra tag elements (e.g. the agent-address marker) are ignored.

Testing

  • Added filter::tests::test_match_event_mention_tag covering an event tagged ["mention", agent_pubkey] — fails before, passes after.
  • cargo test -p buzz-acp --lib — 21 tests pass.
  • Exercised end-to-end: deployed the patch on a running buzz-acp harness; a channel message carrying only ["mention", pubkey] (no p tag) previously produced no agent response.

buzz-review-completed

Buzz clients emit `["mention", pubkey]` tags for agent-address
mentions in channel messages, while `["p", pubkey]` remains the
notification mechanism. buzz-acp's require_mention filter only
looked for `p` tags, so a mention delivered only via a `mention`
tag was silently ignored — the agent never saw the prompt.

Match both tag kinds when require_mention is set.

Signed-off-by: choi <choi@dgst.me>
@github-actions

github-actions Bot commented Oct 1, 2026

Copy link
Copy Markdown

🔐 Codex Security Review

Status: review required for the current range.

The current range is 5fdb2e53659ee29002545f1022c138fe0b8282f9...f97af2d47f852c1d176a0dba230f42b0eadd1a50.
A new review must complete for this exact range. When manual authorization
is required, a user with write access must comment exactly
@buzz-security-review f97af2d47f852c1d176a0dba230f42b0eadd1a50 to authorize a new review.
Any previous review applies only to its recorded range.

@hunchulchoi
hunchulchoi marked this pull request as ready for review October 1, 2026 03:58
@hunchulchoi
hunchulchoi requested a review from a team as a code owner October 1, 2026 03:58

This branch has not been deployed

No deployments
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.

1 participant