Skip to content

fix(acp): deliver forum mentions under the default subscription - #5945

Open
Chessing234 wants to merge 2 commits into
block:mainfrom
Chessing234:fix/acp-forum-mentions
Open

fix(acp): deliver forum mentions under the default subscription#5945
Chessing234 wants to merge 2 commits into
block:mainfrom
Chessing234:fix/acp-forum-mentions

Conversation

@Chessing234

Copy link
Copy Markdown
Contributor

Fixes #5268.

An agent started with the default --subscribe mentions subscribed to kind:9 stream messages, workflow approval requests and reminders. Forum channels don't use kind:9 — their conversation is kind:45001 posts and kind:45003 comments — so an agent invited to a forum channel joined, logged the subscription and showed online, and then never received an event for an @mention there. From the outside it looks like the agent is ignoring you; there's nothing in the log to suggest the mention was filtered out, because it was never delivered in the first place.

Both forum kinds are now in the default list.

  • --kinds still overrides the default wholesale, so anyone who has narrowed it explicitly is unaffected.
  • The three kinds the mode covered before are still covered, and a test asserts that, so a later edit can't quietly narrow it.
  • The list moved out of an inline closure in tokio_main into default_mention_kinds() (first commit, no behaviour change) so it's testable and visible next to the other subscription helpers.

Verified locally on the pinned 1.95.0 toolchain:

  • cargo test -p buzz-acp --lib — 780 passed (778 before, plus the two new)
  • cargo clippy -p buzz-acp --all-targets -- -D warnings — clean
  • cargo clippy --workspace --all-targets -- -D warnings — clean
  • cargo fmt --all -- --check — clean

Note: I'm an outside contributor, so the workflow runs on this PR will sit at action_required until a maintainer approves them; only the DCO check reports on its own.

The kind list for `--subscribe mentions` was an inline `unwrap_or_else`
closure buried in `tokio_main`, which is where a subscription gap can sit
unnoticed for a long time. Lift it to `default_mention_kinds()` next to the
other subscription helpers and pin the current coverage with a test, so any
later edit to the list has to keep kind:9, workflow approvals and reminders
deliberately rather than by accident.

No behaviour change.

Signed-off-by: Taksh <takshkothari09@gmail.com>
`--subscribe mentions` listened to kind:9, workflow approvals and reminders.
A forum channel carries its conversation as kind:45001 posts and kind:45003
comments, so an agent on the default subscription was deaf in exactly the
channels built for threaded discussion: it joined, logged the subscription,
showed online, and an `@mention` in a forum post produced no inbound event at
all (block#5268).

Add both forum kinds to the default list. `--kinds` still overrides it
wholesale, and the test added in the previous commit asserts the stream kinds
are still covered, so this cannot quietly narrow.

Signed-off-by: Taksh <takshkothari09@gmail.com>
@Chessing234
Chessing234 requested a review from a team as a code owner August 15, 2026 11:17
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.

buzz-acp: subscribe=mentions never receives forum-post mentions (kinds 45001/45003)

1 participant