Skip to content

feat(buzz-acp): use cat pickup reaction - #3870

Open
Greg-Moskalenko wants to merge 1 commit into
block:mainfrom
Greg-Moskalenko:feat/cat-pickup-reaction
Open

feat(buzz-acp): use cat pickup reaction#3870
Greg-Moskalenko wants to merge 1 commit into
block:mainfrom
Greg-Moskalenko:feat/cat-pickup-reaction

Conversation

@Greg-Moskalenko

Copy link
Copy Markdown

Summary

  • replace the two-phase 👀 / 💬 pickup indicator with one visible 🐱 reaction
  • clear the cat plus legacy pickup reactions on completion, failure, panic, membership removal, queue eviction, native steering, and shutdown paths
  • bind native-steer cleanup to the exact accepting turn so a late acknowledgement cannot attach cleanup to a successor turn

Verification

  • cargo test -p buzz-acp — 658 unit tests and 9 lifecycle integration tests passed
  • cargo clippy -p buzz-acp --all-targets --all-features -- -D warnings
  • cargo fmt --all -- --check
  • git diff --check

The exact-turn native-steer lifecycle handling adapts and credits the prior work in #1498.

Originating Buzz channel: 53e4b720-c324-4c27-b26c-aaaee778c857

Replace the two-phase eyes and speech-bubble pickup indicator with a single cat. Clean current and legacy reactions across completion, native steering, queue overflow, membership removal, panic, and shutdown paths.

The exact-turn native-steer cleanup adapts lifecycle work from block#1498.

Co-authored-by: Tyler Longwell <tlongwell@block.xyz>
Co-authored-by: Greg Moskalenko <greg1mosk@gmail.com>
Signed-off-by: Greg Moskalenko <greg1mosk@gmail.com>
@Greg-Moskalenko
Greg-Moskalenko requested a review from a team as a code owner July 31, 2026 07:34
@Chessing234

Copy link
Copy Markdown
Contributor

cute. can you keep the old eye/speech cleanup for a release or two so agents mid-upgrade dont leave stale pickup reactions behind?

@Chessing234

Copy link
Copy Markdown
Contributor

also: if the cat reaction fails to publish, does pickup still clear? might want a best-effort clear even when the reaction post errors

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.

2 participants